figma-spec
This skill is required to create, read, edit, review, or comment on Figma specs. You must read it when working on a PRD, brief, RFC or any kind of document in either a standalone Figma spec or a Figma spec embedded in a Figma Design or Figjam file.
Install
With your agent
Install OMGSkills skill "figma/mcp-server-guide:skills/figma-spec" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/figma/mcp-server-guide /tmp/mcp-server-guide && ln -s /tmp/mcp-server-guide/skills/figma-spec ~/.claude/skills/figma-specFrom README
Work with a Figma spec You MUST always call whoami before using any figma.spec. API and confirm that the target file’s plan (or the destination plan for a new file) has specsenabled: true. whoami does not identify which plan owns a file. If the plan is unclear, you MUST ask the user; never infer it from the file key or another plan’s access. If specsenabled is false or absent for that plan, explain that Specs is unavailable and stop the workflow. A native Figma spec is GitHub-Flavored Markdown (GFM) under a SPECBLOCK node. A standalone Figma spec is just one spec; a FigJam or Design file can contain several embedded specs. Discover and choose the Figma spec Resolve a supplied URL node-id when present with figma.getNodeByIdAsync and require type === "SPECBLOCK" plus specBlockType === "DOCUMENT".
More from this repo
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section...
figma-use
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call.
figma-code-workflows
Import or upload local HTML or project files into Figma, choose editable Design frames, runnable Code Layers or...