Design Debt Audit logo

Design Debt Audit

CommunityPopular
Owl-Listener
design-debt-audit

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).

Overview

PublisherOwl-Listener
Repositorydesigner-skills
Skill namedesign-debt-audit
Stars
2.7K
Forks
384
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Design Debt Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p .claude/skills
cp -r /tmp/designer-skills/design-ops/skills/design-debt-audit .claude/skills/design-debt-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design Debt Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design Debt Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design Debt Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 questions

What does the Design Debt Audit AI skill do?

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).

Why use Design Debt Audit on TypingMind?

Because you install it once and use it with any model. Design Debt Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design Debt Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-debt-audit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Design Debt Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design Debt Audit?

As many as you like. As long as a model supports skills, you can use Design Debt Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design Debt Audit AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
obra logo

Verification Before Completion

obra
CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

25.8K
288.1K
Instructions
View
obra logo

Writing Plans

obra
CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

25.8K
288.1K
1 files
View
mattpocock logo

Ask Matt

mattpocock
CommunityPopular

Ask which skill or flow fits your situation. A router over the skills in this repo.

22.3K
264.4K
2 files
View
mattpocock logo

Code Review

mattpocock
CommunityPopular

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

22.3K
264.4K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇