From pm-figma
Run a pre-handoff QA checklist on any Figma design before it goes to engineering. Use when asked to QA a Figma design, do a pre-handoff check, review a design before engineering, or validate a Figma file is ready to build. Produces a structured QA checklist covering file hygiene, component usage, accessibility, and handoff readiness with pass/fail status. Optimised for Opus 4.7 and newer models.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-figma:figma-design-qaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Runs a systematic pre-handoff QA check on a Figma design — catching issues that cause engineering back-and-forth before they become expensive.
Runs a systematic pre-handoff QA check on a Figma design — catching issues that cause engineering back-and-forth before they become expensive.
Ask the user for these if not provided:
QA Report: [Feature] | [Date] | [Platform] Overall status: Ready / Minor fixes needed / Not ready
For each fail: [Issue] — Blocking / Fix before handoff / Fix in next iteration
Status, signed off by, date.
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-figma2plugins reuse this skill
First indexed Jul 8, 2026
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.