Agent skill · Frontend

design-critique

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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill design-critique --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/design-critique/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Design Critique Skill This skill provides structured, actionable design feedback using established UX frameworks. It balances positive observations with clear, prioritised improvement suggestions. ## 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 → su

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Structure
  3. 1. What's Working
  4. 2. Priority Issues
  5. [Priority] Issue [N]: [Short name]
  6. 3. Heuristic Assessment
  7. 4. Gestalt Principles Check
  8. 5. JTBD Alignment
  9. 6. Top 3 Recommended Next Steps
  10. Quality Checks
  11. Anti-Patterns
  12. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the design-critique skill do?

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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill design-critique --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going