Skip to main content
skill CX Codex

ds-design-audit — Claude Code skill: what it does, how to install

ds-design-audit audits an interface using evidence from screenshots and code, fixes the highest-impact issues, and verifies the outcome. Runs before shipping UI work or when a screen looks cluttered.

MIT 548 installs ★ 320 updated 2026-10-28

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aicodeking/deepseek-stack --skill ds-design-audit -a claude-code
Open on GitHub

What ds-design-audit does

The skill scores interface elements from one to five with evidence from the screen or code, then fixes the most critical problems in design tokens or shared components. It checks hierarchy, typography, color, spacing, states, accessibility, and copy.

During the audit, the agent captures viewport snapshots at 1440px and 390px widths along with interactive states, applies up to five fixes, and repeats the check once if scores remain low. The audit stops if the target fails to render.

Without a working render of the target file or URL, the skill stops and does not audit from source code alone.

What it helps with

  • score an interface with evidence from code and screenshots
  • fix accessibility breaks and poor visual hierarchy
  • detect banned default styles and generic patterns
  • generate a before and after comparison report

Example prompts for the agent

  • /ds-design-audit Review the main dashboard screen
  • Run /ds-design-audit on the checkout flow
  • Audit the current UI with /ds-design-audit

How to install ds-design-audit

1Skills CLI (Vercel)

npx skills add aicodeking/deepseek-stack --skill ds-design-audit -a claude-code

2Manually: put the files in place

~/.claude/skills/ds-design-audit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ds-design-audit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ds-design-audit

How to install ds-design-audit in Claude Code?

Run npx skills add aicodeking/deepseek-stack --skill ds-design-audit -a claude-code and check ~/.claude/skills/ds-design-audit/SKILL.md.

What does ds-design-audit do?

It evaluates a user interface against design criteria, scores each area with evidence, and applies fixes to tokens and shared components.

What is required to run this skill?

The skill requires the target file or URL to render successfully during the audit process.

Source text

SKILL.md · MIT
---
name: ds-design-audit
description: "Reviews an existing UI with scores based on evidence, then fixes the highest-impact problems. Use when a page or app screen looks generic, cluttered, or unfinished, or before you ship UI work. Run as /ds-design-audit."
---

Score a UI from what is on the screen, fix the worst problems, and show that the fixes work.

## Steps

1. Identify the target file or URL and render it. If it does not render, report this and stop. Do not audit from the source code alone.
2. Take screenshots of the first viewport and the full page at about 1440px and 390px wide. Also capture the hover, focus, empty, loading, and error states where you can.
3. Read the target's code: tokens, fonts, colors, focus styles, media queries, and copy.
4. Give each area a score from 1 to 5. Give one line of evidence for each score: something visible or a line of code.
   - Hierarchy: the main message and action are clear within 3 seconds, and there is one focal point.
   - Typography: the fonts are paired on purpose, the scale is consistent, and the line length and leading are correct.
   - Color: there is one dominant color and one accent, the colors are tokens and not scattered hex values, and there are no decorative gradients.
   - Spacing: the spacing follows a scale, the rhythm is consistent, and the mobile alignment is correct.
   - States: hover, focus, empty, loading, error, and long-content states all exist.
   - Accessibility: the contrast is 4.5:1 or higher, the focus rings are visible, the fields have labels, the touch targets are 44px, and reduced motion is respected.
   - Copy: the copy is specific to the product, with no stock phrases and no placeholder data.
5. Record each banned default that you see: purple-blue gradients, a default font used for display, emoji used as icons, a centered hero with three identical cards, glassmorphism everywhere, gray text on gray, and generic copy.
6. Rank the fixes by their impact on users. Put broken accessibility and an unclear main action first. Put decoration last. For each fix, give the file, the change, and the score that it raises.
7. Apply the top 3 to 5 fixes. Fix the cause in the tokens or in the shared components, not in each instance. Keep the identity, content, and behavior of the product.
8. Take new screenshots at the same widths and in the same states as in step 2. Score each area again and show the before and after scores side by side.
9. If an area still has a score of 2 or lower, or a banned default remains, repeat steps 6 to 8 once. Do not do more than two passes.

## Stop when

- Two passes are complete, or every area has a score of 3 or higher and no banned default remains.
- The report shows the before and after scores, the evidence, the fixes that you applied, and the fixes that you did not apply, each with a reason.

## Rules

- Do not give a score without evidence. If you could not see an area, mark it "not checked" and give the reason.
- Do not change factual copy, prices, claims, or feature behavior without asking.
- If the brief requires a style that this skill would flag, it is not a fault.
- If the UI needs a full rebuild, recommend /ds-design. Do not rebuild it in this skill.

© aicodeking · MIT · aicodeking/deepseek-stack

Similar skills

All skills for Design →

From the same set29

The whole set →
ds-context-reset ds-context-reset is a Claude Code skill that manages context resets for long tasks using a PROGRESS.md tracking file. CX Codex +1 562installs ds-principles Provides engineering principles for design, debugging, and verification. The agent applies them during code structure choices, diff sizing, or when typing /ds-principles. CX Codex +1 557installs ds-blast-radius The ds-blast-radius Claude Code skill checks what a change might break beyond its diff, then tests a key safety claim by running code. Use it to inspect risky or untrusted changes before shipping. CX Codex +1 550installs ds-help ds-help — a Claude Code skill that picks the right deepseek-stack tool for a task and explains how the pack fits together. CX Codex +1 549installs ds-design ds-design — a Claude Code skill for setting a distinct visual direction for frontend work. It runs when creating a page, app screen, or component, and when restyling an existing interface. CX Codex +1 548installs ds-review-loop ds-review-loop — a skill for Claude Code that runs an author and a reviewer in an iterative loop until they agree on the code changes. CX Codex +1 548installs ds-unslop This Claude Code skill rewrites prose and code comments in plain, specific English. It activates while editing replies, docs, READMEs, PR descriptions or commit messages, and on /ds-unslop. CX Codex +1 547installs ds-blueprint Defines types, signatures, and module boundaries before writing code bodies. It triggers on /ds-blueprint or when asked to design the structure first. CX Codex +1 546installs

Project sponsors

Companies that keep this analytics open