component-audit
Skill8 starsChanged 7 months agoMITView on GitHub
Component consistency audit covering state coverage, hierarchy, and patterns. Use when the user asks for a component audit, a component review, or a check of UI consistency.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- murphytrueman/design-system-opstheir own version, first seen Sep 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- murphytrueman/design-system-ops★ 197same name
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- a11y-auditSkill
- color-auditSkill
- design-auditSkill
- design-checklistSkill
- design-compareSkill
- design-scoreSkill
- design-tokensSkill
- flow-auditSkill
- layout-auditSkill
- refactor-planSkill
- style-directionSkill
- theme-builderSkill
- type-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 13
Check state coverage per component type
- Distinctive: line 16
Check empty, loading, and error states
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
/component-audit: Component Consistency Audit
Focused audit of UI component quality using the component-reviewer agent.
Flow
- Inventory all UI components (Glob for component files)
- Check state coverage per component type
- Evaluate button hierarchy
- Audit form quality
- Check empty, loading, and error states
- Assess cross-component consistency
- Output findings with improvement suggestions
Output
- Component inventory
- State coverage matrix (component x state)
- Button hierarchy assessment
- Form quality score
- Missing states per component
- Consistency findings
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.