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

figma-ds-rules

Skill7 starsChanged 4 months agoMITView on GitHub

Route generation of Figma-aware repository rules to Figma's current official MCP workflow without reproducing upstream instructions. Use when AGENTS.md, CLAUDE.md, or client rules must reflect verified Figma and codebase conventions.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the repository's existing instructions, component locations, token sources, frameworks, and test conventions.

    line 12
  2. Distinctive:

    If the official resource is unavailable, provide the source link and limit the output to verified repository facts.

    line 18

≈ “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-System Rules Router

This router connects a repository-specific rules request to the official Figma resource.

Procedure

  1. Read the repository's existing instructions, component locations, token sources, frameworks, and test conventions.
  2. Separate project facts from generic preferences and unverified assumptions.
  3. Load Figma's current design-system-rules skill from the official MCP guide distribution.
  4. Generate the smallest ruleset that records verified repository conventions and the official Figma integration sequence.
  5. Preserve existing higher-priority instructions and avoid duplicating rules already enforced by code or CI.
  6. Validate the result against one representative design-to-code task.
  7. If the official resource is unavailable, provide the source link and limit the output to verified repository facts.

Official source: Figma MCP Server Guide

Return the rules changed, evidence for each repository-specific claim, validation performed, and remaining uncertainty.

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