design-workflow
Use when building or changing UI, components, design tokens, colours, typography, motion, imagery or a DESIGN.md, in any frontend stack (Flutter, Next.js, React, Obsidian, UI5), and before approving a plan that touches a rendered surface. Gives the ten-step design workflow, the definition of done for a component, and the per-stack way to do each step.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- design-workflow
- description
- Use when building or changing UI, components, design tokens, colours, typography, motion, imagery or a DESIGN.md, in any frontend stack (Flutter, Next.js, React, Obsidian, UI5), and before approving a plan that touches a rendered surface. Gives the ten-step design workflow, the definition of done for a component, and the per-stack way to do each step.
02 资源文件 3
- 参考文档sections/flutter.md1.3 KB
- 参考文档sections/web.md1.2 KB
- 参考文档sections/workflow.md3.7 KB
03 SKILL.md 正文
design-workflow
A decided design must reach the build. Docs alone do not reach an agent, so this skill is routed by what
you are doing (UI work). Every step is stack-neutral (purpose, artefact, check). The full table, the
definition of done, the per-stack matrix and the sources are in sections/workflow.md; the per-stack
detail is in sections/<stack>.md (sections, not skills: Read the file when it applies).
The ten steps
- Understand the docs and audit what exists.
- Proposal: what, why, and why no existing component fits.
- Foundations as tokens.
- Motion and imagery spec.
- Concept prototype.
- Design spec, the definition of ready.
- Implement per stack, from tokens only.
- Verify: accessibility, visual regression, states, motion.
- Document and release; reference integrity.
- Adopt and maintain, with a maturity status.
Design-first for anything users see. Shipping before full compliance is allowed only as draft, never stable.
How to run it
- At plan time, run step 1 before proposing anything: read the product DESIGN.md, then
propagate design depsonce it ships (until then: not built yet, #243; audit by hand). - Do steps 2 to 6 in the plan, 7 to 8 in the build, 9 to 10 before calling the work done.
- For the stack in front of you, Read its section. For a stack with no section, the step is done with the stack's own tools, "when reached".
- A name you write in a design doc goes in backticks.
curate-docs reportresolves them against the code and saysSTALEfor a name that does not exist. A name designed but not built goes in the doc's frontmatterdesigned-not-built:list, and leaves it when built.
Read sections/workflow.md for each step's check and the definition of done.
04 同仓库更多 Skills
propagate
暂无简介
curate-docs
Use when a repo's markdown docs have drifted — orphaned or unreferenced docs, plans nobody triaged, an archive nobody drained, a docs/ directory nobody can navigate, stale architecture or spec docs, broken links between docs, "which doc is current", "why does this doc exist", or before answering an architecture or methodology question from docs you have not verified are current.
propagate
Use when a change to one file needs to reach files that must move with it — across branches, worktrees, or repos. Triggers on "/propagate", "propagation status", "drain propagation", "what depends on this", "did anything drift", "what did I forget to update", a red or unexplained propagate check, or any reference to PROPAGATION_LEDGER or a .propagates.yml sidecar.