figma-design-critique-pm
Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review of a Figma design, or feedback from a product perspective without needing to be a designer. Produces structured outcome-based feedback tied to user goals, business metrics, and requirement coverage.
npx skills add mohitagw15856/pm-claude-skills --skill figma-design-critique-pm --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Figma Design Critique — PM Perspective Skill This skill is specifically for product managers critiquing designs — focused on whether the design achieves the user goal and business outcome, not whether it looks good. Different from the general design-critique skill which covers UX aesthetics; this one centres product thinking. ## Required Inputs - **Design description or screen summary** - **User goal** (what is the user trying to accomplish?) - **Business goal** (what outcome does the product need?) - **Original requirements** (what was this supposed to do?) - **Key metric** (what would move if this design works?) ## Output Structure ### 1. PM Critique Summary User goal, business goal restated. **Verdict:** On track / Mostly on track / Needs rethinking One-paragraph summary: what works from a product perspective, and the single most important thing to address. ### 2. Goal Alignment Check | Goal | Design supports it? | Evidence | |---|---|---| | [User goal] | Yes/Partial/No | [Specific observation] | | [Business goal] | Yes/Partial/No | [Observation] | | [Key requirement] | Yes/Partial/No | [Observation] | ### 3. PM Feedback (Outcome-Focused) Every concern must tie to an outcome.
- Required Inputs
- Output Structure
- 1. PM Critique Summary
- 2. Goal Alignment Check
- 3. PM Feedback (Outcome-Focused)
- 4. What the Design Does Well
- 5. Questions Before Next Iteration
- 6. PM Recommendation
- PM Critique Rules
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the figma-design-critique-pm skill do?
Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review of a Figma design, or feedback from a product perspective without needing to be a designer. Produces structured outcome-based feedback tied to user goals, business metrics, and requirement coverage.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill figma-design-critique-pm --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.