figma-implement-design/SKILL.md
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
npx skillsauth add lidge-jun/cli-jaw-skills figma-implement-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Translate Figma designs into production-ready code with pixel-perfect accuracy via the Figma MCP server.
https://figma.com/design/:fileKey/:fileName?node-id=1-2
figma-desktop MCP: select a node directly in the Figma desktop app (no URL required)codex mcp add figma --url https://mcp.figma.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login figmaFrom URL: Extract :fileKey (segment after /design/) and node ID (node-id query param).
https://figma.com/design/kL9xQn2VwM8pYrTb4ZcHjF/DesignSystem?node-id=42-15
kL9xQn2VwM8pYrTb4ZcHjF, nodeId: 42-15From desktop app (figma-desktop MCP only): tools auto-use the currently selected node; fileKey is not needed.
get_design_context(fileKey=":fileKey", nodeId="1-2")
Returns layout properties, typography, colors, component structure, spacing.
If response is truncated:
get_metadata(fileKey, nodeId) for the node mapget_design_contextget_screenshot(fileKey=":fileKey", nodeId="1-2")
Keep this screenshot accessible throughout implementation — it's the source of truth.
Download images, icons, SVGs returned by the MCP server.
localhost sources directly when providedCompare final UI against the Figma screenshot:
| Issue | Solution |
|-------|----------|
| Figma output truncated | Use get_metadata for node structure, then fetch specific nodes |
| Design doesn't match | Compare side-by-side with screenshot; check spacing, colors, typography in design context data |
| Assets not loading | Verify MCP server's assets endpoint accessible; use localhost URLs directly |
| Token values differ from Figma | Prefer project tokens for consistency; adjust spacing/sizing for visual fidelity |
development
Goal execution guidelines with PABCD integration, verification tiers, documentation workflow, and AI-driven planning
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
development
Use this skill any time a spreadsheet file is the primary input or output (.xlsx, .xlsm, .csv, .tsv). This includes: creating, reading, editing, analyzing, or formatting spreadsheets; cleaning messy tabular data; converting between formats; and data visualization with charts. Also use for pandas-based data analysis when the deliverable is a spreadsheet. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration.
tools
Use this skill when the user wants to build a financial model, 3-statement model, DCF valuation, cap table, scenario analysis, or financial projections in Excel. Trigger on: 'financial model', '3-statement model', 'DCF', 'cap table', 'pro forma', 'projections', 'sensitivity analysis', 'waterfall', 'debt schedule', 'break-even', 'discounted cash flow', 'capitalization table', 'fundraising model', 'WACC calculation', 'scenario analysis model'. Input is a text prompt with assumptions. Output is a single .xlsx file with formula-driven, interconnected statement sheets.