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.
Give structured, constructive feedback on any design using UX frameworks.
Install Design Critique
$ npx skills add mohitagw15856/pm-claude-skills --skill design-critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills design-critique --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/design-critique .claude/skills/design-critique && 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-critique" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/design-critique into .claude/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", 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/mohitagw15856/pm-claude-skills/tree/main/skills/design-critiqueType 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 mohitagw15856/pm-claude-skills --skill design-critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills design-critique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/design-critique .agents/skills/design-critique && 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-critique" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/design-critique into .agents/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", 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 mohitagw15856/pm-claude-skills --skill design-critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills design-critique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/design-critique .cursor/skills/design-critique && 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-critique" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/design-critique into .cursor/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", 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/mohitagw15856/pm-claude-skills.git --path skills/design-critique--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 mohitagw15856/pm-claude-skills --skill design-critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills design-critique --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/design-critique .gemini/skills/design-critique && 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-critique" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/design-critique into .gemini/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", 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 mohitagw15856/pm-claude-skills design-critiqueInstalls 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 mohitagw15856/pm-claude-skills --skill design-critique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/design-critique .github/skills/design-critique && 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-critique" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/design-critique into .github/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", 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 mohitagw15856/pm-claude-skills --skill design-critique -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills design-critique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/design-critique .opencode/skills/design-critique && 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-critique" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/design-critique into .opencode/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-critique", 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-critique- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 756 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Give structured, constructive feedback on any design using UX frameworks.
- Works in 6 steps: What's Working → Priority Issues → Heuristic Assessment → …
- Asked to critique a design
- SKILL.md covers Required Inputs, Output Structure, 1. What's Working and 2. Priority Issues, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Critique is an agent skill from mohitagw15856/pm-claude-skills. Give structured, constructive feedback on any design using UX frameworks. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Produces actionable critique applying Jobs-to-be-Done, Gestalt principles, and usability heuristics, with prioritised issues and specific recommendations.
Its SKILL.md is about 1.5k 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, covering Design review and critique, UX design and User stories. It works with Figma. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to critique a design
- Give feedback on a Figma file
- Assess a user flow
- Evaluate a design against UX principles
Example prompts
- “/design-critique”
Workflow steps
6 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 1cbf1f0. 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 Critique loads about 1.5k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 756 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 756 words, ~1,520 tokens.
Download SKILL.mdSave it as
.claude/skills/design-critique/SKILL.md (or your agent's skills folder).- name
- design-critique
- description
- Give structured, constructive feedback on any design using UX frameworks. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Produces actionable critique applying Jobs-to-be-Done, Gestalt principles, and usability heuristics, with prioritised issues and specific recommendations.
Design Critique Skill
This skill provides structured, actionable design feedback using established UX frameworks. It balances positive observations with clear, prioritised improvement suggestions.
Not quite this? Use
figma-design-critique-pmwhen you want a product manager's critique run against a Figma file.
Required Inputs
Ask the user for these if not provided:
- What is being reviewed (screen, flow, component, full product)
- Design description or attached image (describe it if no image — the skill will still work)
- User goal (what is the user trying to accomplish with this design?)
- Context (web / mobile / desktop app / physical product)
- Stage (early wireframe / mid-fidelity / high-fidelity / live product)
- Primary concern (optional — e.g. "I'm worried the onboarding is too long" or "I think the CTA is unclear")
Output Structure
Design Critique: [Design Name or Screen]
User goal: [What the user needs to accomplish] Context: [Platform / Stage] Critique focus: [Primary concern if stated, otherwise "full review"]
1. What's Working
[3–5 specific, honest observations about what the design does well. Don't manufacture praise — only include genuine strengths. Be specific: "The visual hierarchy clearly guides the eye from headline → supporting detail → CTA" is useful. "Looks clean" is not.]
2. Priority Issues
Rank issues by impact on the user goal. Use:
- 🔴 High — Blocks or significantly degrades the user's ability to complete their goal
- 🟡 Medium — Causes friction or confusion but doesn't block completion
- 🟢 Low — Polish or preference — nice to fix but not critical
For each issue:
[Priority] Issue [N]: [Short name]
What's happening: [Describe the specific design problem — be precise about which element, screen, or interaction]
Why it matters: [Connect to the user goal or a specific principle — don't just say "it's confusing." Say why it creates confusion and what the consequence is for the user.]
Framework reference: [Name the principle being violated — e.g. Nielsen's Heuristic #6 (Recognition over Recall), Gestalt proximity, JTBD clarity, Fitts's Law, etc.]
Recommendation: [Specific, actionable suggestion. Not "make the button bigger" but "Increase the primary CTA to at least 44x44px to meet touch target guidelines; consider moving it below the form rather than inline with the input fields to reduce accidental taps."]
3. Heuristic Assessment
Quick assessment against Nielsen's 10 Usability Heuristics — score each as ✅ Pass / 🟡 Partial / ❌ Fail:
| Heuristic | Status | Note |
|---|---|---|
| 1. Visibility of system status | ||
| 2. Match between system and real world | ||
| 3. User control and freedom | ||
| 4. Consistency and standards | ||
| 5. Error prevention | ||
| 6. Recognition rather than recall | ||
| 7. Flexibility and efficiency of use | ||
| 8. Aesthetic and minimalist design | ||
| 9. Help users recognise, diagnose, and recover from errors | ||
| 10. Help and documentation |
Only include heuristics relevant to what's visible in the design — don't penalise for things not in scope.
Show full SKILL.md (324 more words)Show less
4. Gestalt Principles Check
[Comment on any Gestalt principles that are either well-applied or violated:]
- Proximity: [Are related elements grouped clearly?]
- Similarity: [Do similar elements look similar?]
- Continuity: [Does the eye flow naturally through the design?]
- Figure/Ground: [Is the primary content clearly distinguished from background?]
- Closure: [Are any implied shapes or containers confusing?]
5. JTBD Alignment
[Assess how well the design serves the stated job-to-be-done:]
- Does the design make the user's primary job obvious? [Yes / Partially / No — explain]
- Are there any elements that distract from the primary job? [List any competing CTAs, distractions, or unclear hierarchy]
- What emotional job does this design serve? [Speed / Confidence / Control / Delight / Other] — and does the visual design match that emotional goal?
6. Top 3 Recommended Next Steps
Prioritised list of the 3 most impactful changes. Each should be actionable in the next design iteration:
- [Most impactful change — specific]
- [Second priority]
- [Third priority]
Quality Checks
- "What's working" includes only genuine, specific observations
- Every issue has a framework reference (not just subjective opinion)
- Recommendations are specific and actionable
- Priority levels (High/Medium/Low) reflect actual impact on user goal
- Heuristic assessment only covers visible elements
Anti-Patterns
- Do not lead with visual preference (e.g. "I don't like the colour") — every issue must reference a UX principle or user impact
- Do not invent problems in the "What's Working" section — manufactured praise undermines the entire critique
- Do not provide the same priority level (High/Medium/Low) to every issue — prioritisation requires genuine judgment about user impact
- Do not skip the JTBD section for product screens — connecting feedback to the user's job-to-be-done is what separates UX critique from aesthetic opinion
- Do not give recommendations that require a full redesign when the user is in high-fidelity — scope recommendations to the design stage
Example Trigger Phrases
- "Critique this design: [description or image]"
- "Give me feedback on this UI/UX"
- "Review this Figma screen for usability issues"
- "What's wrong with this user flow?"
- "Do a heuristic evaluation of [screen/product]"
© mohitagw15856, 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-critique of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Design Critique 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 Critique this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Design Reviewjezweb/claude-skills | 1.1k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| Edit Figma Designwarpdotdev/warp | 65k | 1 repos | ~2.4k | Automated safety check: Pass | AGPL-3.0 | |
| Product Design Workflow BundleXiaomiMiMo/MiMo-Code | 14k | — | ~721 | Automated safety check: Pass | MIT | |
| UI Reviewespennilsen/pi | 122 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
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.
Edit Figma Design
warpdotdev/warp
Creates or revises Figma designs from a written description using the Figma MCP authoring tools, in a new blank file or an existing one.
Product Design Workflow Bundle
XiaomiMiMo/MiMo-Code
Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.
UI Review
espennilsen/pi
Review UI designs and implementations for accessibility, consistency, usability, and visual quality.
UX Audit Walkthrough
AIPexStudio/AIPex
Walks a Figma prototype or live webpage screen by screen and scores it against four minimalist usability principles.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Works with
Questions about Design Critique
What does Design Critique do?
Give structured, constructive feedback on any design using UX frameworks. Design Critique is an agent skill from mohitagw15856/pm-claude-skills. Give structured, constructive feedback on any design using UX frameworks.
When should I use Design Critique?
Design Critique fits situations like: asked to critique a design; give feedback on a Figma file; assess a user flow; evaluate a design against UX principles.
How do I install Design Critique in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill design-critique -a claude-code`. Or copy the skill folder (skills/design-critique in mohitagw15856/pm-claude-skills) into .claude/skills/design-critique in your project. Claude Code loads it when a task matches its description.
How do I install Design Critique in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill design-critique -a codex`. Or copy the skill folder (skills/design-critique in mohitagw15856/pm-claude-skills) into .agents/skills/design-critique in your project. Codex loads it when a task matches its description.
Can I use Design Critique 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 mohitagw15856/pm-claude-skills --skill design-critique -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-critique, .gemini/skills/design-critique, .github/skills/design-critique and .opencode/skills/design-critique in your project.
What does Design Critique need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Critique is instructions for the agent only.
Does Design Critique 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 Critique 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 Critique use?
Design Critique 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 Critique use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Critique?
Skills that share tags, products or a category with Design Critique: Design Review (jezweb/claude-skills, 1.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Edit Figma Design (warpdotdev/warp, 65k stars) and Product Design Workflow Bundle (XiaomiMiMo/MiMo-Code, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Critique?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.