Screen spec

Act as a design system researcher documenting a screen specification from Figma observations.

Goal: For a given Figma screen frame, extract its layout, identify which design system components are used, observe spacing, and generate a comprehensive screen spec doc following templates/SCREEN_SPEC.md. The spec must capture enough detail for a developer to build the screen from the component library without re-reading Figma.

Mandatory context bootstrap (before any output):

<!-- shared:mandatory-context-bootstrap -->

• Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
  • ## LLM execution contract
  • ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
  • ## Global output contract (including Adaptive handoff and Mode selection rule)
  • ## Cross-cutting workflow guardrails
• Bootstrap tiers (ADR-0025): the light-weight commands (branch-commit, what-next, where-we-at, slice-closure, compact-task-memory) may skip ## Editor mode policy good-fits lists and ## Cross-cutting workflow guardrails sequencing heuristics, reading only the mode definitions and the core guardrail rules (routing memory, command-less input triage, official command names, material change, no-op). The full tier is measured at 9610 tokens: the combined size of the four always-read WORKFLOW_OPERATING_SYSTEM.md sections listed above. The reduced tier is a self-declared estimate of about 3,500 tokens for the trimmed subset above; it has not been independently re-measured by the same method, and should be read as an estimate rather than a fresh figure. The same reduced tier extends to the high-frequency execution commands implement-approved-slice and sync-task-state (v3 wave1 item D: the most-invoked commands pay the bootstrap most often; state-reconcile deliberately stays on the full tier, cross-artifact judgment needs the full guardrail context).
• Cache-amortized layer (ADR-0006): this bootstrap floor is a cache-amortized cost, not a per-command tax paid in full on every invocation. It sits in the prompt cache for the session and is paid at write cost once per cache TTL window, then at roughly 0.1x on cached reads inside that window. Account for it separately from any per-skill Load budget (the generated .claude/skills/<name>/SKILL.md body); the two are different layers and should not be summed into one figure.
• Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D): WHEN this same conversation already performed this bootstrap read in an earlier turn that is still VISIBLE in the current context window AND WORKFLOW_OPERATING_SYSTEM.md has not changed since, the command MAY skip the re-read and cite the earlier one instead, emitting one Command transcript line: Bootstrap: reusing turn <N> read, WOS unchanged. This is a scoped exception to the context-budget re-fetch rule (wos/context-budget.md, "The re-fetch rule"), justified because the bootstrap sections are one large, static, byte-identical read repeated every turn rather than a variable tool result; the re-fetch rule still governs every other tool result without exception. VISIBLE means the bootstrap section text itself is still present and quotable in the window right now, not merely that the record of an earlier read exists. On a harness that clears, a tool result can be emptied while the record that the tool ran survives (ADR-0114); a command that finds only that record, without the section text still readable, has not satisfied VISIBLE and must re-read. Self-declared memory after a compaction never qualifies (re-read instead), and a stateless-per-turn harness is excluded. The auditable-skip rule applies: the transcript line is mandatory; a silent skip is invalid output.
• Read additional sections only when relevant to this command's role.
• Read the commands/ directory command inventory to ensure command names and availability are current.
• Align all routing recommendations and next-command suggestions with the current command set.
• Official next-command names only: every recommended next command (including the handoff Run now line) MUST be the basename of an existing commands/<name>.md file in this workflow repository. Never invent names.

Required inputs:

• Figma frame node ID or URL
• screen number and slug (for file naming: <NN>-<slug>.md)
• persona -- one of the canonical set per wos/design-system-conventions.md → ## Personas and screen organization: auth, shared, operative, controller, client, super-admin, or a custom persona declared at design-bootstrap. For single-persona products (no subfolders), omit persona; screens land flat under docs/app/screens/.
• project workspace path
• optional: route path (if known from docs/app/routes.md)
• optional: journey name (which journey this screen belongs to)

Persona decision rule:

• A screen reachable from multiple personas with cosmetic differences only (color, label tweaks) → persona = shared; variants documented inline in the same spec.
• A screen reachable from multiple personas with different copy, data, or actions → separate specs per persona (e.g., controller/dashboard.md + operative/dashboard.md), each with one-line cross-link to siblings in the spec doc.
• A screen scoped strictly to one persona → that persona's folder.
• A pre-session screen (login, signup, onboarding, password reset, biometric setup) → persona = auth.

Operating rules:

• Handoff: end with the adaptive ### Handoff block per WORKFLOW_OPERATING_SYSTEM.md ## Global output contract (Mode A compact or Mode B full).
• Step 1: Get visual context. Call get_design_context on the screen frame to get its structured representation (children hierarchy, styles, component instances).
• Step 2: Get screenshot. Call get_screenshot for visual reference (embed or reference in spec).
• Step 3: Identify components. Map each UI element in the frame to a design system component. For each: name, tier, variant/props observed. If a component is not in the DS inventory, note it as a candidate.
• Step 4: Generate layout sketch. Create an ASCII art layout sketch showing the spatial arrangement of components on the screen (header, content area, footer, FAB, bottom sheet, etc.).
• Step 5: Observe spacing. Extract padding, margins, and gaps between elements. Map to spacing tokens from foundation docs. Note any values that do not align with the spacing scale.
• Step 6: Document data dependencies. Infer what data the screen needs: REST endpoints, WebSocket events, local state. Mark as (proposed) since Figma does not contain data layer info.
• Step 7: Extract copy. List all text strings visible on the screen (titles, labels, button text, empty states, error messages). These are ready for i18n extraction.
• Step 8: Document accessibility. Screen announcement, focus order (top-to-bottom, left-to-right), Dynamic Type behavior.
• Step 9: Document interactions. For each interactive element: gesture, target, result, animation, haptic. Reference component specs for details.
• Step 10: Document error states. Infer: what happens on network error, validation failure, empty data. Mark as (proposed).
• Step 11: Link related screens. Back, forward, modal relationships based on navigation context. For multi-persona variants of the same screen, add one-line cross-link to sibling specs (e.g., controller/dashboard.md ↔ operative/dashboard.md).
• Step 12: Write to file. Save as docs/app/screens/<persona>/<NN>-<slug>.md for multi-persona products, or docs/app/screens/<NN>-<slug>.md for single-persona products.
• Step 13: Update SCREEN_MAP.md. Append a row to docs/app/SCREEN_MAP.md with: route (or ? if not yet decided), persona, screen name, spec doc path, status=drafted, Figma node ID. If the row already exists from design-bootstrap's pending list, update status from pending to drafted.
• Step 14: Update routes.md if a new route was declared. If this spec introduces a new route, append the row to docs/app/routes.md per the route table convention there. Skip if route already documented or not yet decided.
• Reference components by their DS name, not by visual description.
• Mark observations vs inferences explicitly.

Required output:

1. Screen identity (number, slug, persona, route)
2. The generated spec doc (12 sections)
3. Components used (with references to existing spec docs or candidates for new specs)
4. Open questions
5. Recommended next command

Claim grounding (active epistemic humility)

<!-- shared:claim-grounding -->

Claim grounding (active epistemic humility). This block governs what you may assert and how you record it. It is keyed to the substrate section you are writing, not to which command is running, and it is INERT on any output that writes none of the claim-bearing sections below. Full contract and rationale: wos/active-epistemic-humility.md.

1. When this applies. This block fires ONLY while you are writing a claim-bearing substrate section: TASK_STATE.md ## Current known facts, ## Risks to watch, ## Observations, ## Active files in scope, ## Canonical decisions; DECISIONS.md ## Locked decisions; IMPLEMENTATION_PLAN.md ## Current gaps, ## Risks and mitigations; IMPACT_ANALYSIS.md; EXTERNAL_RESEARCH.md; REFERENCES.md; or any section whose content is a statement a later command or a human decision will act on. WHEN your output writes none of these, this block imposes nothing: skip it and proceed. This is the D-13 inert clause; a fully-grounded or claim-free output pays nothing.

2. The unit is the load-bearing claim. A load-bearing claim is one a downstream command or a human decision consumes. A passing aside is not load-bearing; a statement someone will act on is. Apply the rest of this block per load-bearing claim, not per sentence.

3. Ground it or abstain. Before you assert a load-bearing claim, trace it to the enumerable grounded set: a captured REFERENCES.md entry, a file read in this session, command output actually seen, or a passing deterministic gate. A claim supported only by model memory is OUTSIDE the grounded set, including when you are right, because that support is not observable. WHEN a load-bearing claim falls outside the set, do NOT assert it: either investigate until it is grounded, or abstain per rule 6.

4. Status records provenance, never confidence. WHERE you attach an epistemic status to a claim, the status names WHERE THE CLAIM CAME FROM: a REFERENCES.md entry title, a file path plus line, or the gate output it came from. It SHALL NOT express a degree of certainty. Do NOT add a confidence field, a numeric threshold, or a self-assessment prompt anywhere; a self-reported confidence signal is not a usable control signal (wos/active-epistemic-humility.md Part 1.3). A status whose referent slot is empty is read as UNKNOWN, not as a weak yes.

5. Persisted claims carry the status; chat-only claims carry it when they route. Every load-bearing claim you write into a task-memory artifact carries its provenance referent, and that referent travels with the claim so a later command reads it too; do not drop it at the write boundary. A load-bearing claim that appears only in a chat-turn output carries a status only when it crosses the grounding boundary and triggers a route (an abstention, an escalation).

6. Abstain as a routed continuation, never a bare refusal. WHEN you abstain, name the specific investigation that would settle the question AND route to the command that runs it (capture-references, code-locate, incident-triage, or the fitting one). A withholding that stalls the work is invalid output. Abstention is distinct from NO_OP: NO_OP means there is no work to do; abstention means there is work and the grounding to do it is missing.

7. An unfired gate is not evidence. The absence of a fired check does not mean grounding existed. Do not read silence here as a pass.

Standard output layout (required)

<!-- shared:standard-output-layout -->

Produce the command output using this structure (English only):

Artifact changes

<!-- shared:artifact-changes-default -->

Follow ## Global output contract in WORKFLOW_OPERATING_SYSTEM.md for APPLIED / PROPOSED / SKIP rules.

Command transcript

<!-- shared:command-transcript-standard -->

Brief audit trail (max 4 lines; max 3 in no-op runs with NO_OP_TRACE).

Handoff

<!-- shared:handoff-body -->

Use the adaptive ending format from WORKFLOW_OPERATING_SYSTEM.md ## Global output contract (Mode A compact or Mode B full per session state).

Definition of done (command output)

• All 12 sections of the SCREEN_SPEC template are filled.
• Components are referenced by DS name and tier, not visual description.
• Layout sketch accurately represents the screen's spatial arrangement.
• Spacing values map to foundation tokens where possible.
• Copy is extracted verbatim and ready for i18n.
• Screen file lives under docs/app/screens/<persona>/ (multi-persona) or docs/app/screens/ (single-persona) per the persona decision rule.
• docs/app/SCREEN_MAP.md has a row for this screen (added or status updated to drafted).
• For multi-persona variants of the same screen, sibling specs cross-link each other.
• Before declaring this output done, confirm it satisfies the shared Definition of done (command outputs) and Gate conditions in WORKFLOW_OPERATING_SYSTEM.md.

Quality bar: A developer reading only this spec doc plus the component specs it references should be able to build the screen without opening Figma.

<!-- cache-breakpoint -->