uidesign-flow

name	uidesign-flow
description	Use when an approved tone-and-manner decision must become concrete UI styling tokens and visual previews.
metadata	{"short-description":"tonemana → tokens → component+screen previews"}

Purpose

Turn a tone-and-manner decision into reviewable UI styling evidence:

• snapshot tokens used for styling
• render a component preview page
• render 3 representative screens
• produce a deterministic review bundle (UIDesign Pack)

This skill does not change IA (screens, navigation, decision points). That belongs to uiux-core.

When to use

• A UIUX Pack exists but “it works but looks off”
• You need a stable bridge artifact for human feedback
• You want consistent review outputs across Android/iOS/Web projects

Workflow

1. Locate the target UIUX Pack folder (uiux/YYYYMMDD-/).
2. Verify ui_spec.json includes meta.tone_and_manner with:
   • pattern_id
   • tonemana_spec_ref
   • token_refs.json and token_refs.css If missing, invoke $tonemana-apply first (do not proceed).
3. Validate token refs before reading or copying them:
   • each ref must be a relative path under tonemana/catalog/tokens/
   • refs must not be absolute paths and must not contain .. traversal
   • the JSON ref must end with .tokens.json; the CSS ref must end with .tokens.css
   • the referenced files must exist and match their expected token content type (JSON parses as an object; CSS is copied only from the allowed .tokens.css catalog path) If validation fails, stop and invoke $tonemana-apply or ask for corrected catalog token refs; never snapshot an unvalidated path.
4. Create output folder uidesign/YYYYMMDD-<slug>/ (or uidesign/.config output_dir override when present).
5. Copy templates into the output folder if missing.
6. Snapshot tokens into:
   • tokens/resolved.tokens.json
   • tokens/resolved.tokens.css (Copy only from the validated meta.tone_and_manner.token_refs.* catalog token files so previews are stable.)
7. Generate visual previews (HTML, no external deps):
   • previews/components.html
   • previews/screens/entry.html
   • previews/screens/form.html
   • previews/screens/status.html
   • previews/index.html as a hub
8. Fill uidesign_contract.yaml then update uidesign_spec.json.
9. Compute/update auto_review.json (machine checks vs human judgement).
10. Write diff_summary.md.
11. Hand off to humans:

• Humans write feedback into review_notes.md using the provided structure.

Output expectation

uidesign/YYYYMMDD-<slug>/ exists with all required artifacts and previews, and the pack is review-ready without additional tooling.