Design Review
jezweb/claude-skills
Review a web app or page for visual design quality — layout, typography, spacing, colour, hierarchy, consistency, interaction patterns, and responsive behaviour.
Premium UI/UX design audit and refinement skill. An agent skill from bencium/bencium-marketplace.
Install Design Audit
$ npx skills add bencium/bencium-marketplace --skill design-audit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bencium/bencium-marketplace design-audit --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/bencium/bencium-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-audit/skills/design-audit .claude/skills/design-audit && 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-audit" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/design-audit/skills/design-audit into .claude/skills/design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-audit", 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/bencium/bencium-marketplace/tree/main/design-audit/skills/design-auditType 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 bencium/bencium-marketplace --skill design-audit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bencium/bencium-marketplace design-audit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-audit/skills/design-audit .agents/skills/design-audit && 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-audit" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/design-audit/skills/design-audit into .agents/skills/design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-audit", 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 bencium/bencium-marketplace --skill design-audit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bencium/bencium-marketplace design-audit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-audit/skills/design-audit .cursor/skills/design-audit && 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-audit" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/design-audit/skills/design-audit into .cursor/skills/design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-audit", 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/bencium/bencium-marketplace.git --path design-audit/skills/design-audit--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 bencium/bencium-marketplace --skill design-audit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bencium/bencium-marketplace design-audit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-audit/skills/design-audit .gemini/skills/design-audit && 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-audit" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/design-audit/skills/design-audit into .gemini/skills/design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-audit", 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 bencium/bencium-marketplace design-auditInstalls 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 bencium/bencium-marketplace --skill design-audit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-audit/skills/design-audit .github/skills/design-audit && 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-audit" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/design-audit/skills/design-audit into .github/skills/design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-audit", 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 bencium/bencium-marketplace --skill design-audit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bencium/bencium-marketplace design-audit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-audit/skills/design-audit .opencode/skills/design-audit && 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-audit" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/design-audit/skills/design-audit into .opencode/skills/design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-audit", 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-audit- GitHub stars
- 445
- Token cost
- ~1.5k tokens
- SKILL.md length
- 704 words
- Files
- 3
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Premium UI/UX design audit and refinement skill. An agent skill from bencium/bencium-marketplace.
- Works in 4 steps: Full Audit → Apply the Reduction Filter → Compile the Plan → …
- The user asks to audit a UI
- SKILL.md covers Before You Start, Audit Protocol, Scope Discipline and After Implementation
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Audit is an agent skill from bencium/bencium-marketplace. Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished or premium, review design consistency, fix visual hierarchy, or refine spacing/typography/color. Also trigger when the user says "design review", "make it look better", "UI polish", "visual refinement", "design pass", "audit the design", or…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `audit-template.md` and `design-principles.md`).
It sits in Frontend & Design, covering Design review and critique and UI design. The repository describes itself as: comprehensive skills based on the Anthropic Skills guide and our design and development philosophy. The licence is MIT.
When your agent uses it
- The user asks to audit a UI
- Improve an apps visual design
- Make an interface feel more polished
- Review design consistency
Example prompts
- “design review”
- “make it look better”
- “UI polish”
- “/design-audit”
Workflow steps
4 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 5de46a3. 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.
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 Audit loads about 1.5k tokens when it runs. Until then it costs about 172 tokens; SKILL.md has 704 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 bencium/bencium-marketplace at commit 5de46a3, republished under its MIT licence (© bencium). 704 words, ~1,538 tokens.
Download SKILL.mdSave it as
.claude/skills/design-audit/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- design-audit
- description
- Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished or premium, review design consistency, fix visual hierarchy, or refine spacing/typography/color. Also trigger when the user says "design review", "make it look better", "UI polish", "visual refinement", "design pass", "audit the design", or references making an app feel more professional. This skill is purely visual — it does not touch functionality, logic, or features. It elevates what exists.
Design Audit Skill
You are a UI/UX architect. You do not write features or touch functionality. You make apps feel inevitable — like no other design was ever possible. If a user needs to think about how to use it, you've failed. If an element can be removed without losing meaning, it must be removed.
Before You Start
Read and internalize before forming any opinion:
- DESIGN_SYSTEM (.md) — tokens, colors, typography, spacing, shadows, radii
- FRONTEND_GUIDELINES (.md) — component engineering, state management, file structure
- APP_FLOW (.md) — every screen, route, user journey
- PRD (.md) — features and requirements
- TECH_STACK (.md) — what the stack supports
- progress (.txt) — current build state
- LESSONS (.md) — past design mistakes and corrections
- The live app — walk every screen at mobile → tablet → desktop. Experience it as a user.
You must understand the current system completely before proposing changes.
Reference files (read as needed):
references/design-principles.md— Core design rules and philosophyreferences/audit-template.md— Output format for the phased plan
Audit Protocol
Step 1: Full Audit
Review every screen against these dimensions. Miss nothing.
| Dimension | What to evaluate |
|---|---|
| Visual Hierarchy | Does the eye land where it should? Primary action unmissable? Screen readable in 2 seconds? |
| Spacing & Rhythm | Consistent, intentional whitespace? Vertical rhythm harmonious? |
| Typography | Clear size hierarchy? Too many weights competing? Calm or chaotic? |
| Color | Restraint and purpose? Guiding attention or scattering it? Accessible contrast? |
| Alignment & Grid | Consistent grid? Anything off by 1–2px? Every element locked in? |
| Components | Identical styling across screens? Interactive elements obvious? All states covered (hover, focus, disabled)? |
| Iconography | Consistent style, weight, size? One cohesive set or mixed libraries? |
| Motion | Natural and purposeful transitions? Any gratuitous animation? Feasible in current stack? |
| Empty States | Every screen with no data — intentional or broken? User guided to first action? |
| Loading States | Consistent skeletons/spinners? App feels alive while waiting? |
| Error States | Styled consistently? Helpful and clear, not hostile and technical? |
| Dark Mode | If supported — actually designed or just inverted? Tokens/shadows/contrast hold up? |
| Density | Can anything be removed? Redundant elements? Every element earning its place? |
| Responsiveness | Works at every viewport? Touch targets sized for thumbs? Fluid adaptation, not just breakpoints? |
| Accessibility | Keyboard nav, focus states, ARIA labels, contrast ratios, screen reader flow? |
Step 2: Apply the Reduction Filter
For every element on every screen:
- Can this be removed without losing meaning? → Remove it.
- Would a user need to be told this exists? → Redesign until obvious.
- Does this feel inevitable? → If not, it's not done.
- Is visual weight proportional to functional importance? → If not, fix hierarchy.
Show full SKILL.md (290 more words)Show less
Step 3: Compile the Plan
Read references/audit-template.md for the exact output format. Organize findings into three phases:
- Phase 1 — Critical: Hierarchy, usability, responsiveness, consistency issues that actively hurt UX
- Phase 2 — Refinement: Spacing, typography, color, alignment, iconography that elevate the experience
- Phase 3 — Polish: Micro-interactions, transitions, empty/loading/error states, dark mode, subtle details
Include: design system updates required + implementation notes precise enough for a build agent to execute without interpretation.
Step 4: Wait for Approval
- Present the plan. Do not implement anything.
- User may reorder, cut, or modify any recommendation.
- Execute only what's approved, surgically.
- After each phase: present results for review before moving to the next.
- If the result doesn't feel right, say so. Propose refinement before proceeding.
Scope Discipline
You Touch
- Visual design, layout, spacing, typography, color, interaction design, motion, accessibility
- DESIGN_SYSTEM token proposals when new values are needed
- Component styling and visual architecture
You Do Not Touch
- Application logic, state management, API calls, data models
- Feature additions, removals, or modifications
- Backend structure
If a design improvement requires a functional change, flag it:
"This design improvement would require [functional change]. Outside my scope. Flagging for the build agent."
Rules
- Every design change must preserve existing functionality exactly as defined in PRD
- All values must reference DESIGN_SYSTEM tokens — no hardcoded colors, spacing, or sizes
- If a component doesn't exist in DESIGN_SYSTEM, propose it — don't invent it silently
- If user behavior for a screen isn't documented in APP_FLOW, ask before designing for an assumed flow
After Implementation
- Update progress (.txt) with design changes made
- Update LESSONS (.md) with patterns or mistakes to remember
- If DESIGN_SYSTEM was updated, confirm agent instruction files are current
- Flag remaining approved-but-not-implemented phases
- Present before/after comparison for each changed screen when possible
© bencium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in design-audit/skills/design-audit of bencium/bencium-marketplace.
- SKILL.md
- audit-template.md
- design-principles.md
Open the folder on GitHubat commit 5de46a3
Compare with similar skills
Design Audit 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 Audit this skillbencium/bencium-marketplace | 445 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Design Reviewjezweb/claude-skills | 1.1k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Design Critiquemohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| Tastemaker UI Designcodeswithroh/tastemaker | 439 | — | ~16k | Automated safety check: Pass | MIT | |
| UI Aesthetics Judgmentkasonye/ui-aesthetics-skill | 384 | — | ~3.2k | Automated safety check: Pass | None |
Similar skills
Design Critique
mohitagw15856/pm-claude-skills
Give structured, constructive feedback on any design using UX frameworks.
Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Tastemaker UI Design
codeswithroh/tastemaker
Grounds AI-built interfaces in real reference images and a saved personal taste profile, so UI work avoids the generic defaults of typical generated apps.
UI Aesthetics Judgment
kasonye/ui-aesthetics-skill
Sets rules for web UI work that favor hierarchy, spacing and restrained styling, with routes for generating, reviewing and polishing interfaces.
Agentos UI UX
SapienXai/AgentOS
Design, review, or implement AgentOS UI and UX work using the project’s operator-console visual system.
More from bencium/bencium-marketplace
All 13 skills in this repoVanity Engineering Review
bencium/bencium-marketplace
Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or…
Adaptive Communication
bencium/bencium-marketplace
A skill your agent uses when detecting ambiguous user intent, hedging language, open-ended framing, personal context before requests, or when unsure whether user wants exploration vs direct answer.
Insurgent Campaign
bencium/bencium-marketplace
Grassroots-first campaign design for anyone being outspent — startups vs.
Eu AI Act Reviewer
bencium/bencium-marketplace
Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions.
Hungarian Humanizer
bencium/bencium-marketplace
Detect and remove AI-generated markers from Hungarian text, making it sound like a native Hungarian speaker wrote it.
UI Typography
bencium/bencium-marketplace
Professional typography rules for UI design, web applications, software interfaces, and all screen-based text.
Related
Categories
Questions about Design Audit
What does Design Audit do?
Premium UI/UX design audit and refinement skill. An agent skill from bencium/bencium-marketplace. Design Audit is an agent skill from bencium/bencium-marketplace. Premium UI/UX design audit and refinement skill.
When should I use Design Audit?
Design Audit fits situations like: the user asks to audit a UI; improve an apps visual design; make an interface feel more polished; review design consistency.
How do I install Design Audit in Claude Code?
Run `npx skills add bencium/bencium-marketplace --skill design-audit -a claude-code`. Or copy the skill folder (design-audit/skills/design-audit in bencium/bencium-marketplace) into .claude/skills/design-audit in your project. Claude Code loads it when a task matches its description.
How do I install Design Audit in Codex?
Run `npx skills add bencium/bencium-marketplace --skill design-audit -a codex`. Or copy the skill folder (design-audit/skills/design-audit in bencium/bencium-marketplace) into .agents/skills/design-audit in your project. Codex loads it when a task matches its description.
Can I use Design Audit 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 bencium/bencium-marketplace --skill design-audit -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-audit, .gemini/skills/design-audit, .github/skills/design-audit and .opencode/skills/design-audit in your project.
What does Design Audit need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Audit is instructions for the agent only.
Does Design Audit 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 Audit 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 Audit use?
Design Audit 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 Audit use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Audit?
Skills that share tags, products or a category with Design Audit: Design Review (jezweb/claude-skills, 1.1k stars), Design Critique (mohitagw15856/pm-claude-skills, 1.4k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars) and Tastemaker UI Design (codeswithroh/tastemaker, 439 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Audit?
bencium (a GitHub user) maintains it in bencium/bencium-marketplace, which has 445 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 4, 2026.
Source: bencium/bencium-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.