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. This skill owns the decision; it routes the build, verification, and copy out (ownership map in Related skills).

• IS: the decision layer. From a brief, spec, mockup, intent, or existing UI: choose the right interaction and control, name the object, scope, and consequence of actions, enumerate every reachable state, set resilience expectations, require accessibility as task completion. It decides, then routes build and verification out.
• IS NOT:
  • building or styling UI, visual direction, palettes, type: use ui-design.
  • auditing the built result (rendered quality, a11y markup, keyboard, layout, performance, type surface, 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?

Dispatch on the artifact, not the topic. Both care about states and interaction; they act at different moments.