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

figma-to-code

Skill0 starsChanged 4 months agoMITView on GitHub

Routes Figma implementation to the original native design-to-code skill with owner scope and evidence rules.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    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:

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

    line 14
  2. Distinctive:

    Keep credentials and unrelated private app state outside design evidence.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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 To Code

Load and follow the complete original figma:figma-design-to-code skill exposed by the current host. It is the mandatory prerequisite for Figma design implementation. Load figma:figma-use when the original workflow requires direct Figma API work. Keep the native plugin's skill, references and tooling under native ownership; this adapter does not reproduce its workflow.

If the original skill or required Figma connection is missing, the route is unavailable. Use the host's official Figma plugin setup to install or enable it and refresh session exposure. Files on disk alone do not establish a live connection; do not substitute a local summary for the original.

Owner Policy

  • Limit implementation to the requested Figma selection and repository scope. Preserve unrelated local changes and project conventions.
  • Keep credentials and unrelated private app state outside design evidence.
  • Report the actual provider, affected Figma node IDs and source changes, rendered verification results and any unavailable evidence.

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.

Reviews can't be read right now.

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