command-interface-design-audit
Check existing code against your design system for spacing, depth, color, and pattern violations. Use this skill only when the user explicitly asks to invoke.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
interface-design audit
Usage
/audit <path> # Audit specific file/directory
/audit # Audit common UI paths
What to Check
If .vscode/interface-design/system.md exists:
-
Spacing violations
- Find spacing values not on defined grid
- Example: 17px when base is 4px
-
Depth violations
- Borders-only system → flag shadows
- Subtle system → flag layered shadows
- Allow ring shadows (0 0 0 1px)
-
Color violations
- If palette defined → flag colors not in palette
- Allow semantic grays
-
Pattern drift
- Find buttons not matching Button pattern
- Find cards not matching Card pattern
Report format:
Audit Results: src/components/
Violations:
Button.tsx:12 - Height 38px (pattern: 36px)
Card.tsx:8 - Shadow used (system: borders-only)
Input.tsx:20 - Spacing 14px (grid: 4px, nearest: 12px or 16px)
Suggestions:
- Update Button height to match pattern
- Replace shadow with border
- Adjust spacing to grid
If no system.md:
No design system to audit against.
Create a system first:
1. Build UI → establish system automatically
2. Run /extract → create system from existing code
Implementation
- Check for system.md
- Parse system rules
- Read target files (tsx, jsx, css, scss)
- Compare against rules
- Report violations with suggestions
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!