- Home
- Skills
- Frontend & Web Apps
- Figma Click Flow
Works with the AI Agents you already use
Figma Click Flow
Draws click-flow arrows from tappable elements to their destination screens on a Figma section, for static handoff.
Free
About this skill
Draws a click-flow overlay on a section of laid-out Figma screens for static handoff: a dot on each clickable element, an elbow line with rounded corners and an open arrow at the destination screen. figma.createConnector is not a function in Figma Design files, so each connector is emulated with one SVG import (recipe in references/draw-overlay.js).
What it does:
- Finds pairs from prototype reactions (click, press or tap that navigates or opens an overlay), from an explicit list of element-to-screen pairs, or from rows of screens in the layout.
- Returns dropped pairs with a reason (node not found, outside section), and stops with a warning when it finds no pairs.
- Draws into one frame named "flow-overlay · click-connectors". A rerun removes the old frame first.
- Stroke color, stroke weight and corner radius are inputs (defaults #E5484D, 4 px, 12 px).
Requires the figma-canon and figma-preflight skills. Writes to the canvas through figma-console-mcp (figma_execute). The recipe also guards for use_figma on the official Figma MCP server, a path this repo has not run.
Part of figma-maxxing, free and MIT on GitHub: https://github.com/thiagoxikota/figma-maxxing
The use_figma path on the official Figma MCP server has not run in this repo. The auto-layout mode is a heuristic: it counts only portrait screens (height/width at least 1.3), so desktop or landscape screens return drawn: 0 until that constant is lowered, and rows that mix scenarios can produce wrong connectors. Each connector is a single L-shaped route, so lines can cut through unrelated screens; the skill's fix is a larger corner radius or splitting the section. Above 40 connections the skill says to split the section first. Pairs whose endpoints fall outside the section's bounding box (for example cross-page links) are dropped and reported. figma_execute times out at 5000 ms by default (30000 ms max); after a timeout or error, read the figma-canon atomicity reference before rerunning, because the recipe deletes the old overlay before drawing the new one.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts
File Scopes
Writes go into the open Figma Design file through the MCP tool (figma_execute or use_figma): one overlay frame inside the chosen section, removed and redrawn on each rerun. The recipe also switches Figma's current page to the page that holds the section. Nothing is written to local disk. references/draw-overlay.js is a figma_execute body that runs inside Figma's plugin runtime, not a Node script; it makes no network call and reads no environment variable, and the skill runs no shell command. Local reads are its own reference file and the figma-canon references it links. The MCP server it relies on is a separate install with its own access; the README says figma-console-mcp needs a Figma personal access token.