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

figma-plugin-api

Skill7 starsChanged 4 months agoMITView on GitHub

Route exact Figma Plugin API questions to current official typings and developer documentation without redistributing upstream reference material. Use when an implementation depends on verified node, variable, component, style, or editor API behavior.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Do not answer exact API questions from memory when current official reference material is available.

    line 8
  2. Distinctive:

    Search the current official Figma Plugin API documentation and typings for the relevant symbol.

    line 13
  3. Distinctive:

    Verify method availability, asynchronous behavior, permissions, supported editors, and documented limitations.

    line 14
  4. Distinctive:

    Keep writes incremental and validate the resulting file state.

    line 16
  5. Distinctive:

    If the official reference is unavailable or ambiguous, stop before destructive writes and report the unresolved contract.

    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 Plugin API Reference Router

Do not answer exact API questions from memory when current official reference material is available.

Procedure

  1. Identify the exact API concept, editor type, node type, and operation involved.
  2. Search the current official Figma Plugin API documentation and typings for the relevant symbol.
  3. Verify method availability, asynchronous behavior, permissions, supported editors, and documented limitations.
  4. Build the smallest test or read-only inspection needed before attempting a write.
  5. Keep writes incremental and validate the resulting file state.
  6. Cite the official symbol or page and access date.
  7. If the official reference is unavailable or ambiguous, stop before destructive writes and report the unresolved contract.

Official sources:

Return the verified API contract, minimal implementation approach, validation, and any version-sensitive 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