agentleFS
Sign inStart free
MesteriisMesteriis/Engineering-Bible-AI/skills/code-to-figma/SKILL.md

code-to-figma

Skill0 starsChanged 4 months agoMITView on GitHub

Routes code-to-Figma work to original native Code Connect or design-generation skills with owner scope rules.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Follow that author's skill and its references.

    line 14
  2. Distinctive:

    If the selected original skill or Figma connection is missing, the route is unavailable.

    line 17
  3. Distinctive:

    Keep the requested target file, nodes, mappings and allowed source scope explicit.

    line 24
  4. Distinctive:

    Do not inspect secret-bearing or unrelated private app state for artifacts.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Code To Figma

Choose and load the complete original native skill for the requested output:

  • Component-to-code mappings: figma:figma-code-connect.
  • An editable screen or composed view from code: figma:figma-generate-design, with its required figma:figma-use prerequisite.

Follow that author's skill and its references. Preserve the native plugin's ownership and update path; this adapter does not implement its author workflow.

If the selected original skill or Figma connection is missing, the route is unavailable. Use the host's official Figma plugin setup to install or enable it, then refresh session exposure. Do not substitute local summarized steps or claim that an installed package proves a live connection.

Owner Policy

  • Keep the requested target file, nodes, mappings and allowed source scope explicit. Preserve unrelated components and repository changes.
  • The requested output determines the provider; Code Connect mappings and editable screens are distinct deliverables.
  • Do not inspect secret-bearing or unrelated private app state for artifacts.
  • Report the actual provider, changed node IDs or mapping files, verification results and material evidence gaps.

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