본문으로 건너뛰기
cccskills
무료GitHub에 공개

design-debt-audit

Audit accumulated design inconsistencies across a product, including visual differences, navigation problems, accessibility gaps, and outdated documentation. Classify issues by severity, frequency, and repair effort, then create a prioritized improvement plan and an ongoing issue register.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Inventory inconsistencies before a major redesign
  • Prioritize design fixes within limited capacity
  • Review navigation after repeated feature additions
  • Track issue owners and progress over time

포함된 파일(1)

  • SKILL.md4.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고