Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Install Design Debt Tracker
$ npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers design-debt-tracker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/design-debt-tracker .claude/skills/design-debt-tracker && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-debt-tracker" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker into .claude/skills/design-debt-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-debt-tracker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-trackerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers design-debt-tracker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/design-debt-tracker .agents/skills/design-debt-tracker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-debt-tracker" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker into .agents/skills/design-debt-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-debt-tracker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers design-debt-tracker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/design-debt-tracker .cursor/skills/design-debt-tracker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-debt-tracker" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker into .cursor/skills/design-debt-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-debt-tracker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designpowers.git --path skills/design-debt-tracker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers design-debt-tracker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/design-debt-tracker .gemini/skills/design-debt-tracker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-debt-tracker" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker into .gemini/skills/design-debt-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-debt-tracker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designpowers design-debt-trackerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/design-debt-tracker .github/skills/design-debt-tracker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-debt-tracker" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker into .github/skills/design-debt-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-debt-tracker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designpowers design-debt-tracker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/design-debt-tracker .opencode/skills/design-debt-tracker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-debt-tracker" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker into .opencode/skills/design-debt-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-debt-tracker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
design-debt-tracker- GitHub stars
- 251
- Token cost
- ~2.2k tokens
- SKILL.md length
- 950 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
- Works in 5 steps: Capture Debt (After Review) → Review Debt (At Project Start or Before… → Escalation Check → …
- Review produces deferred findings
- SKILL.md covers Why This Exists, When to Use, The Register and Process, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Debt Tracker is an agent skill from Owl-Listener/designpowers. Use when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration. Maintains a living register of design debt — the minor issues, future-iteration notes, and conscious compromises that accumulate across a project
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- Review produces deferred findings
- Checking accumulated design compromises
- Deciding what to address in the next iteration
Example prompts
- “/design-debt-tracker”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cb00757. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design Debt Tracker loads about 2.2k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 950 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 950 words, ~2,183 tokens.
Download SKILL.mdSave it as
.claude/skills/design-debt-tracker/SKILL.md (or your agent's skills folder).- name
- design-debt-tracker
- description
- Use when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration. Maintains a living register of design debt — the minor issues, future-iteration notes, and conscious compromises that accumulate across a project
Design Debt Tracker
Design debt is every conscious compromise the team makes and every minor issue deferred to "next time." Like technical debt, it compounds. Unlike technical debt, most teams don't track it — so it disappears into the gap between what was shipped and what was intended.
This skill maintains a living register that captures debt as it's created, tracks it across iterations, and surfaces it when decisions are being made.
Why This Exists
The design-critic classifies findings as Critical, Major, Minor, and Note. Critical and Major get fixed. Minor and Note get a shrug and "fix if time allows." They rarely get fixed because no one remembers them.
The accessibility-reviewer does the same — Minor issues with specific fixes that never happen because they're buried in a report that no one reopens.
Every "fix if time allows" is a promise to a persona. This skill makes those promises visible.
When to Use
- After critique — when the design-critic produces Minor or Note findings that won't be fixed this round
- After accessibility review — when the accessibility-reviewer flags Minor issues that are deferred
- After a fix round — when not all issues were addressed and some were consciously deferred
- At project start — to review accumulated debt from previous iterations
- Before planning — to decide which debt items to address in the next cycle
- On user request — "show me the design debt" or "what did we defer?"
The Register
Design debt lives in a ## Design Debt Register section in design-state.md. One register per project. It persists across iterations.
Register Format
## Design Debt Register
_Items: [count] | Critical: [count] | Oldest: [date]_
| ID | Date | Source | Severity | What | Who is affected | Suggested fix | Status | Notes |
|----|------|--------|----------|------|----------------|---------------|--------|-------|
| DD-001 | 2025-01-15 | design-critic | Minor | Settings form shows all fields at once — cognitive load | Persona: Jamie (cognitive disability) | Progressive disclosure with sections | Open | Deferred from v1 — setup is one-time flow |
| DD-002 | 2025-01-15 | accessibility-reviewer | Minor | Category colour strips lack icon backup | Users with colour vision deficiency | Add icon per category alongside colour | Open | |
| DD-003 | 2025-01-16 | design-critic | Note | Empty state illustration is placeholder | All users | Commission illustration that matches brand | Open | Low priority — functional without it |
| DD-004 | 2025-01-15 | accessibility-reviewer | Minor | Toast notifications auto-dismiss before screen reader finishes | Screen reader users | Extend timeout to 8s or add persistent log | Resolved | Fixed in v1.1 |Field Definitions
| Field | What goes here |
|---|---|
| ID | Sequential identifier (DD-001, DD-002, ...). Never reuse IDs |
| Date | When the debt was recorded |
| Source | Which agent or review identified it (design-critic, accessibility-reviewer, design-lead, user, etc.) |
| Severity | The original severity classification: Minor or Note (Critical and Major should be fixed, not deferred) |
| What | Specific description of the issue — not "needs improvement" but "form shows 12 fields at once" |
| Who is affected | Which personas or user groups bear the cost of this debt. Be specific |
| Suggested fix | Actionable recommendation from the original review |
| Status | Open, Resolved, Accepted, or Escalated |
| Notes | Why it was deferred, context, related items |
Status Definitions
| Status | Meaning |
|---|---|
| Open | Identified, not yet addressed. This is a promise to come back |
| Resolved | Fixed in a subsequent iteration. Record which iteration |
| Accepted | Consciously decided this is not worth fixing. Requires user approval and a rationale |
| Escalated | Was Minor, but accumulated evidence or changing context makes it Major. Needs attention |
Process
Step 1: Capture Debt (After Review)
When the design-critic or accessibility-reviewer completes a review:
- Read their findings
- Identify all Minor and Note severity items that will NOT be fixed in this round
- For each deferred item, create a register entry with all fields populated
- Append to the Design Debt Register in
design-state.md - Update the summary line (item count, critical count, oldest date)
Do not capture items that are being fixed. The register tracks debt, not the fix list. If it's getting fixed now, it doesn't belong here.
Step 2: Review Debt (At Project Start or Before Planning)
When starting a new iteration or planning cycle:
- Read the current Design Debt Register
- Check for escalation triggers (see below)
- Present a debt summary to the user:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DESIGN DEBT SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Open items: [count]
By severity: [X] Minor, [Y] Note
Oldest unresolved: [date] ([age])
ACCESSIBILITY DEBT:
• [count] items affecting users with disabilities
• Most affected: [persona or user group]
TOP CANDIDATES FOR THIS CYCLE:
1. [DD-XXX] [description] — [why now]
2. [DD-XXX] [description] — [why now]
3. [DD-XXX] [description] — [why now]
ESCALATED (was Minor, now needs attention):
• [DD-XXX] [description] — [escalation reason]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━- Ask the user which items to include in the current cycle's plan
- Items the user selects get added to the design plan as tasks
Show full SKILL.md (382 more words)Show less
Step 3: Escalation Check
Debt items should be escalated from Minor to Major when:
| Trigger | Example |
|---|---|
| Age | Item has been Open for 3+ iterations without resolution |
| Accumulation | Multiple debt items affect the same persona or the same screen |
| Context change | A new persona or use case makes the issue more impactful |
| User complaint | The user or stakeholder mentions the issue independently |
| Compound effect | Two Minor items together create a Major experience gap |
When escalating:
- Change Status to "Escalated"
- Add a note explaining why
- Flag it in the debt summary
- Present it to the user as needing attention
Step 4: Resolve Debt
When a debt item is fixed:
- Update Status to "Resolved"
- Add a note: "Fixed in [iteration/date] by [agent]"
- Add the resolution to the Decisions Log in
design-state.md - Do NOT delete the row — resolved items are history
Step 5: Accept Debt
When the user consciously decides an item is not worth fixing:
- Confirm with the user: "This affects [personas]. Are you sure you want to accept this?"
- Update Status to "Accepted"
- Add the user's rationale in Notes
- Add the acceptance to the Decisions Log
Accessibility debt requires explicit acknowledgement. If a debt item affects users with disabilities, the user must explicitly accept the trade-off. Do not silently accept accessibility debt.
Integration
- Receives from:
designpowers-critique(Minor/Note findings),accessibility-reviewer(Minor findings),verification-before-shipping(deferred items) - Feeds into:
writing-design-plans(debt items become plan tasks),design-retrospective(debt trends are retrospective data) - Updates:
design-state.md(Design Debt Register section) - Called by:
using-designpowers(after reviews, at project start, on user request)
Anti-Patterns
| Pattern | Why It Fails |
|---|---|
| Capturing Critical issues as debt | Critical issues block access. They get fixed now, not tracked for later |
| Deferring the same item 3+ times | That's not debt management, that's avoidance. Escalate it |
| Accepting accessibility debt without user acknowledgement | Accessibility compromises affect real people. The user decides, not the system |
| Deleting resolved items | Resolved items are history. They show the team addresses its promises |
| Not reviewing debt at project start | Starting a new iteration without checking old promises means those promises are broken |
| Tracking everything | Not every observation needs tracking. Notes that are genuinely informational ("consider X someday") can stay in the critique report. Debt is for specific, actionable items that affect specific people |
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/design-debt-tracker of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Design Debt Tracker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Debt Tracker this skillOwl-Listener/designpowers | 251 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Design State
Owl-Listener/designpowers
A skill your agent uses when any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to.
Related
Categories
Questions about Design Debt Tracker
What does Design Debt Tracker do?
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration. Design Debt Tracker is an agent skill from Owl-Listener/designpowers. Use when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
When should I use Design Debt Tracker?
Design Debt Tracker fits situations like: review produces deferred findings; checking accumulated design compromises; deciding what to address in the next iteration.
How do I install Design Debt Tracker in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a claude-code`. Or copy the skill folder (skills/design-debt-tracker in Owl-Listener/designpowers) into .claude/skills/design-debt-tracker in your project. Claude Code loads it when a task matches its description.
How do I install Design Debt Tracker in Codex?
Run `npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a codex`. Or copy the skill folder (skills/design-debt-tracker in Owl-Listener/designpowers) into .agents/skills/design-debt-tracker in your project. Codex loads it when a task matches its description.
Can I use Design Debt Tracker in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designpowers --skill design-debt-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-debt-tracker, .gemini/skills/design-debt-tracker, .github/skills/design-debt-tracker and .opencode/skills/design-debt-tracker in your project.
What does Design Debt Tracker need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Debt Tracker is instructions for the agent only.
Does Design Debt Tracker access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Design Debt Tracker safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Design Debt Tracker use?
Design Debt Tracker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design Debt Tracker use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design Debt Tracker?
Skills that share tags, products or a category with Design Debt Tracker: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Debt Tracker?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.