Figma Reader

Read Figma design context via the Figma MCP server.

Arguments

$ARGUMENTS[0]

— Figma link, design prompt copied from Figma, or attached UI design image (optional)

$ARGUMENTS[1]

— (optional) Output directory for persisting the design context. Defaults to

.implement-assets/figma

When invoked by the orchestrator (e.g.

implement

),

$ARGUMENTS[1]

is provided. When used standalone, it defaults to

.implement-assets/figma

.

Execution

Codebase check

Verify this is a frontend project — follow

references/rules.md

Codebase Check. If not frontend, skip the entire skill.

Pre-flight check

Use

ToolSearch

to detect if Figma MCP tools are available — follow

references/rules.md

If MCP is not available, use

AskUserQuestion

to guide setup or allow skip

Resolve design input

:

If

$ARGUMENTS[0]

contains a valid Figma link or prompt → use it directly

If

$ARGUMENTS[0]

is an attached UI image → show it for context, then use

AskUserQuestion

to ask the user to select the relevant component in Figma (see

references/rules.md

Design Input)

If

$ARGUMENTS[0]

is empty or not provided → use

AskUserQuestion

to ask user (see

references/rules.md

Design Input)

Read design

Use the Figma MCP tools to read the design from the Figma link resolved in step 4

Format the output per

references/output-format.md

Save output

Run mkdir -p $ARGUMENTS[1] via Bash, then save the full formatted output to $ARGUMENTS[1]/output.md using the Write tool