design-system-compiler
Skill1 starsChanged 18 days agoMITView on GitHub
Use only when the user explicitly requests design-system-compiler or a requested skill workflow requires it. Compile an owner-approved UI design into the frozen `docs/design/design-system.md` and `docs/design/design-system.json` pair plus its derived `design-system-preview.html`. Run it after Visual Approval and Design System Need Gate: required. It freezes tokens, primitives, components, motion, responsive rules, and states; it does not choose product, stack, layout, or visual direction.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- delivery-harnessSkill
- growth-reviewSkill
- product-definition-builderSkill
- ui-design-builderSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run only on the user's explicit request, continuation, or a required dependency of that requested skill workflow.
- Distinctive: line 29
Read the owning section before its matching action.
- Distinctive: line 31
Before compile or update, read Compilation Skills Gate, Inputs And Ownership,
- Distinctive: line 32
Before validate or reuse, read Compilation Skills Gate, Inputs And Ownership, and
- Distinctive: line 33
Before publication, read Output Rules and Artifact Lifecycle.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design System Compiler
Run only on the user's explicit request, continuation, or a required dependency of that requested skill workflow. A matching task, installation, discussion, source edit or existing project artifact does not activate it. Required checks and dependencies stay within the requested outcome; a new top-level stage needs an explicit request.
Installed Commands
Resolve <design-system-compiler-skill-root> and logical script paths as Installed Commands states.
Purpose
At every invocation, run the entry checklist. Compile the approved persona-dependent component states without creating accounts or changing requirements. Rechecking or rebuilding the same approved direction is technical verification, not a reason to repeat its approval; changed direction remains an upstream gap.
Turn an approved UI direction into two binding reusable UI sources:
design-system.mdfor the selected visual direction and short human-facing rules; anddesign-system.jsonfor machine-readable tokens, primitives, closed variants, product components, motion, responsive rules, source paths, and the state matrix.
Invoke it only when Product Definition Approval and the Stack Decision Checkpoint are approved and docs/design/ui-design.md records the approved complete HiFi decision plus Design System Need Gate: required. A full ui-design/3 package requires it and names Package action: compile|update|reuse; under Delivery profile: mvp the Need Gate may record not_required, and then the compiler does not run. The compiler respects the approved component foundation and styling approach; it never changes stack by implication. PRD.md owns product behavior, while ui-design-builder owns ui-design.md and the HiFi target; a historical wireframe remains legacy evidence only. Do not duplicate or change those contracts, implement production UI, or create Harness PLAN/RUN state.
Stage Routing
Read the owning section before its matching action. Domain and direction guidance stays conditional.
- Before compile or update, read Compilation Skills Gate, Inputs And Ownership, Workflow, Validation, and Output Rules.
- Before validate or reuse, read Compilation Skills Gate, Inputs And Ownership, and Validation.
- Before publication, read Output Rules and Artifact Lifecycle.
- For an unresolved domain decision or reference route, read Reference Routing. Do not reselect the stack or visual direction.
Entry Boundary
- Product Definition Approval and the Stack Decision Checkpoint must be approved before compilation.
- A
ui-design/3package compilesdesign-system/4; aui-design/2package compilesdesign-system/3only when its Design System Need Gate is required. Both consume the complete approvedui-hifi/2package. PRD.mdowns product behavior;ui-design-builderownsui-design.mdand the approved HiFi target. The compiler owns the design-system pair and its derived HTML.frontend-designis required without a fallback; compilation does not reopen direction. Product or stack changes return upstream.- Compilation derives approved consequences only. Validation includes mutating
--writecommands and does not auto-authorize publication. - Script- or state-driven motion uses
ds-showcase/2source-runtime rows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

