Design & media

Templates

Try it

Read Figma design context from Multica issue figma_urls without Figma MCP.

What it does

Read Figma design context from Multica issue figma_urls without Figma MCP.

The skill document

Read Figma Design

Use this skill when a Multica issue contains non-empty figma_urls.

This is a pure skill. The scripts do all deterministic work: token handling, Figma REST reads, screenshots, node expansion, style extraction, Code Connect clues, and artifact writing.

Required Workflow

Run from this skill root before repairing UI code:

node scripts/read-figma-context.mjs \
  --issue-json /.multica/tmp/.json \
  --out /.multica/figma-context \
  --repo 

For a single URL:

node scripts/read-figma-context.mjs \
  --url "https://www.figma.com/design//?node-id=" \
  --out /.multica/figma-context \
  --repo 

For a direct smoke or manual URL:

node scripts/read-figma-context.mjs \
  --url "https://www.figma.com/design//?node-id=" \
  --out /.multica/figma-context \
  --repo 

Then read, in this order:

  1. summary.md
  2. manifest.json
  3. urls//design-properties.json
  4. urls//code-connect.json
  5. urls//screenshots/
  6. urls//css-hints.css

Validate artifacts manually when needed:

node scripts/validate-artifact.mjs 

Offline diagnostics:

node scripts/read-figma-context.mjs --help
node scripts/read-figma-context.mjs --version

Both commands run without reading credentials or network. --help runs without reading credentials or network. --version runs without reading credentials or network.

Run a real API smoke before declaring this skill usable in a new environment:

node scripts/smoke-figma-context.mjs \
  --url "https://www.figma.com/design/VSfJU5zJ10wSdeMu2vk1Ar/New-workflow_Sensitive-Industry--Configuration_Age-Gating?node-id=6127-21193" \
  --out /.multica/figma-context \
  --repo  \
  --env-file ../../.env

Hard Rules

  • Do not guess design intent from the URL alone.
  • Read the generated artifacts before changing UI code.
  • Cite the Figma URL, canonical node id, and artifact path in the repair notes.
  • If parsing or Figma reading fails, report the stable error code and do not claim the design was used.
  • Code Connect is best effort by default; do not turn unavailable into unmapped.
  • Prefer local design-system components and tokens before custom CSS.
  • Do not expose tokens in logs, comments, artifacts, or repair notes.
  • Do not commit .multica/figma-context/ or .multica/tmp/.

Related skills

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-conv...

7 installs

Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, docum...

Convert Figma designs to mobile UI code (Compose/XML/SwiftUI/UIKit/Flutter) via the Figma REST API with local resource scanning, multi-frame comparison, and feedback-log corrections. Activate when a user provides a Figma link and asks for mobile layout code.

24 installs1 stars

Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whet...

Runs a pre-handoff QA checklist on a Figma design before it goes to engineering. Use when asked to QA a Figma design, do a pre-handoff check, or validate a F...

Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review o...