coreyone Design System Audit Checklist ✅
When to use
Use this skill when the task is primarily about design and this guidance is the most relevant operating rule set.
When not to use
Do not use this skill as the primary guide when another skill has a tighter domain fit for the requested output.
Trigger cues
- Request explicitly references
design-system-rulesor this source file. - Request language includes terms like: design, system, rules.
- Keywords include: IA, usability, responsive layout, design system, aesthetic direction, motion.
Routing boundary
- Primary for UX architecture, visual hierarchy, responsiveness, and interface behavior.
- Do not use as primary for backend architecture, threat modeling, or release operations.
Inputs required
- Goal or task request
- Current constraints (time, scope, platform, risk)
- Existing artifacts (code, docs, screenshots, metrics) when available
- Source of truth:
subagents/rules/design/design-system-rules.md
Instructions
- Read references/source.md first.
- Extract the non-negotiable rules and translate them into a short execution checklist.
- Apply the checklist to the current task, produce concrete outputs, and avoid abstract recommendations.
- Validate outcomes with evidence (tests, screenshots, logs, diffs, or written audit findings).
- Record decisions and tradeoffs so another engineer can continue without re-discovery.
Output format
- Primary decision/output: User flow clarity, interaction model, and visual system constraints.
- Summary: one-paragraph decision or result
- Actions: compact checklist with owners and status
- Evidence: links/paths to artifacts proving completion