---
name: "skill-product-design"
type: skill
license: CC BY-NC-SA 4.0
description: 'Design product and UI against a design system — screens, flows and components for the digital products. Use this whenever Pixel needs to design an interface for careerOS, app.fitness, Luna or any app surface, working in Figma and handing specs to Forge to build. Reads the product''s design system; never writes the repo itself. Maturity: later.'
---

# skill-product-design

Pixel's interface skill. Designs screens and flows against a product's design system, producing specs Forge can build from.

## Behaviour

Trigger: a product needs a screen, flow or component designed, or an existing one reworked.

Loop:

1. Read the product's design system and the requirement (from the operator, Atlas or a Linear ticket).
2. Design the screens and flows in Figma using the system's components; cover states (empty, loading, error) and responsive behaviour.
3. Annotate for build — spacing, tokens, interactions, edge cases — so Forge can implement without guessing; map components via Code Connect where it exists.
4. Hand the spec to Forge; route to Prism for review once built.

**No design-system Figma file for this product — the written-spec branch.** Not every product has been designed in Figma, and for some it never should be: a small internal console built by Forge from code, with no Figma-to-code path in its repo, gains nothing from a Figma file that a written spec does not already give the builder. Where **no Figma file exists for the product and the target repo has no Figma-to-code path**, do not create one to satisfy step 2. The harvest-ready deliverable is instead a **structural spec written directly into the ticket body**, and it counts as harvest-ready for Forge only when it contains: a **route and component map** (every screen and the components it composes, named against the repo's existing components where they exist); **panel placement** (what sits where, at what breakpoints); the **flows and drill-downs** between screens; a **states table** covering empty, loading, error and any per-panel state; and the **interaction spec** (what each control does, keyboard and focus behaviour where relevant). Annotate spacing and tokens against the product's design system as step 3 would. Creating a Figma file remains right where the product *will* be designed there going forward — say which case applies in the hand-off. `skill-dispatch-run` step 5 lands a written spec in the ticket body under the exec-shaped hand-off. (Worked case: A1-373, the firmup-operator dashboard IA and navigation spec, Pixel dispatch 2026-08-25 — a route/component map, panel-placement table, drill-down flows and states table written into the ticket in place of a wireframe — APP-1062.)

## The Journey view — deliverable format

A **journey map** is a product-design deliverable with its own format rules. They were settled across the first build and four further review rounds on A1-685 (Muse Route A handover, 2026-10-19) and belong here because this skill owns design deliverables. Five rules, all five load-bearing:

1. **A journey is a branching map, not a row.** Draw every branch and every return, not the happy path, and **label each connector with the control that triggers it** — the tap, the field, the back gesture — so the map reads as a mechanism rather than a sequence. A single left-to-right row of cards with notes beneath reads as linear; that was the first build on A1-685 and it was rejected.
2. **Thumbnails keep the full phone ratio, uncropped** — about 1:2. A cropped or re-proportioned screen has stopped being the screen.
3. **All connectors are elbows.** Orthogonal throughout, never mixed with curves inside one map.
4. **A scaled thumbnail draws its frame once at full size**, then scales the contents — scaling a frame with a 2px border gives an uneven stroke across thumbnails of different sizes.
5. **The Journey view carries purpose and connection notes only.** Why-notes, open questions and annotation threads stay on the prototype view; mixing the two makes the Journey view unreadable at map zoom.

Hand the Journey view over **with** the prototype view, never instead of it: by rule 5 the two carry different note classes and neither is complete alone.

(Evidence weight: one session, four review rounds after the first build — a single observation. It is authorable now because the rules came out of those rounds already concrete, not because the pattern has recurred. APP-2466.)

## Reads

The product's design system, the requirement/ticket, `github-conventions` (for handoff), the Figma library.

## Guardrails

Design against the system, not around it — extend the system deliberately, do not fork it per screen. Specify enough that Forge does not have to invent. Never write or merge repo code. Propose-only.
