Package
derive a design-system package from an existing codebase
npx -y skills add tommylower/asbuilt --skill packageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this package when extending or auditing {{project_name}} UI. It captures the derived tokens, component grammar, architecture, and platform mapping from the shipped code.
SKILL.md
1.5 KB, 292 tokens by cl100k_base, as published. Nobody here has run it
{{project_name}} Design System
Use this package before creating or modifying UI for {{project_name}}.
Read First
- references/tokens.md
- references/architecture.md
- references/components.md
- references/platform-mapping.md
Thesis
{{design_thesis}}
Hard Rules
- Code is the source of truth.
- New components enter through the component intake rule in
references/components.md. - Use existing semantic tokens before proposing new ones.
- Reuse a behavior floor when one exists.
- Do not copy skin from external references.
- Record unresolved decisions instead of hiding them.
Anti-Patterns Seen In The Code
- {{anti_pattern}}
Component Intake
Before adding a new component, classify it:
composition: an arrangement of existing partsheadless-floor: behavior exists in a proven floor; skin it with project tokensnovel: no floor exists; write the full state machine
Completion Bar
A UI change conforms only when:
- it uses semantic tokens or records a proposed token
- it names the component bucket
- every state is represented
- motion numbers come from this package or the code
- build/lint/test commands listed in
AGENTS.mdpass, or failures are documented