design-audit

Scans UI code against a design system contract and reports deviations as structured findings.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill design-audit-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-audit
Source: https://github.com/pnewsam/skills/tree/main/archive/design-audit
Command: npx skills add https://github.com/pnewsam/skills --skill design-audit-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI codebases drift away from their documented design system over time, and manually comparing every component against the contract is slow and error-prone. This Skill audits code against docs/DESIGN_SYSTEM.md and produces a structured, actionable list of deviations. ## Core Features & Use Cases - Contract-Based Scanning: Checks spacing, color, typography, component patterns, and layout against the values defined in docs/DESIGN_SYSTEM.md. - Severity Classification: Labels each finding as a violation, drift, or inconsistency so fixes can be prioritized. - Structured Audit Artifact: Writes a findings report to docs/tmp/design-audit-{scope}.md with file paths, line numbers, current values, expected values, and concrete fixes. - Use Case: Audit the src/features/dashboard/ directory to find every raw hex color, off-scale spacing value, and non-standard border radius, then hand the report to a fix workflow. ## Quick Start Audit the dashboard components against docs/DESIGN_SYSTEM.md and write a findings report. Note: this Skill is deprecated; prefer the current ui-* and design-* reference skills unless you explicitly need the legacy docs/DESIGN_SYSTEM.md contract workflow.

Frequently Asked Questions about design-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UI code against a design system?▼

Read the design system contract first, then scan each component in scope for spacing, color, typography, component pattern, and layout deviations. Record each finding with its file location, current value, expected value, and severity so fixes can be applied directly.

What does a design audit check for in frontend code?▼

It checks off-scale spacing values, raw hex colors instead of tokens, font sizes and weights outside the typography scale, non-standard border radius or shadows, and layout structures that diverge from documented conventions.

Can I run a design audit without a design system document?▼

No. The audit requires an existing docs/DESIGN_SYSTEM.md contract defining the expected values. Without it, there is no standard to measure against, so you should create the design system document first.

How are design audit findings prioritized?▼

Findings are classified into three severities: violations (raw values where tokens exist), drift (clear mismatches with the system), and inconsistencies (possibly intentional variations). Fix violations first, then drift, then inconsistencies.

What are the limitations of a design system audit?▼

It only flags deviations from the documented contract, not aesthetic improvements, and it cannot judge whether a deviation was intentional. Sections where the contract is silent produce ambiguous findings that require contract updates.