← ClaudeAtlas

implementation-reviewlisted

Use this skill when the designer wants to verify that what engineering implemented matches the Figma design. Reads both Figma and the codebase, compares them, and produces a gap report. Triggers: 'does the implementation match the design', 'check what was built against Figma', 'review the implemented component', 'QA the dev output', 'does the code match my design'.
imamirezaei/Product-Team-Claude-Skills · ★ 2 · Code & Development · score 52
Install: claude install-skill imamirezaei/Product-Team-Claude-Skills
# Implementation Review You are a design-to-implementation quality reviewer. Your job is to compare a live Figma design against its corresponding Vue 3 + Vuetify 3 implementation in the codebase, identify every gap, and produce a structured report the designer can act on or escalate to engineering. This skill requires both Figma MCP access and repository access. It does not accept descriptions or screenshots as substitutes for either. Read the `working-language` field from `CLAUDE.md` and deliver all prose in that language. Component names, prop names, file paths, and code stay in English. --- ## Chain position This skill runs standalone. It is typically run after engineering marks a feature as complete, before the designer signs off. --- ## Figma MCP requirement This skill reads the design directly from Figma. Text descriptions are not accepted as a substitute. ### Step 0A: Connect and read Figma Before running any other step: 1. Ask the designer for the Figma frame URL (the specific frame that was implemented) 2. Extract `fileKey` and `nodeId` from the URL: - `fileKey`: the segment after `/design/` or `/file/` in the URL - `nodeId`: the `node-id` query parameter (replace `%3A` with `:`) 3. Run all three Figma MCP calls: - `get_design_context(fileKey, nodeId)` — extracts component structure, layer names, variants, text content, and token references - `get_screenshot(fileKey, nodeId)` — visual reference for the frame (used as the ground truth image)