design-system-audit
Skill0 starsChanged 3 months agoMITView on GitHub
Audit a design system for token, component, accessibility, documentation, and adoption inconsistencies.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- jrpease/throughlinetheir own version, first seen Oct 11, 2026
- henrique-simoes/Istaratheir own version, first seen Sep 27, 2026
- shashanksdesign/drifttheir own version, first seen Sep 13, 2026
- Gaurav890/everything-agentic-engineeringtheir own version, first seen Sep 13, 2026
- brayandiazc/project-starter-template-en-aitheir own version, first seen Sep 7, 2026
Used with
Projects with it also use design-tokens, accessibility-audit and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ilikescienceSkilldesign-tokens
Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.
Also in 3 projects that use this
GitHubSkillaccessibility-audit
Audits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.
Also in 4 projects that use this
AnthropicSkilldesign-critique
Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- jrpease/throughline★ 80same name
- brayandiazc/project-starter-template-es-ai★ 15same name
- henrique-simoes/Istara★ 15same name
- brayandiazc/project-starter-template-en-ai★ 2same name
- shreyas-makes/agent-skills★ 2same name
- Gaurav890/everything-agentic-engineering★ 1same name
- InsightStudio-2026/agent-assets★ 1same name
- jpoindexter/theft-kit★ 1same name
- toribryan/design-skills★ 1same name
- aiuxmasters/agentic-design-tools★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessible-interfaceSkill
- color-and-contrastSkill
- design-contextSkill
- forms-and-validationSkill
- interaction-and-motionSkill
- interface-critiqueSkill
- layout-and-spacingSkill
- loading-empty-error-statesSkill
- responsive-designSkill
- typographySkill
- visual-hierarchySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
Distinctive
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 12
Do not infer adoption from a component directory or documentation site.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design System Audit
Evaluate whether a design system is coherent, usable, accessible, and adopted in product code. Use this for a bounded audit of tokens, components, patterns, documentation, governance, and real consumption.
Do not infer adoption from a component directory or documentation site. Do not rewrite the system during diagnosis, and do not treat every product exception as a defect.
Workflow
- Define the audited surfaces, versions, repositories, consumers, and evidence limits.
- Inventory foundations, semantic tokens, components, variants, states, patterns, documentation, release process, and ownership.
- Trace representative product usages. Compare documented APIs and design guidance with shipped code, visual outcomes, and accessibility behavior.
- Find duplication, orphaned tokens, ambiguous naming, variant explosion, missing states, composition gaps, inaccessible defaults, and undocumented escape hatches.
- Separate system defects, adoption defects, migration debt, and justified product exceptions.
- Measure blast radius and migration risk. Prioritize foundations and defaults that affect many consumers before isolated cosmetic differences.
- Recommend keep, clarify, consolidate, deprecate, migrate, test, or research. Define evidence and ownership for each next step.
Output
Return scope and limitations, system health by layer, concrete findings with consumer evidence, risk and reach, a sequenced remediation plan, and metrics or tests that show improvement.
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.