| name | figma-design-check |
| description | Verify a planned or completed UI change against the Figma design via the Figma MCP before writing or editing component, layout, color, spacing, typography, sizing, or interaction-state code. Use when building or changing any visual surface and a Figma reference exists. Gated by capabilities.figma — skip with a capability-absent note when it is false. |
Figma Design Check
Verify every UI change against the Figma design before implementing it, using the
Figma MCP server. The Figma design is the source of truth for visuals; code must match
it (or the user must explicitly approve a deviation). A design match never waives the
accessibility or visual-regression gates that follow.
Profile keys consumed
capabilities.figma
framework.ui
architecture.source_root
architecture.component_prefix
Capability gate
This skill is gated by capabilities.figma. When it is false — or when the Figma MCP
server is not configured/reachable — record a capability-absent note and degrade:
SKIPPED: figma-design-check when capabilities.figma is false. Note
"Figma parity check not configured for this project", then proceed to the UI change
without it — but never invent the design intent from memory. If no design reference
exists, ask the user for the intended look (see "Prerequisite" below).
- The skip is bounded to the visual-parity check only. It does not waive the
accessibility gate (route to the
accessibility-auditor agent) or the visual-regression
gate (the target mapped by make.test_visual, driven by the qa-visual-tester agent).
Those run regardless of , subject only to their own gates: the
visual-regression lane is itself skipped with its own capability-absent note when
is or is .