agentleFS
Sign inStart free
theamtheam/claude-dev-kit/skills/figma-fetch/SKILL.md

figma-fetch

Skill17 starsChanged 3 months agoApache-2.0View on GitHub

Extract frame/component structure and all visible text from a Figma design URL. Use whenever a prompt or a fetched issue contains a figma.com/design or figma.com/file link.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the Figma MCP tools to read the file/node.

    line 23
  2. Very specific:

    If the MCP server is not authenticated, tell the user to authorize the Figma connector (via /mcp or their claude.ai connector settings) and …

    line 25
  3. Distinctive:

    Designer notes: call out any text layers that read as annotations rather than UI copy.

    line 40
  4. Distinctive:

    Never use inline styles; follow the project's styling conventions (see the consuming repo's CLAUDE.md).

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Figma Fetch

Pull design context from Figma so the implementation matches the intended UI.

Trigger

Any URL matching figma.com/(design|file)/([A-Za-z0-9]+).

How to parse the URL

Given https://www.figma.com/design/ABcd1234EFgh/My-File?node-id=123-456:

  • File key: segment after /design/ or /file/ → ABcd1234EFgh
  • Node ID: the node-id query param with - replaced by : → 123:456

How to fetch

Use the Figma MCP tools to read the file/node. Walk the node tree; collect TEXT node content and the name/type of every named node, preserving nesting depth.

If the MCP server is not authenticated, tell the user to authorize the Figma connector (via /mcp or their claude.ai connector settings) and stop. Do not invent design content.

Output format

  1. Node hierarchy with all text content, indented by depth:
===== Figma Node: <name> (<type>) =====
[FRAME] Screen name
  [TEXT] Visible label
  [INSTANCE] ComponentName
    [TEXT] Button copy
  1. Plain-English UI summary: what screens/components are shown, what labels exist, and the apparent layout intent.
  2. Designer notes: call out any text layers that read as annotations rather than UI copy.

After fetching

Incorporate the Figma context into the implementation plan before presenting it to the user. When implementing:

  • Reuse existing project components first, then the project's UI library, and only then create new components.
  • Never use inline styles; follow the project's styling conventions (see the consuming repo's CLAUDE.md).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free