---
description: Generate or revise a JSX/TSX mock for a named user flow. Mocks are high-fidelity but non-functional, reference the design system and interaction design, and pass a text feasibility audit before being committed.
arguments:
  - name: flow
    description: The flow to mock (must exist in flows.md). If omitted, lists available flows.
    required: false
---

Invoke the `composer-mocks` skill with `$ARGUMENTS`.

Prerequisites the skill checks before generating:

1. `docs/planning/flows.md` exists and names the flow.
2. `docs/planning/design-system.md` exists (tokens, type, components vocabulary).
3. `docs/planning/interaction-design.md` exists (state surfaces, motion, input, i18n, breakpoints).
4. `docs/planning/mocks/tokens.ts` is current with `design-system.md`.

If any prerequisite is missing the skill stops and points at it. The mock is
only as good as the systems it references.

After generation the skill runs a **text feasibility pass**: every visible
string is categorized (static, computed, authored), computed strings are
traced to source data and transformations, and any string that implies an
unspecified feature is flagged for the user to either spec properly or remove
from the mock.

After a clean text pass, the skill optionally summons Marge (end-user) and
Maya (a11y) for a review.