agentleFS
thiagoxikotathiagoxikota/figma-maxxing/skills/figma-preflight/SKILL.md

figma-preflight

Skill12 starsChanged 42 days agoMITView on GitHub

Read-only preflight for an authorized Figma write: correct live target, applicable DS/API context, states and single-writer lock; also supports requested flow-graph audits.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. senlindesign/claude2figma★ 194same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

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-only gate before an authorized canvas write.

    line 17
  2. Distinctive:

    Read applicable canon/API details for this operation.

    line 32

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

Read-only gate before an authorized canvas write. It returns clear preconditions or concrete gaps and never mutates the canvas. Read-only inspection does not require write approval. A gate pass or lock is not user consent; apply authorization already present in the task without asking again.

Preconditions for the affected scope

  • Live connection and correct file: figma-console figma_get_status with a probe and correct pairing, or the available official MCP identity + metadata path. Local process/port output alone cannot prove pairing.
  • Precise target id/selection and fresh structure. Resolve ambiguity only when it affects the target; valid metadata in context can be reused.
  • Styled writes resolve the relevant variables/styles; new UI searches existing components/icons and app assets before inventing geometry. Report unrelated DS debt instead of turning a local edit into a file-wide cleanup.
  • Read applicable canon/API details for this operation. Plan the product states and flow outcomes it actually affects; no universal manual bundle or required mental pass count.
  • Claim the file lock using this skill’s scripts/figma_lock.py, with explicit agent/task identity. Same-file single writer remains the invariant. A conflict, missing/broken lock script or uncertain owner keeps writes blocked. Never release another task's lock, override autonomously on "disjoint pages", or use an empty process snapshot as permission to bypass.

gate-checks.md explains tool alternatives, targets, variables, reuse and states when a check needs detail. file-lock.md documents the existing TTL lock CLI and release rules. Release only your exact agent/task lock in cleanup/finally. An explicit user exception must name what is waived; it does not waive every gate, fix missing access or authorize another task's lock release by analogy.

Execution and proof

For partial errors/timeouts, read the canvas before retrying. Verify the property actually changed, not an unchanged proxy; preserve existing work and guard null nodes/live edits. write-verification.md contains the fragile Plugin API cases. Do not invent support for a tool/API.

New-screen or requested graph audit uses flow-audit.md: entry, destinations, orphan/dead/broken edges and semantic mismatch. An audit never creates a missing screen or rewires a valid flow on inference alone. Report the target, clear/gap status and evidence briefly; a tiny write does not require a ceremonial eight-row stamp or repeated user confirmation.

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.