figma-click-flow
Skill12 starsChanged 42 days agoMITView on GitHub
Draw or refresh a static click-flow overlay on laid-out Figma screens from prototype reactions or explicit pairs, using the existing SVG recipe and verified targets.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- figma-bridge-doctorSkill
- figma-canonSkill
- figma-comment-fix-loopSkill
- figma-handoff-gateSkill
- figma-orientSkill
- figma-preflightSkill
- figma-slop-checkSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 27
Use figma-preflight, the file lock and the available write path.
- Distinctive: line 39
Verify origins on real controls, destinations, crossings, section-local placement, count and visible geometry at a useful scale.
≈ “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.
Files
Click-flow overlay
Draw a static overlay on an existing laid-out section: origin dots, rounded elbows and open arrows at destinations. It documents a flow; it does not create product screens, wire a missing prototype or authorize new destinations.
Inputs: sectionId and mode (from-prototype, explicit or heuristic
auto-layout); explicit pairs are {from,to}, without a label field. Reuse
known authorized targets. If no pairs are found, report the gap instead of
drawing an empty success. Heuristic adjacency needs visual confirmation and
must not silently turn row order into a product decision.
Use figma-preflight, the file lock and the available write path. Design does
not support createConnector/cloning existing CONNECTOR nodes; use this
skill’s references/draw-overlay.js, parameterized without rewriting its
fragile coordinate logic. The official use_figma path was not validated by
this repo; obey its current runtime instructions and verify every result.
overlay-details.md preserves configuration, geometry, page/section coordinates, mode semantics, dropped pairs, capture and cleanup recipes. Read the applicable sections when drawing or diagnosing. The recipe replaces the prior named overlay, so scope/ownership of that target must be correct. Timeout/partial error requires read-back before rerun.
Verify origins on real controls, destinations, crossings, section-local placement, count and visible geometry at a useful scale. Use plugin capture when available and respect REST budgets. Keep project accent/canon instead of forcing the default red. Split a dense graph when necessary for readability, not by an arbitrary task-wide count. Report ids and dropped/uncertain pairs.
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
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.

