PM Design Critique Skill: Structured UX Feedback

What is the pm-design-critique skill?

Its own quality checklist begins with a rule against flattery: the What's Working section may only hold genuine, specific observations. Looks clean does not count, while a hierarchy that guides the eye from headline to call to action does.

The skill is named design-critique in its frontmatter and lives in a very large library of professional skills, each one a plain markdown file. This copy sits in the OpenClaw export folder of that repository.

What it asks you for

• What is being reviewed: a screen, flow, component or full product.
• A design description or an attached image. Without an image, the skill still works from your description.
• The user goal, meaning what the person is trying to accomplish.
• The context, such as web, mobile, desktop app or physical product, and the stage from early wireframe to live product.
• An optional primary concern, for example an onboarding flow that feels too long.

What the critique contains

1. What's Working, with 3 to 5 honest and specific observations.
2. Priority Issues, each rated High, Medium or Low and tied to a named principle.
3. A Heuristic Assessment table scoring Nielsen's 10 usability heuristics as Pass, Partial or Fail.
4. A Gestalt check covering proximity, similarity, continuity, figure and ground, and closure.
5. JTBD Alignment, which asks whether the primary job is obvious and what distracts from it.
6. Top 3 Recommended Next Steps for the next design iteration.

Who the pm-design-critique skill is for

Best for

• Product managers and founders who need written feedback on a wireframe, flow or live screen without a design review meeting. For a plain critique prompt, there is critique.
• Designers who want every comment tied to a principle and not to taste. A related review format is kwp-design-critique.
• Early stage checks, since recommendations are scoped to the stated stage.

Not for

• Running a Figma file review for a product manager. The skill points to a separate figma-design-critique-pm skill for that.
• Replacing user research. It critiques what you describe or attach, and does not test with real users.
• Choosing colors or type. The output is about usability and goals, and not about visual style. See uiux-design for broader design guidance.

Use it with UiChemy

Run the critique on your Figma screen or on a screenshot of a WordPress page, then act on the three next steps. UiChemy Figma to WordPress converts the revised design into an editable page, and Composer handles visual tweaks. Click Get Started.

How to install PM Design Critique Skill: Structured UX Feedback

npx pm-claude-skills add

1. Run the installer

   The README's install line is npx pm-claude-skills add, described as working for any tool, including Cursor, Codex, Windsurf, Cline and Zed.

2. Or use Claude Code

   In Claude Code, run /plugin and search for pm-skills, which the README says is the official directory route. It also shows bundles such as /plugin install pm-decoders@pm-claude-skills.

3. Or copy this skill only

   Clone https://github.com/mohitagw15856/pm-claude-skills.git and copy the exports/openclaw/design-critique folder into the place where your agent loads skills.

Check that it loaded

Ask your agent to critique a screen and describe the user goal, platform and stage. With the skill loaded the reply should follow six numbered sections and finish with three next steps.

Read the official instructions on GitHub

Key features

• Six section critiqueA fixed structure runs from What's Working through Priority Issues, a heuristic table, a Gestalt check and a JTBD check to the top three next steps.
• Ranked issuesEach issue is marked High, Medium or Low by its effect on the user goal, with what is happening, why it matters, a framework reference and a recommendation.
• Nielsen's 10 heuristicsA table covers all ten heuristics and scores each as Pass, Partial or Fail, but only for what is visible in the design and not for things out of scope.
• Gestalt principles checkPrompts the agent to comment on proximity, similarity, continuity, figure and ground, and closure, whether they are well applied or violated.
• Jobs-to-be-Done alignmentAsks whether the primary job is obvious, what competes with it, and which emotional job the design serves, such as speed, confidence, control or delight.
• Stage aware adviceInputs include the stage, from early wireframe to live product, and an anti-pattern forbids recommending a full redesign when the work is already high fidelity.
• No manufactured praiseThe skill says to include only genuine strengths, because invented praise undermines the whole critique.
• Principle over preferenceEvery issue must cite a UX principle or user impact. Leading with a visual preference such as disliking a color is listed as an anti-pattern.
• Built in quality checksA checklist confirms that strengths are specific, issues carry a framework reference, recommendations are actionable and priority levels (High, Medium, Low) reflect actual impact on the user's goal.
• Plain trigger phrasesExample prompts include critique this design, give me feedback on this UI, review this Figma screen for usability issues and do a heuristic evaluation.

Frequently asked questions