What do I need to use Figma Design Critique — PM Perspective?

Design description or screen summary; User goal; Business goal; Original requirements; Key metric.

Is Figma Design Critique — PM Perspective free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Figma Design Critique — PM Perspective

Q: How do I know the Figma Design Critique — PM Perspective output is good?

The skill verifies itself against its own quality checks: Every concern tied to user or business outcome; What is working section is genuine and specific; Questions section included (not just directives); PM recommendation is explicit.

🔵 Stable🕐 updated 2026-06-08 🔷 SkillSpec L3 pm-figma

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Give me a PM critique of this design”“Review this design from a product perspective”“What product feedback do I have on this Figma design?”“Critique this design without being a designer”“Does this design achieve the user goal?”

What to give it

▸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?

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every concern tied to user or business outcome

✓What is working section is genuine and specific

✓Questions section included (not just directives)

✓PM recommendation is explicit

✓Evidence basis stated honestly

⚠️ What it refuses to do

Do not critique visual aesthetics — PM feedback must focus on product outcomes, user goals, and business requirements

Do not provide feedback without stating the evidence basis — distinguish between observed design facts and assumed user behaviour

Do not give vague feedback like "the flow feels confusing" — every concern must reference a specific screen state or interaction

Do not ignore what is working — balanced critique includes explicit acknowledgment of design decisions that are well-executed

Do not critique without knowing the design constraints — always ask about technical, time, or resource limitations before judging decisions

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="figma-design-critique-pm"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Figma Design Critique — PM Perspective is one of 1182 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog