product-design
Specifies interaction choices, action scope, reversibility, recovery, and reachable states. Use when asked to "design the flow", "should delete be undoable", "choose the control", or "review this product decision". For visual implementation use ui-design; for motion use ui-animation; for wording use copywriting.
mblode · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mblode/agent-skills --skill product-design技能说明
name: product-design description: Specifies interaction choices, action scope, reversibility, recovery, and reachable states. Use when asked to "design the flow", "should delete be undoable", "choose the control", or "review this product decision". For visual implementation use ui-design; for motion use ui-animation; for wording use copywriting.
Product Design
Decide what the interface should do, then route who builds and verifies it: pick the right interaction, make scope and consequence clear, cover reality beyond the happy path.
- IS: the decision layer. From a brief, spec, mockup, intent, or existing UI: choose the interaction and control, name the object, scope, and consequence of each action, settle reversibility and the safeguard it implies, enumerate every reachable state, set resilience expectations, and require accessibility as task completion. It decides, then routes build, verification, and wording out.
- IS NOT:
- whether a feature deserves investment or fits the product: the external
product-judgmentskill from Brandwriter. - building or styling UI, visual direction, palettes, type:
ui-design. - auditing the built result (rendered quality, a11y markup, keyboard, layout, performance, React or Next code-level UX with a ship verdict):
ui-designAudit mode. - copy wording, persuasion, or AI-ism removal:
copywriting. - motion, gesture physics, or deep typography:
ui-animation,typography-audit. - whether an agentic feature earns trust:
ax-audit.
- whether a feature deserves investment or fits the product: the external
Routing boundary
product-design owns action semantics, scope, reversibility, and contested state choices. ui-design builds and styles those states. ui-animation owns timing, gestures, and measured motion. A routine missing loading or error state stays with the UI build; a gesture replacing a control needs a product decision and an accessible alternative before its physics.
Request modes
Resolve one mode from the user's verb and artifact before acting, then load that mode's references. references/rules.md loads in every mode: every finding cites a rule ID from it, and you cannot conclude that no rule governs a decision without the registry in front of you.
| Mode | Dispatch when the user asks for | Load (plus references/rules.md) |
|---|---|---|
| shape (default) | "design the flow for", "what control here", "how should this work", "is this the right pattern", a brief with no settled UI | references/product-judgment.md, references/surfaces.md |
| spec | "spec the right interaction", "define the expected states", judgment applied before or during a build | references/product-judgment.md, references/surfaces.md, references/naming-and-copy.md; route the build to ui-design |
| review | "review this flow for product correctness", "what's wrong with this UX decision", "is this the right interaction" | references/interface-quality.md |
| action | "what should this action affect", "should this be undoable", "do we need a confirm dialog", or reversibility is unsettled | references/naming-and-copy.md; route final wording to copywriting |
| harden | "make this resilient", "what breaks here", error, permission, offline, expiry, and destructive paths | references/surfaces.md, references/interface-quality.md, references/product-judgment.md |
Review mode is about a flow, not an artifact. "Audit this component", "check my UI", and "design QA this page" point at built markup and belong to ui-design Audit mode. This skill's review asks whether the decisions behind a flow are right, and stops at decision altitude.
Modes chain: shape leads into spec; review leads into harden. When intent is ambiguous, use the narrowest mode the verb supports. A URL, screenshot, route, or component identifies scope; it does not authorize edits.
references/lint-patterns.md has no mode: read it when deciding whether a standard belongs in the consuming project's linter or in this skill. evals/evals.json never loads during a user task; it is the regression set for anyone changing this skill.
Workflow
Product design pass:
- [ ] Step 1: Classify the request into one mode
- [ ] Step 2: Locate authority (user constraints, project design system, AGENTS.md)
- [ ] Step 3: Load rules.md plus that mode's reference files
- [ ] Step 4: Write the internal brief (shape, spec, harden); stop and ask if job, outcome, or consequence is unfillable
- [ ] Step 5: Name object, scope, consequence, and reversibility for each action in scope (spec, action, review)
- [ ] Step 6: Enumerate reachable states and check coverage (shape, spec, harden)
- [ ] Step 7: Emit output with a rule ID or labeled coverage gap per finding or decision; route follow-on work to siblings
- [ ] Step 8: Check the decision contract and identify unresolved product decisions
Steps 5 and 6 are mode-scoped because their references are: a pure action pass has no state matrix to enumerate, and a shape pass has no built actions to name yet.
Output length follows the work, not the template. A single settled decision is a short answer; drop the sections a pass did not need rather than filling them.
Decision authority
Conflict order, highest first:
- The user's explicit goal and constraints.
- Verified user and product evidence, and what the system actually does.
- Project-canonical guidance:
AGENTS.mdorCLAUDE.md, the project's design system, routed sibling skills. - Sibling-skill ownership: route, do not duplicate.
- This skill's standards (below).
- General interface and platform conventions (WCAG 2.2, NN/g, Apple HIG, Material, GOV.UK), which
references/rules.mdcites per rule.
When a request spans authorities, name the owning skill and hand off.
Product design standards
Five pillars, each naming its rule IDs in references/rules.md and the reference that details it.
- Right interaction. Pick the control from the choice