菜单
Use when an approved tone-and-manner decision must become concrete UI styling tokens and visual previews.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| 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"} |
Turn a tone-and-manner decision into reviewable UI styling evidence:
This skill does not change IA (screens, navigation, decision points). That belongs to uiux-core.
ui_spec.json includes meta.tone_and_manner with:
pattern_idtonemana_spec_reftoken_refs.json and token_refs.css
If missing, invoke $tonemana-apply first (do not proceed).tonemana/catalog/tokens/.. traversal.tokens.json; the CSS ref must end with .tokens.css.tokens.css catalog path)
If validation fails, stop and invoke $tonemana-apply or ask for corrected catalog token refs; never snapshot an unvalidated path.uidesign/YYYYMMDD-<slug>/ (or uidesign/.config output_dir override when present).tokens/resolved.tokens.jsontokens/resolved.tokens.css
(Copy only from the validated meta.tone_and_manner.token_refs.* catalog token files so previews are stable.)previews/components.htmlpreviews/screens/entry.htmlpreviews/screens/form.htmlpreviews/screens/status.htmlpreviews/index.html as a hubuidesign_contract.yaml then update uidesign_spec.json.auto_review.json (machine checks vs human judgement).diff_summary.md.review_notes.md using the provided structure.uidesign/YYYYMMDD-<slug>/ exists with all required artifacts and previews, and the pack is review-ready without additional tooling.
Use when finishing a branch or PR after verification and review, including merge, PR publication, keep, discard, cleanup, local sync, and reporting merge or PR URLs with current git state.
Use when handling received code-review feedback on a PR or diff, including requested changes, inline comments, approvals, non-blocking notes, and disputed suggestions. Separates accepted fixes, refutations, deferrals, clarification needs, and merge handoff.
Use when preparing a focused code-review request for a PR or diff after implementation evidence exists, especially to package scope, reviewer focus, PR URL, verification, known risks, and deferred work without deciding final submit readiness.
Use before every submission to decide whether required checks, artifacts, and branch evidence are complete enough to submit.
Use when work is complex, long-running, multi-step, cross-boundary, likely to span multiple PRs/sessions, or needs handoff-ready planning under plans/.
Use when adding or changing Agent-facing workflows, generated prompts, collect plans, executable handoff artifacts, CLI workflows, controller/target-local workflow chains, or validation artifacts consumed by downstream reports. Do not use for ordinary code changes without an Agent-facing workflow or generated instruction surface.