Runs a structured PM design review against product
Figma Design Review Skill
Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whether a design meets the product spec.
--- name: figma-design-review description: "Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whether a design meets the product spec. Produces a requirements coverage check, UX concerns, open questions, and an explicit approval status — approved, approved with conditions, or not approved." --- # Figma Design Review Skill Runs a structured PM design review — checking that a design meets product requirements, covers all user flows, and is ready for engineering. This is a requirements-and-outcomes review, not an aesthetic critique. ## Required Inputs - **Design description or screen summary** - **Original requirements** (PRD snippet, ticket, or acceptance criteria) - **User flow being designed** - **Review stage** (concept / mid-fidelity / pre-handoff final) ## Output Structure
Overview
Runs a structured PM design review — checking that a design meets product requirements, covers all user flows, and is ready for engineering. This is a requirements-and-outcomes review, not an aesthetic critique.
Manual install (npx, ZIP)
Claude Code
npx skills add mohitagw15856/pm-claude-skills --skill figma-design-review -g -a claude-codeClaude Code (manual)
mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \
| tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/figma-design-reviewWindows (PowerShell)
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/06f77cd4cd723506984e/figma-design-review.zip" -OutFile "$env:TEMP\figma-design-review.zip"; Expand-Archive "$env:TEMP\figma-design-review.zip" -DestinationPath "$HOME\.claude\skills" -ForceClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md3.0 KB
Read the files here
mohitagw15856/
SKILL.md
Show the full text76 lines
Figma Design Review Skill
Runs a structured PM design review — checking that a design meets product requirements, covers all user flows, and is ready for engineering. This is a requirements-and-outcomes review, not an aesthetic critique.
Required Inputs
- Design description or screen summary
- Original requirements (PRD snippet, ticket, or acceptance criteria)
- User flow being designed
- Review stage (concept / mid-fidelity / pre-handoff final)
Output Structure
1. Review Header
Feature, review stage, reviewed by, date. Overall status: Approved / Approved with changes / Needs revision
2. Requirements Coverage Check
| Requirement | Covered? | Notes |
|---|---|---|
| [Requirement from PRD] | Yes/No/Partial | [Specific observation] |
Missing coverage summary: [Requirements not addressed — must resolve before approval]
3. User Flow Completeness
| Flow step | Designed? | Issues |
|---|---|---|
| [Step] | Yes/No/Partial | [Issue] |
| Error state | Yes/No | |
| Empty state | Yes/No | |
| Loading state | Yes/No |
4. PM Concerns
[Concern] — Blocking / Should fix / Nice to fix
- What: [Specific observation]
- Why it matters: [Business or user impact — not aesthetic preference]
- Suggested resolution: [What PM wants to see]
5. Open Questions
| Question | Owner | Needed by |
|---|---|---|
| [Question] | Designer/Eng/PM | [Date] |
6. Approval Decision
Approved / Approved with changes (list) / Needs revision (focus area + next review date)
Quality Checks
- Every requirement assessed
- All flow states checked (error, empty, loading)
- Concerns are outcome-focused not aesthetic
- Open questions have owners
- Approval status is explicit
Anti-Patterns
- Do not review a design without a list of requirements to check against — always ask for the PRD, design brief, or acceptance criteria first
- Do not give a vague approval status — the decision must be explicitly "approved", "approved with conditions", or "not approved"
- Do not conflate requirements gaps with UX concerns — track them separately so engineers and designers can act independently
- Do not raise concerns without suggesting what information is needed to resolve them
- Do not skip open questions — unresolved assumptions at review time become bugs after engineering handoff
Example Trigger Phrases
- "Review this Figma design against the requirements"
- "Do a PM design review for [feature]"
- "Check if this design meets the product spec"
- "Is this design ready to hand off to engineering?"
- "What is missing from this design before we can build it?"
| 1 | |
| 2 | name figma-design-review |
| 3 | description "Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whether a design meets the product spec. Produces a requirements coverage check, UX concerns, open questions, and an explicit approval status — approved, approved with conditions, or not approved." |
| 4 | |
| 5 | |
| 6 | # Figma Design Review Skill |
| 7 | |
| 8 | Runs a structured PM design review — checking that a design meets product requirements, covers all user flows, and is ready for engineering. This is a requirements-and-outcomes review, not an aesthetic critique. |
| 9 | |
| 10 | ## Required Inputs |
| 11 | |
| 12 | **Design description or screen summary** |
| 13 | **Original requirements** (PRD snippet, ticket, or acceptance criteria) |
| 14 | **User flow being designed** |
| 15 | **Review stage** (concept / mid-fidelity / pre-handoff final) |
| 16 | |
| 17 | ## Output Structure |
| 18 | |
| 19 | ### 1. Review Header |
| 20 | Feature, review stage, reviewed by, date. |
| 21 | **Overall status:** Approved / Approved with changes / Needs revision |
| 22 | |
| 23 | ### 2. Requirements Coverage Check |
| 24 | |
| 25 | | Requirement | Covered? | Notes | |
| 26 | |---|---|---| |
| 27 | | [Requirement from PRD] | Yes/No/Partial | [Specific observation] | |
| 28 | |
| 29 | Missing coverage summary: [Requirements not addressed — must resolve before approval] |
| 30 | |
| 31 | ### 3. User Flow Completeness |
| 32 | |
| 33 | | Flow step | Designed? | Issues | |
| 34 | |---|---|---| |
| 35 | | [Step] | Yes/No/Partial | [Issue] | |
| 36 | | Error state | Yes/No | | |
| 37 | | Empty state | Yes/No | | |
| 38 | | Loading state | Yes/No | | |
| 39 | |
| 40 | ### 4. PM Concerns |
| 41 | |
| 42 | **[Concern] — Blocking / Should fix / Nice to fix** |
| 43 | What: [Specific observation] |
| 44 | Why it matters: [Business or user impact — not aesthetic preference] |
| 45 | Suggested resolution: [What PM wants to see] |
| 46 | |
| 47 | ### 5. Open Questions |
| 48 | |
| 49 | | Question | Owner | Needed by | |
| 50 | |---|---|---| |
| 51 | | [Question] | Designer/Eng/PM | [Date] | |
| 52 | |
| 53 | ### 6. Approval Decision |
| 54 | Approved / Approved with changes (list) / Needs revision (focus area + next review date) |
| 55 | |
| 56 | ## Quality Checks |
| 57 | [ ] Every requirement assessed |
| 58 | [ ] All flow states checked (error, empty, loading) |
| 59 | [ ] Concerns are outcome-focused not aesthetic |
| 60 | [ ] Open questions have owners |
| 61 | [ ] Approval status is explicit |
| 62 | |
| 63 | ## Anti-Patterns |
| 64 | |
| 65 | [ ] Do not review a design without a list of requirements to check against — always ask for the PRD, design brief, or acceptance criteria first |
| 66 | [ ] Do not give a vague approval status — the decision must be explicitly "approved", "approved with conditions", or "not approved" |
| 67 | [ ] Do not conflate requirements gaps with UX concerns — track them separately so engineers and designers can act independently |
| 68 | [ ] Do not raise concerns without suggesting what information is needed to resolve them |
| 69 | [ ] Do not skip open questions — unresolved assumptions at review time become bugs after engineering handoff |
| 70 | |
| 71 | ## Example Trigger Phrases |
| 72 | "Review this Figma design against the requirements" |
| 73 | "Do a PM design review for [feature]" |
| 74 | "Check if this design meets the product spec" |
| 75 | "Is this design ready to hand off to engineering?" |
| 76 | "What is missing from this design before we can build it?" |
Details
- Updated
- Sep 23, 2026
- License
- MIT
- Stars on the repo
- ★ 1,395
- Checked
- Source
- mohitagw15856/pm-claude-skills ↗
- Creator
- mohitagw15856 · 193 listings
Made with figma-design-review
Figma Design Review Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Figma Design Review Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Similar skills
See all →
SkillBrainstorms ideas into designs before any creative workBrainstorming Ideas Into Designs
obra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub stars
SkillDescribe your product or app and how customers use it; getBrutal Design Review Of Your Product
wondelai/skills · by wondelaiDescribe your product or app and how customers use it; get back a blunt verdict with an exact list of what to cut and what to fix first.★ 2.2k GitHub stars
SkillRuns a PM-perspective design critique focused on productFigma Design Critique — PM Perspective Skill
mohitagw15856/pm-claude-skills · by mohitagw15856Runs 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.★ 1.4k GitHub stars
SkillDung khi da co THIET KE va can duyet truoc khi dang47 design review
minhnv0807/ai-business-skills · by minhnv0807Dung khi da co THIET KE va can duyet truoc khi dang — cham diem 4 nhom brand consistency, hierarchy va do doc, yeu to chuyen doi, phu hop nen tang, moi nhom 10 diem, kem feedback theo dang van de - tai sao - cach sua va verdict duyet / sua nhe / lam lai. Kich hoat khi user nhac 'review design', 'duyet thiet ke', 'feedback thiet ke', 'cham diem design', 'anh nay ok chua', 'nhin sao sao ma khong biet sai cho nao', 'check brand', 'approve creative'. Dung ca khi user chi gui anh va hoi 'xem giup'. Khong dung cho — duyet CHU nhu content brief va ads copy thi dung skill 62-marketing-review; do xem trang co ra don khong thi dung skill 68-cro-audit-trang.★ 599 GitHub stars
SkillA finished DESIGN needs scoring and feedback47 design review globalminhnv0807/ai-business-skills · by minhnv0807Use when a finished DESIGN needs scoring and feedback — brand consistency, hierarchy plus readability plus accessibility, conversion elements, and platform fit, 10 points each, with per-issue feedback in issue, why, and how-to-fix form and a verdict of approve, minor fix, or redo. Trigger on 'design review', 'review this design', 'score this creative', 'is this design good', 'brand check on this banner', 'can we ship this or not'. Also use when the user just sends an image and asks for thoughts. Not for — reviewing copy and briefs, see `62-marketing-review-global`; writing the brief before production, see `42-image-brief-global`; the brand rules being checked against, see `46-brand-guideline-global`.★ 599 GitHub stars
SkillTell us what your banner is for and what it should sayBanner Design - Multi-Format Creative Banner System
nextlevelbuilder/ui-ux-pro-max-skill · by claudekitTell us what your banner is for and what it should say, and get back polished, ready-to-post cover and ad images sized correctly for each platform.★ 130k GitHub starsMore from mohitagw15856
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub stars
SkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub stars
SkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub stars
SkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub stars
SkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub stars
SkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars