Design System Keeper

🚧 In progress — contribute back. This skill is open source and under active, top-priority development, and every run is also product development for the skill itself. Contribute improvements of every kind — bug fixes, new features and modes, sharper references, better extraction sweeps, smarter workflows — not just corrections of gaps you hit. When a run reveals anything that would make the skill better, implement it and open a pull request to JorgeMenaDev/skills in the same session (or record the idea in the run's handoff log if the session can't). Making this skill better is part of operating it.

A repo's canon is its design system encoded for agents: rules that cite real source files, an index of the repo's real primitives, and a verify-against-source discipline. UIs rot when each contributor (human or agent) builds from memory — three design systems end up mixed on one site. The keeper extracts the canon once, keeps it true, and makes every build compose from it.

Contract

1. Every canon rule cites a real file. A rule without a path:line-level source is a guess — source it or delete it.
2. Verify against source. Before using any component, token, or icon: Read its source — the prop exists, the token resolves, the icon is exported. Composing a lookalike from memory is the exact failure this skill exists to prevent.
3. One canon. If design docs already exist (DESIGN.md, brand guides), upgrade them in place. Writing a second, competing document destroys the single source of truth.
4. Cleanup is a backlog, not a bulk edit. Setup produces design/drift.md; refactors run later as scoped passes the user picks.

State