agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/figma-library-builder/SKILL.md

figma-library-builder

Skill7 starsChanged 4 months agoMITView on GitHub

Route a Figma library build to Figma's current official MCP workflow and this repository's portable design-system skills without reproducing upstream instructions. Use when creating tokens, components, documentation, and code mappings in Figma.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Use design-systems and token-architecture to make platform-neutral architecture decisions.

    line 10
  2. Distinctive:

    If the official workflow is unavailable, return the architecture and migration plan without performing Figma mutations.

    line 20

≈ “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 Library Builder Router

Deprecated compatibility slug. Use figma-generate-library for the canonical library-generation workflow.

Use design-systems and token-architecture to make platform-neutral architecture decisions. Use the official Figma workflow for current product and API execution details.

Procedure

  1. Inventory the codebase token sources, components, naming, variants, accessibility requirements, and release constraints.
  2. Inspect the target Figma file and existing libraries before proposing new assets.
  3. Produce a mapping plan from code concepts to Figma concepts and obtain approval for destructive or large-scale changes.
  4. Load Figma's current library-generation skill from the official MCP guide distribution.
  5. Execute in bounded phases, validating created assets and visual output after each phase.
  6. Preserve Code Connect and local component identities where they already exist.
  7. If the official workflow is unavailable, return the architecture and migration plan without performing Figma mutations.

Official source: Figma MCP Server Guide

Return the architecture, mappings, assets created, validation evidence, and remaining migration work.

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