Kwark. Design System
Open Kwark

Product skills

The product-management and design skills Kwark uses, what each is for, when it is the right tool, and how to run it with an AI agent so the answer stays true to Kwark's rules.

Kwark method
discovery-opportunity-solution-treeFrame the outcome
discovery-prioritize-assumptionsTest the riskiest first
anthropic-design-ux-copyWrite every string

What these are

The founder keeps a library of skills in ~/.claude/skills/: packaged instructions an AI agent loads to run a product or design method the same way each time. They come from several sources (a product-management fellowship he took in 2025, published PM and design skill sets) and they are generic. This page says which ones Kwark uses, for which step of the method, and what Kwark changes about each so that a generic method gives a Kwark answer.

A skill is a tool, not an authority. Where a skill and a Kwark decision record disagree, the record wins.

Download the Kwark workflows

The original methods below describe the founder’s working library. The downloadable Product workflows adapt that process for a team using the public system. Each skill names its inputs and the result it should leave. They cover framing, opportunity mapping, assumptions, prioritisation, specification, synthesis, measurement and release checks.

The spine: one chain

The nextleap-pm skill distils the fellowship into one chain that every deliverable walks in order:

business outcome, product outcome, the person, the problem, a hypothesis, several distinct solutions, prioritise, design (flow, wireframe, prototype), spec, metrics and experiments.

Its first rule is Kwark’s too: never start from a solution. “It’s impossible to judge an idea if you don’t understand the problem it solves.” Kwark’s UX before build is this chain with the founder’s agreement inserted after the design step.

The skills, by step

Frame the problem

Skill For Kwark uses it when
pm-problem-statement Who is blocked, what they are trying to do, why it matters, how it feels Writing the one-sentence need at the top of a spec
prod-problem-validation Whether a problem is worth solving: frequency, intensity, workarounds A request arrives with no named person
pm-jobs-to-be-done, prod-jtbd-analysis The job a person hires a product for, pains and gains, the forces for and against switching Finding the real job behind a feature request (“make sure 23 people arrive at 06:30”, not “manage call sheets”)
pm-customer-journey-map Stages, actions, thoughts, feelings across a flow Walking a multi-screen journey, such as a guest who imports a film and reloads (Decision 0034)
pm-proto-persona A working profile before deeper validation Rarely; Kwark’s people are already named on Discovery. Label any persona as a proto-persona, not research

Map the options

Skill For Kwark uses it when
discovery-opportunity-solution-tree, pm-opportunity-solution-tree From one outcome to the opportunities under it, the solutions for each, and the tests A broad ask (“make Home calmer”) needs breaking into separable problems
discovery-brainstorm-ideas-existing Ideas from PM, designer and engineer viewpoints Three distinct solutions are needed for a record’s Alternatives section
pm-user-story-mapping Activities, steps and release slices along the journey Cutting a big feature (series and universes) into slices that each ship safely

Find what could be wrong

Skill For Kwark uses it when
discovery-identify-assumptions-existing Risky assumptions across value, usability, viability and feasibility Before any build longer than a day
discovery-prioritize-assumptions An impact by risk grid and an experiment for each Choosing which assumption to test first
discovery-brainstorm-experiments-existing, pm-pol-probe The cheapest test that could prove an assumption wrong Choosing between a mock-up, a preview build and a role simulation
discovery-interview-script, prod-user-interview Interview questions about past behaviour, no pitching The founder has a producer meeting or a shoot coming
discovery-summarize-interview, anthropic-design-research-synthesis Turning notes into needs and actions After a real conversation, with the person’s words kept exact

Decide what goes first

Skill For Kwark uses it when
discovery-prioritize-features, pm-prioritization-advisor Ranking a backlog by impact, effort, risk and fit An audit produces 40 findings (the 17 October audit ranked its top ten by what each cost the writer)
prod-scope-cutting Fixed time, variable scope A feature has grown past its appetite
prod-bet-sizing One-way and two-way doors; how much a bet is worth Anything expensive to reverse: data shape, permissions, naming

Specify and hand off

Skill For Kwark uses it when
anthropic-pm-write-spec, pm-prd-development, prod-prd-writing A spec with goals, non-goals and acceptance criteria Writing the proposal that becomes the decision record. Use Kwark’s parts list on Specs and handoff
anthropic-design-design-handoff Layout, tokens, props, states, breakpoints Handing a designed screen to a builder agent
pm-user-story Stories with acceptance criteria Writing the tests a fix must pass

Position and compare

Skill For Kwark uses it when
anthropic-pm-competitive-brief, prod-competitor-analysis Feature matrices and gap analysis A competitor review. Filter it through Competitors are the floor
pm-positioning-statement, prod-product-positioning Who it is for, the problem, the category, why it differs Public pages such as /why and /info, where every sentence is a promise

Review the design and the words

Skill For Kwark uses it when
anthropic-design-design-critique, ui-design-review Hierarchy, consistency, usability The UI and UX supervisor rungs of the review ladder
anthropic-design-accessibility-review, a11y WCAG contrast, keyboard, targets, screen reader Every UI review; the result lists P0, P1, P2 with criteria
anthropic-design-design-system Naming, hard-coded values, documenting a pattern Auditing a screen for raw colours or adding a pattern to this site
anthropic-design-ux-copy, ux-writing Buttons, errors, empty states, toasts Writing every string in a spec
ux-researcher-designer Personas, journeys, usability test plans Planning a usability session with a real person

What Kwark changes about every skill

Generic product methods assume a growth business with a research team. Kwark is a calm place to write with one founder. Tell the agent this before it runs any skill.

  • Never let a skill’s metrics become engagement targets. No daily active streaks, return-visit goals, notifications to bring people back, or public counts (Decision 0001). Kwark measures whether work is safe and whether people can do their job.
  • Never let a brainstorm propose AI scoring, coverage or feedback on the writing (Decision 0002), or coaching prompts (Decision 0004).
  • Never let a synthesis invent users, quotes or numbers. If there are no interviews, the skill’s output says so.
  • Never run an A/B test on writers’ work or split people into groups that see different safety behaviour. Kwark’s tests are mock-ups, preview builds, role simulations and single real sessions.
  • Always estimate reads, writes, listeners and file sizes for the actual action and expected audience. Use the project’s current service limits and cost constraints.
  • Always keep competitor names out of anything published (Decision 0045).
  • Always finish with a decision the founder can make in one message: two or three options, a recommendation, and its cost.

How to run a skill with an agent

  1. Load the context first. Give the agent the project’s mission, the current handoff and relevant decision records. For a team starting from this site, use Principles, the closest kit and its own source artefacts.
  2. Name the skill and the step. “Use discovery-identify-assumptions-existing for the call sheet crew link. We are at step 5 of discovery.”
  3. Give the Kwark constraints in the prompt (the list above), not afterwards.
  4. Ask for the output in Kwark’s shape: a need sentence, options with costs, a recommendation, open questions that change the build (three at most).
  5. Review it as the founder would. Does it count, grade or nag? Does it claim evidence it does not have? Is it phone first?
  6. File it. Proposals in docs/ux/proposals/, reviews in docs/ux/audit/, the decision in docs/ux/decisions/.

When you run a product or design skill for Kwark, state at the top which skill you used and which step of the method it serves, and list any of the skill’s defaults you overrode because of a Kwark decision record.

Run discovery-prioritize-assumptions on the crew link and conclude: “Riskiest: an anonymous link exposes contact numbers. Test: security review of the rule before any UI.”

Do

Run a metrics skill and propose “daily active writers” and a streak to raise it.

Don’t

AI readiness test

Task. Use an opportunity solution tree to plan “help writers finish their first draft”.

Give the agent. This page, Discovery, Decisions 0001, 0002, 0004, 0008.

Constraint. Kwark’s constraints stated before the tree.

A reliable answer

  • The outcome is about the writer’s progress on their own terms, not engagement
  • No streaks, scores, public counts or AI feedback appear as solutions
  • Each solution names the artefact it feeds or the fear it removes
  • Ends with the riskiest assumption and the smallest test, labelled honestly

Give this Markdown to your coding agent or share its URL.

Open .mdllms.txt
Loading…