figma-design-check

Verify planned UI changes against Figma designs via the Figma MCP before editing component code.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill figma-design-check-vilnacrm-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-design-check
Source: https://github.com/VilnaCRM-Org/claude-plugins/tree/main/plugins/react-frontend-sdlc/skills/figma-design-check
Command: npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill figma-design-check-vilnacrm-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend developers often implement UI changes that drift from the approved Figma design, causing rework and visual inconsistencies. This Skill enforces a pre-implementation verification gate that compares every planned visual change against the Figma source of truth before any code is written. ## Core Features & Use Cases - Design Parity Verification: Pulls design context, screenshots, variable definitions, and metadata from the Figma MCP server and compares fill, color, spacing, typography, sizing, and interaction states field by field. - Capability Gating: Skips gracefully with a capability-absent note when capabilities.figma is false, without waiving the accessibility or visual-regression gates. - Divergence Handling: Stops implementation on mismatch, surfaces the exact discrepancy to the user, and records explicit overrides. - Use Case: Before modifying a React button component's hover state, run this gate to fetch the Figma node's interaction states, confirm the planned colors and spacing match the design tokens, then proceed only on a match. ## Quick Start Verify my planned changes to the header component against the Figma design at this node URL before I edit any code.

Frequently Asked Questions about figma-design-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify UI code matches a Figma design before implementing?▼

Run this verification gate before editing any visual code. It pulls the Figma node's design context, screenshot, and variable definitions via the Figma MCP server, then compares fill, color, spacing, typography, sizing, and interaction states field by field against your planned change.

What Figma MCP tools are used for design comparison?▼

The workflow uses get_design_context for structured design and code context, get_screenshot for visual comparison, get_variable_defs for design tokens, get_metadata for node hierarchy, and get_code_connect_map for existing component-to-code mappings.

What happens if Figma is not configured for my project?▼

When capabilities.figma is false or the Figma MCP server is unreachable, the check is skipped with a capability-absent note. The accessibility and visual-regression gates still run, and you must ask the user for the intended look rather than guessing the design.

Does a Figma design match skip accessibility checks?▼

No. A design match never waives the accessibility gate handled by the accessibility-auditor agent or the visual-regression gate. If the Figma design itself fails a WCAG rule such as contrast, it is flagged to the user.

What should I do when my planned change diverges from the Figma design?▼

Stop implementation and surface the specific discrepancy, showing the design value versus the planned value. The design wins unless the user explicitly overrides it, and any override must be recorded in the report.