figma-cli

name	figma-cli
description	Use this skill when you need to inspect a Figma Design file for LLM workflows, discover page/component/variant candidates, validate a local semantic manifest, or query Figma nodes via semantic keys with the local figma-web-cli in this repository.

figma-cli

Use this skill when the user wants to:

• inspect a Figma file or page for LLM/codegen work
• understand page boundaries or page variants from Figma
• validate .figma-llm/manifest.json
• resolve semantic keys like page.checkout
• fetch normalized Figma node data instead of raw API output

Assume the CLI source is in the current repository root.

Prerequisites

• FIGMA_TOKEN must be set
• This skill is for Figma Design files via the local Rust CLI in this repo
• If the binary is not installed, prefer cargo run -- ...

Workflow

1. Start with cargo run -- pages list --file <FILE_KEY> --pretty to find canvases and top-level candidates.
2. Use cargo run -- page inspect --file <FILE_KEY> --page-id <CANVAS_ID> --pretty to get LLM-friendly structure, candidate boundaries, page variant groups, and component usage.
3. Let an external LLM draft .figma-llm/manifest.json.
4. Validate the manifest with cargo run -- manifest validate --file <FILE_KEY> --manifest .figma-llm/manifest.json --pretty.
5. Resolve or fetch by semantic key with cargo run -- resolve ... or cargo run -- get ....

Rules

• Prefer --pretty for human review and omit it when piping JSON to another tool.
• Do not invent semantic mappings before running pages list or page inspect.
• Treat semantic key resolution as exact-match only; if a key is ambiguous, fix the manifest instead of guessing.
• Use cargo install --path . only when the user wants a local install; otherwise cargo run -- ... is the safest default.