Product Design

Decide what the interface should do, then route who builds and verifies it. Choose the right interaction, make scope and consequence clear, and cover reality beyond the happy path. This skill owns the decision of what should exist and how it should behave; it routes the visual build to ui-design, the verification of the built result to ui-audit, and copy wording to copywriting.

• IS: the decision layer. Given a brief, spec, mockup, intent, or existing UI, decide the right interaction and control, name the object, scope, and consequence of actions, enumerate every reachable state, set resilience expectations, and require accessibility as task completion. It decides, then routes the build and the verification out.
• IS NOT:
  • building or styling UI in code, visual direction, palettes, type: use ui-design.
  • auditing the built result (rendered quality, a11y markup, keyboard, layout resilience, performance, type surface, and React/Next code-level UX with a ship verdict): use ui-audit.
  • copy wording, persuasion, or AI-ism removal: use copywriting.
  • deep typography or motion: use typography-audit or ui-animation.

product-design or ui-audit?

The dispatch signal is the artifact, not the topic. Both skills care about states and interaction; they act at different moments.