🔍
FrontendMarkdown

Design Debt Audit

by Owl-Listener

Design Debt Audit is a Frontend skill for Claude Code, published by Owl-Listener in designer-skills.

2.1K stars335 forkson Owl-Listener/designer-skillsAdded 2026/08/18+2% in starsRepository updated 2026/08/08
View source on GitHubDownload repo ZIP
agenticagentic-aiaiai-toolsclaude-codedesign-systemdesign-systemsprompt-engineeringskillsux-design
Install in seconds
Install Design Debt Audit
Copy Design Debt Audit into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-debt-audit ~/.claude/skills/design-debt-audit

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/Owl-Listener/designer-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
design-ops/skills/design-debt-audit/SKILL.md in Owl-Listener/designer-skills
Installs to
~/.claude/skills/design-debt-audit
Collection
One of 25 skills cataloged from this repository
Category
Frontend — 567 skills

What Design Debt Audit does

Design Debt Audit inventories and prioritizes accumulated design inconsistencies across a product so teams can plan remediation. Use it before redesigns or when UI drift, accessibility gaps, and structural debt have built up.

Design Debt Audit is cataloged under Frontend on DirSkills. Design Debt Audit comes from a repository tagged agentic, agentic-ai, ai, ai-tools and claude-code.

Documentation

README

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

Frequently asked about Design Debt Audit

  • What else does Owl-Listener publish alongside Design Debt Audit?

    Design Debt Audit is one of 25 skills that DirSkills catalogs from Owl-Listener/designer-skills, the repository it ships in. Its siblings there include Accessibility Audit, Affinity Diagram and Card Sort Analysis. Each one is a separate skill with its own page in this directory, installs the same way Design Debt Audit does, and is maintained by Owl-Listener in that same repository. The rest of the collection is listed on the Owl-Listener/designer-skills page.

  • How does Design Debt Audit compare to other Frontend skills?

    Design Debt Audit ranks #238 by stars among the 567 Frontend skills in this catalog. The most-starred ones next to it are Angular Developer, Android Clean Architecture and Accessibility. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Design Debt Audit against them. Open each page to compare what they document and how they install.

More from Owl-Listener/designer-skills

Design Debt Audit is one of 25 skills cataloged on DirSkills from Owl-Listener/designer-skills.

See all 25 skills →
♿
2w ago

Accessibility Audit

Accessibility Audit examines an existing interface against WCAG criteria, identifies barriers, and provides severity-rated findings with remediation steps. Use it when you have a design or build to assess now, not for planning future assistive-technology testing sessions.
Quality
2.1K335
🗂️
2w ago

Affinity Diagram

Affinity Diagram clusters qualitative data points into themes and insight statements. Use it when synthesising across multiple sessions or sources to create a structured hierarchy with supporting evidence.
Data
2.1K335
🗂️
2w ago

Card Sort Analysis

Card Sort Analysis analyzes open or closed card sort results into a proposed grouping and label set. Use it after running a sort study to inform navigation and content organization.
Frontend
2.1K335
🧩
2w ago

Component Spec

Component Spec specifies one component's props, states, variants, accessibility, and usage rules. Use when defining a library component.
Frontend
2.1K335
💬
2w ago

Design Critique

Design Critique facilitates structured team critique sessions, guiding framing, feedback rules, and actionable outcomes. Use it when running a session with people in the room to keep feedback constructive and aligned.
Frontend
2.1K335
📊
2w ago

Design Impact Reporting

Design Impact Reporting measures and communicates design's contribution to business and user outcomes in stakeholder language. Use it when reporting results upward to leadership or cross-functional partners.
Data
2.1K335

More Frontend skills

Design Debt Audit is one of 567 Frontend skills cataloged on DirSkills, ranked #238 by stars among them.

Browse all Frontend skills →
🅰️
3w ago

Angular Developer

Angular Developer generates Angular code and provides architectural guidance for Angular projects. Use it for creating projects, components, or services, or for best practices on reactivity, forms, DI, routing, SSR, accessibility, animations, styling, testing, and CLI tooling.
Frontend
239.8K36.4K
🏗️
3w ago

Android Clean Architecture

Android Clean Architecture provides patterns for structuring Android and Kotlin Multiplatform projects, covering module boundaries, UseCases, Repositories, and data layer with Room, SQLDelight, and Ktor. Use it when setting up layered architecture in Android or KMP projects.
Frontend
239.8K36.4K
♿
3w ago

Accessibility

Accessibility helps design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards for keyboard, contrast, and screen-reader support. Use it when building or auditing UI that must meet WCAG 2.2 Level AA or reviewing changes for accessibility.
Frontend
239.8K36.4K