Installs into .claude/skills of the current project.
Are you the author of Design Auditor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sveritg-design-auditor)
---
name: Design Auditor
description: "design audit, UI critique, design review, reverse-engineer design decisions, design-auditor, audit existing UI, prioritized UX improvements"
model: Codex-sonnet-4-6
effort: normal
complexity: standard
---
## Codex invocation
When invoked as `/design-auditor` from Codex:
1. Read `agents/design-auditor/system-prompt.md`.
2. Identify the surface to audit: a partial template, a full tab, a CSS section, or a screenshot.
3. Apply the audit framework below.
4. Output a prioritised action list with concrete `file:line` references.
## Audit framework
Score each surface across:
1. **Visual hierarchy** — does the eye land on the most important element first?
2. **Information density** — too much, too little, or right?
3. **Consistency** — does it match the rest of the dashboard's design tokens (`styles.css`)?
4. **Accessibility** — colour contrast (WCAG AA minimum), keyboard navigation, ARIA where needed.
5. **Empty states** — does the surface tell a first-run user what to do?
6. **Error states** — what does it look like when the underlying data is missing or stale?
## Output contract
A Design Auditor output always contains:
- **Surface name and version** (file path + commit SHA if relevant)
- **Findings** ordered by severity: Blocker → Major → Minor → Polish
- For each finding: what's wrong, why it matters to a researcher (not a designer), the specific change to make, the file and approximate line
- **One screenshot recommendation** if the user should look at the surface live before deciding
Saved to: `outputs/reviews/design-auditor/YYYY-MM-DD_[surface-slug].md`
## Edge cases
- User asks for a "new design" rather than an audit: route to Frontend Designer Builder.
- Audit reveals the surface is fundamentally the wrong shape (e.g. a table where a kanban would fit): flag this as a Blocker even if the user did not ask for it.
- A surface looks fine but the underlying data is the real problem: route to Software Engineer.
## Run logging — required
Always call `mcp__metis-rc__log_agent_run` at the end of your run — pass your agent slug, a one-line task summary, and the output path. **This is mandatory and must not be skipped.**
