Design Audit: the free Claude Code skill that fixes where users get stuck
Install it in one command, let it review your app, and approve the fixes it makes in your code.
People sign up for your SaaS, click around for a minute, and leave. Most of the time you never find out why. Often it's not your idea. It's small things: a button nobody sees, a screen that looks broken on mobile, an empty page with no next step, an error message that explains nothing. You stopped noticing them weeks ago. New users notice them in seconds. Design Audit is a free skill for Claude Code that goes through your app and finds those spots. Then it plans the fixes and makes them in your code, but only after you say yes.
| Skill | Built by | Original repository |
|---|---|---|
| Design Audit | bencium | github.com/bencium/bencium-marketplace |
What Design Audit checks
The skill reviews your app across 15 areas:
| Area | What it looks at |
|---|---|
| Visual hierarchy | Does the most important thing on each screen stand out? |
| Spacing & rhythm | Consistent gaps, nothing cramped or floating |
| Typography | Readable sizes, clear headings, not too many styles |
| Color | Contrast, consistent use, colors that mean something |
| Alignment & grid | Things line up, layouts feel calm |
| Components | Buttons, inputs and cards look and behave the same everywhere |
| Iconography | Consistent icons that are easy to understand |
| Motion | Animations that help instead of distract |
| Empty states | What new users see before there's any data |
| Loading states | What happens while things load |
| Error states | Whether errors tell people what to do next |
| Dark mode | Whether it actually works, not just inverts colors |
| Density | Not too much, not too little on one screen |
| Responsiveness | Phone, tablet and desktop |
| Accessibility | Contrast, keyboard use, screen readers |
How it works
Full audit.
It reviews your app across all 15 areas.
A plan in three phases.
Phase 1, Critical: problems that actively hurt the experience, like hierarchy, usability, responsiveness and consistency. Phase 2, Refinement: spacing, typography, color, alignment and icons. Phase 3, Polish: micro-interactions, transitions, empty, loading and error states, dark mode and small details.
You approve.
Nothing changes until you say yes.
It fixes, phase by phase.
It reviews the result after each phase before moving on.
Setup in 5 steps
1. Open your project in Claude Code. Open the terminal in your app's project folder and start Claude Code.
npx skills add https://github.com/bencium/bencium-marketplace --skill design-auditRun a design audit on my app.Run a design audit on the signup and onboarding flow. Focus on where a new user could get stuck.4. Read the plan. Go through the three phases. Remove anything you don't want, and ask questions if something is unclear.
5. Approve phase 1 first. Let it fix the critical issues, check your app, then move on to the next phase.
Tips before you run it
- Commit your code first. Then you can undo every change with one command.
- Start with one flow. Signup and onboarding are where most new users leave.
- Give it context. The skill works best when your project has docs like a design system, an app flow or a product description. If you don't have them, describe your app and your users in the prompt.
- Approve one phase at a time. Check the result in the browser and on your phone before you continue.
- Keep your brand. If it suggests changing colors or fonts you want to keep, tell it.
Is Design Audit really free?
Yes. The skill is free on GitHub. You need Claude Code to run it, which uses your existing Claude plan.
Does it work with any tech stack?
It works on your app's frontend code. It's most useful for web apps. Check the result after each phase, especially if you use an unusual setup.
Will it break my app?
It doesn't change anything until you approve the plan, and it goes phase by phase. Commit your code before you start, so you can always go back.
Can it see where my real users drop off?
No. It reviews your app, not your user data. Use it together with your analytics to see if the spots it finds match where people actually leave.