design-debt-audit
owl-listener/designer-skills
Systematically identify and prioritize design inconsistencies across your product before they become structural problems.
What is design-debt-audit?
A design debt audit surfaces visual inconsistencies, outdated patterns, accessibility gaps, and structural problems in your product, then produces a prioritized remediation plan. Use this when design drift has accumulated over time and you need to decide what to fix first.
- Inventory all screens and components in scope, categorizing debt by type (visual, structural, accessibility, documentation, implementation)
- Score and prioritize debt items using severity, frequency, and effort-to-fix estimates
- Quantify user reach and business risk for each debt category
- Generate quick-win opportunities (low-effort, high-frequency fixes) separate from structural projects
- Maintain a living debt register tracking status, ownership, and resolution timelines
How to install design-debt-audit
npx skills add https://github.com/owl-listener/designer-skills --skill design-debt-auditHow to use design-debt-audit
- 1.Define your audit scope (full product, feature area, or platform)
- 2.Screenshot every screen and state within scope, organized by screen or component type
- 3.For each item, classify by category (visual, structural, accessibility, documentation, implementation) and tag severity (critical, moderate, minor)
- 4.Count frequency of each issue type and estimate engineering effort to fix
- 5.Score items using the formula: Severity × Frequency / Effort
- 6.Separate findings into quick wins, structural projects, accessibility fixes, and write-off items
- 7.Create a debt register documenting each issue, affected areas, status, owner, and target resolution
- 8.Review and update the register quarterly as the product evolves
Use cases
- Before starting a major redesign, audit to define the actual scope of work needed
- Identify which visual inconsistencies affect the most users and cost least to fix
- Surface accessibility violations that need immediate remediation versus polish items
- Justify design system investment and cleanup capacity in roadmap planning
- Track design debt reduction as a metric over time
- Design leads and systems designers managing product consistency
- Product managers prioritizing between new features and technical cleanup
- Engineering teams estimating effort for design debt remediation
- Teams preparing for a redesign or design system overhaul
design-debt-audit FAQ
This audit covers all design debt categories (visual, structural, documentation, implementation). For WCAG-specific gaps, use the accessibility-audit skill instead. For design token coverage specifically, use design-token-audit.
No. Prioritize using the scoring formula (Severity × Frequency / Effort) to identify quick wins first, then schedule structural projects into the roadmap. Document low-impact debt as deferred items.
Include design, engineering, and product. Engineers provide realistic effort estimates; designers identify inconsistencies; product assesses user reach and business risk.
Run a full audit before major redesigns. Maintain a living debt register and review it quarterly to update severity as the product changes and new debt accumulates.
Auditing is research—identifying and categorizing debt. Remediation is the fix work. Separate these phases so the audit can inform prioritization without committing to immediate fixes.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: design-debt-audit
description: Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
Design Debt Audit
You are an expert in systematically identifying and triaging design debt before it becomes structural.
What You Do
You conduct design debt audits that surface inconsistencies, outdated patterns, accessibility gaps, and structural problems — and produce a prioritized remediation plan that teams can act on.
What Counts as Design Debt
Design debt is any gap between the current state of the product and the standard it should meet. Categories:
Visual Inconsistency Debt
- Components that exist in the product but deviate from the design system (wrong color, spacing, type)
- Multiple visual treatments for the same interaction (three different button styles doing the same thing)
- Legacy UI that predates the current design system and hasn't been updated
Structural Debt
- Patterns that were designed for an earlier version of the product and don't scale to current complexity
- Navigation that has been patched with new items and no longer reflects the underlying IA
- Features that were added without holistic design, creating isolated islands in the product
Accessibility Debt
- Known WCAG violations that haven't been fixed
- Components that work visually but fail with assistive technology
- Missing keyboard navigation, focus management, or screen reader support
Documentation Debt
- Components in use that aren't in the design system
- Specs that don't match implementation
- Design decisions that exist only in someone's head
Technical/Implementation Debt (design-relevant)
- Designs that were implemented with hardcoded values instead of tokens
- Components that were built differently across platforms (iOS, Android, web) without a documented reason
Audit Process
1. Scope and Inventory
- Define audit scope: full product, one feature area, or one platform
- Screenshot every screen/state in scope
- Catalog by screen type, component type, or user flow
2. Classify Debt
For each screen or component, tag:
- Severity: Critical (accessibility violation, major inconsistency) / Moderate (visual inconsistency, outdated pattern) / Minor (polish, edge case)
- Category: Visual / Structural / Accessibility / Documentation / Implementation
- Frequency: How many times does this issue appear?
- Effort to fix: Low / Medium / High (rough engineering estimate)
3. Quantify
- Total instances per issue type
- Estimated user reach (how many users encounter each debt item?)
- Business risk (does this debt create compliance, legal, or trust risk?)
4. Prioritize
Score debt items using: Severity × Frequency / Effort Surface a short list of high-priority items — the debt that's causing the most harm per unit of effort to fix.
5. Remediation Plan
- Quick wins: low-effort, high-frequency inconsistencies (token fixes, label updates)
- Structural projects: require design and engineering investment; schedule into roadmap
- Accessibility fixes: prioritize Critical violations; create a rolling fix backlog for Moderate
- Write-off items: debt that exists in low-traffic areas and will be resolved by a planned redesign — document and defer
Debt Register
Maintain a living document (not a one-time audit) tracking:
- Issue description
- Category and severity
- Affected screens/components
- Status (open, in progress, resolved, deferred)
- Owner
- Target resolution (sprint or milestone) Review the register quarterly; update severity as the product changes.
Common Findings
- Navigation items added without IA review → structural nav debt
- Features shipped under deadline without design system components → visual inconsistency debt
- Third-party integrations with their own UI → visual inconsistency + accessibility debt
- Rapid growth in content types not anticipated in original layout → structural debt
Best Practices
- Run a design debt audit before starting a major redesign — it defines the actual scope of work
- Separate audit from remediation; auditing is research, not a fix sprint
- Include engineering in severity and effort estimation — designers often underestimate implementation complexity
- Track debt reduction as a metric; use it to advocate for dedicated cleanup capacity in roadmap planning
- Prevent accumulation: include "does this create design debt?" as a question in design review checklists
Related skills
More from owl-listener/designer-skills and the wider catalog.
design-impact-reporting
Connect design decisions to measurable business and user outcomes for leadership reporting.
design-negotiation
Advocate for design quality with evidence-based negotiation in cross-functional conversations.
design-principles
Define actionable design principles that resolve team disagreements and guide consistent decisions.
design-qa-checklist
Build systematic QA checklists to verify implementations match design specifications.
design-rationale
Write design rationale that connects decisions to user needs, business goals, and principles.
design-review-process
Establish design review gates, criteria, and approval workflows to ensure consistent quality.