design-debt-audit

Inventory and prioritize accumulated design inconsistencies across a product into a remediation plan.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill design-debt-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-debt-audit
Source: https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-debt-audit
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill design-debt-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Products accumulate design debt over time: inconsistent components, outdated patterns, accessibility gaps, and undocumented decisions. Without a systematic audit, teams cannot see the full scope of the problem or decide what to fix first.

Core Features & Use Cases

  • Debt Classification: Tag every finding by severity, category (visual, structural, accessibility, documentation, implementation), frequency, and effort to fix.
  • Prioritization Scoring: Rank debt items using Severity × Frequency / Effort to surface the highest-harm, lowest-cost fixes first.
  • Living Debt Register: Maintain a tracked register with status, owner, and target resolution, reviewed quarterly rather than treated as a one-time audit.
  • Use Case: Before a major redesign, run a full-product audit to screenshot every screen, catalog inconsistencies against the design system, and produce a remediation roadmap split into quick wins, structural projects, and accessibility fixes.

Quick Start

Audit the checkout flow for design debt and produce a prioritized remediation plan with a debt register.

Frequently Asked Questions about design-debt-audit

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

FAQPage Schema
How do I conduct a design debt audit?

Define the audit scope, screenshot every screen in scope, then classify each finding by severity, category, frequency, and effort to fix. Prioritize items using Severity × Frequency / Effort and produce a remediation plan split into quick wins, structural projects, and accessibility fixes.

What counts as design debt in a product?

Design debt includes visual inconsistencies with the design system, structural patterns that no longer scale, known WCAG accessibility violations, undocumented components and decisions, and implementations using hardcoded values instead of design tokens.

How is a design debt audit different from an accessibility audit?

A design debt audit covers all inconsistency categories including visual, structural, and documentation debt, with accessibility as one category. For dedicated WCAG gap analysis, use a focused accessibility audit instead; for token coverage specifically, use a design token audit.

How do you prioritize which design debt to fix first?

Score each item with Severity × Frequency / Effort to find the highest-harm, lowest-cost fixes. Prioritize Critical accessibility violations, schedule structural projects into the roadmap, and defer low-traffic debt that a planned redesign will resolve.

When should you run a design debt audit?

Run one before starting a major redesign to define the actual scope of work, and maintain the debt register as a living document reviewed quarterly. Include engineering in effort estimation, since designers often underestimate implementation complexity.