agentleFS
thiagoxikotathiagoxikota/figma-maxxing/skills/figma-handoff-gate/SKILL.md

figma-handoff-gate

Skill12 starsChanged 42 days agoMITView on GitHub

Audit a Figma handoff for action/state completeness, readable annotations, recipient use and valid proof. Read-only review and already authorized correction remain distinct; no fixed review-role ritual.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the project's handoff/locale/sample-data rules first.

    line 22

≈ “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 handoff readiness

Audit the affected handoff against concrete developer/recipient needs. This is read-only unless correction is already authorized. Apply that authorization within scope without asking again per finding; a new product/DS decision or external send needs its own authorization.

Use the project's handoff/locale/sample-data rules first. Technical criteria are in handoff-checks.md: spacing and label clearance, caption sizing/contrast/density, honest screen counts, component states, localization, typographic conventions, state/actor/inverse-action completeness, process-free delivered canvas and proof at the scale of use. Load the sections needed for the handoff; a full release audit covers all applicable criteria.

A screen's actions need designed outcomes: destinations, help/info, inverse pairs, affected actor, destructive confirmation and after-state. Explicitly partial/out-of-scope work is reported as such, never declared a complete flow. Prototype reachability and starting point must support a "clickable" claim. Overview captures do not prove a tiny icon or text detail.

Craft/precision evidence from figma-slop-check can be reused; no mandatory separate pass, four-role stamp, fixed order or external reviewer is needed for every change. Inspect the actual artifact and recipient path, not a written simulation of what a model thinks might happen. Refresh checks invalidated by a later edit, rather than restarting unrelated gates.

Report blockers separately from nonblocking warnings, with target and evidence. A warning alone does not invent a release block; a missing required outcome or unverified critical state cannot be disguised as PASS. Reviewer output does not authorize edits/replies. Approved fixes use preflight/lock, property read-back and appropriate visual proof. Keep process logs/review packages private, not on the delivered canvas; runtime memory is separately governed.

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.