Review Figma Designs From Engineer Perspective1 skill
Analyzes Figma designs at two levels (basic properties and engineering concerns) and posts comments to exact element locations.
Product & Design Blueprint
Safety checkedA Claude Code skill that reviews Figma designs and automatically posts position-specific comments to target elements.
Copy this prompt and paste it into your AI agent to install.
Reviews Figma designs from an engineer's perspective and automatically posts comments to exact locations in Figma. It analyzes designs at two levels: basic design properties (spacing, color, sizing, structure) extracted from node information, and engineer-focused concerns (data structures, forms, performance, specifications) from screenshots. Instead of generic feedback scattered in chat, every issue gets positioned at the exact element in Figma.
Once set up with a Figma token and Claude Code access, run /figma-design-review <figma_url>. The skill validates prerequisites, extracts node information via REST API, captures a screenshot, runs two-phase analysis (basic design checks against node properties, then engineer perspective review), calculates exact element coordinates, and posts individual comments to each issue location in Figma. Output: a summary table of all flagged issues organized by category (spacing, color, sizing, data structure, forms, etc.).
Analyzes Figma designs at two levels (basic properties and engineering concerns) and posts comments to exact element locations.
Every design review issue appears in Figma at its exact location with reasoning, so engineers understand both what to fix and why without switching between tools.
Requires Node.js runtime for Python scripts (post_comment.py, get_node_info.py) and Figma MCP enabled in Claude Code. REST API calls use FIGMA_TOKEN for authentication; if MCP screenshot/metadata calls fail on complex node trees, the standalone REST API script continues to work because it operates independently.
Requires Figma Desktop App running with the target file open and the target node/frame selected. If Figma MCP fails on complex designs with many nested nodes (common with tables/lists), the REST API can still extract coordinates. FIGMA_TOKEN environment variable must be set before running the skill. MCPsocket connection is required between Claude Code and Figma Desktop.
Basic Design Review
Checks spacing consistency, color usage, touch target sizing (44x44px minimum), component structure, and grid alignment from node properties
Engineer Perspective Analysis
Reviews data structure nesting depth, form validation patterns, table scrolling needs, state complexity, permissions, and specification ambiguities
Position-Specific Comments
Calculates exact element coordinates from REST API and posts comments to the center of flagged components, not generic page comments
Coordinate Accuracy
Uses Figma REST API for precise coordinate detection rather than visual estimation, ensuring comments land on intended elements
Bilingual Documentation
Full English and Japanese documentation with setup, usage, and troubleshooting for both languages
Avoid paying top-tier rates for routine work or discovering too late that a polished result solved the wrong problem. A confirmed plan routes each phase to an appropriate model, limits context bloat, and leaves a handoff for longer tasks.
Matthias Jahn
Sr. Director, Analytics at G2
Reduce hours lost to repetitive admin without adding a complicated stack. Prioritized, tested workflows automate routine research, client communication, project tracking, and website tasks while keeping people in control of important decisions.
Avoid costly, fragmented digital projects with a plan that connects business goals to practical tools, implementation steps, and measurable results. It also flags performance, security, accessibility, and SEO checks before launch.