← ClaudeAtlas

design-flowlisted

Design screens in Figma with their flowchart drawn right beside them, so each page states what it shows and how it behaves, and a developer can build it from one look. Uses the Figma MCP. Use when the user shares a figma.com/design URL and wants to analyze how the file is organized, add a flow to a screen or menu, design a new page with its flow, check which screens still lack a flow, or turn screen + flow into an implementation checklist. Trigger on "flow on the design page", "flowchart next to the screen", "design with flow", "user flow in Figma", "screen flow handoff", "ออกแบบหน้าพร้อม flow", "ใส่ flowchart ข้างหน้าจอ", "flow ของหน้านี้". Not for standalone FigJam boards with no screens (use figma-generate-diagram) or for plain design-to-code with no flow (use figma-design-to-code).
th3r-dev/th3-skills · ★ 2 · Web & Frontend · score 66
Install: claude install-skill th3r-dev/th3-skills
# Design Flow A screen in Figma shows what the page looks like. A flowchart placed beside it shows what the page does: which decisions it makes, where it goes on success, which alert it shows on failure, and which role can see it. This skill keeps the two together on the same canvas and in the same naming scheme, so the handoff becomes one checklist per screen. It works on the file's **existing** conventions. It reads them before it draws anything and does not bring in a style of its own. Setup, everyday use and the step-by-step agent runbook are in [README.md](README.md). Read its Part 3 before the first Figma call in a session. ## Before any call 1. Parse the URL: `figma.com/design/<fileKey>/<name>?node-id=<a>-<b>` gives you `fileKey` and `nodeId = "<a>:<b>"`. 2. `create_session` with the fileKey and a one-line task description. Pass the returned `sessionId` on every later file-tool call. 3. Load the official Figma skills when they're needed. Don't copy their content here: - `figma-use` before **any** `use_figma` call. Add `figma-generate-design` before a call that makes visible changes. - `figma-design-to-code` before `get_design_context`. - Tool order and limits come from https://github.com/figma/mcp-server-guide. 4. **Principles.** Read the sibling sub-skill [`../core/SKILL.md`](../core/SKILL.md) (design-core). Its composition, writing and interface-quality rules apply to every screen, state screen and flow step this skill makes, and its revie