ds
Skill8 starsChanged 3 months agoMITView on GitHub
Which design-system skill to reach for — routes between /ds-doctor, /ds-plan, and /ds-drift.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Before a feature: /ds-plan <ticket|design> in the app repo.
- Very specific: line 40
After generation: /ds-drift on the branch (or batch across parallel branches).
≈ “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
ds — the router
Three sibling skills police design-system conformance. All are report-only — they write verdicts, maps, and plans, never code. This skill only routes; when the user's intent matches a row below, tell them the command (or invoke the named skill if they ask you to proceed).
/ds-doctor → audits the DS itself, writes ds/MANIFEST.md + ds/tokens.json
└→ everything below reads it
/ds-plan → classifies a feature's UI against the DS before it is built
├→ Covered / Composable → exact props, to the generators
└→ Extension / Net-new → DS work items → the DS backlog
generators → N branches of AI work
/ds-drift → reviews finished code for DS conformance
├→ reviews: verdicts + specs → back to the generators
└→ plans: self-contained specs → cheap executor, or --issuesReach for
/ds-drift— the work exists and needs judging: gate a branch or PR, batch-review parallel agent branches, sweep a repo for token/adoption/a11y drift, audit a DS version upgrade, orreconcilethe backlog./ds-plan— the work doesn't exist yet: a ticket, spec, or design needs classifying against the DS, sequencing into DS-repo vs app-repo waves, or a quick "do we have something for this?" (element)./ds-doctor— the design system itself is the subject: is it enforceable, where are the doc/token/policy gaps, and generate or refresh the conformance manifest (runmanifestafter every DS release).
The loop
- In the DS repo:
/ds-doctor, fix blockers,/ds-doctor manifest, publishds/with the package. - Before a feature:
/ds-plan <ticket|design>in the app repo; ship Wave 0 DS work, hand the map to the building agent. - After generation:
/ds-drifton the branch (orbatchacross parallel branches); feed the review back to the generator. - Periodically:
/ds-drift sweepfor the baseline,coveragefor the trendline,reconcileto keep the record honest.
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.

