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

figma-design-systems

Skill7 starsChanged 4 months agoMITView on GitHub

Route Figma-specific component, variable, style, and library questions to Figma's current official design-system guidance without reproducing upstream material. Use as a reference when exact Figma behavior matters.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 the repository's portable design-systems and token-architecture skills for general system decisions.

    line 8
  2. Distinctive:

    Verify the relevant API or product behavior against the current documentation and plan constraints.

    line 14
  3. Distinctive:

    If current official documentation is unavailable, state the uncertainty and avoid irreversible library changes.

    line 17
  4. Distinctive:

    Do not treat this router as copied Figma documentation or as a complete library-building workflow.

    line 24

≈ “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 Design Systems Reference Router

Use the repository's portable design-systems and token-architecture skills for general system decisions. Use this router only when the decision depends on current Figma product behavior.

Procedure

  1. Identify whether the question concerns components, variables, text styles, effect styles, libraries, or permissions.
  2. Open Figma's current official MCP guide and developer documentation.
  3. Verify the relevant API or product behavior against the current documentation and plan constraints.
  4. Apply the portable design-system decision first, then map it to the verified Figma mechanism.
  5. Cite the official page and access date used.
  6. If current official documentation is unavailable, state the uncertainty and avoid irreversible library changes.

Official sources:

Do not treat this router as copied Figma documentation or as a complete library-building workflow.

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