figma-orient

Map the territory before moving in it. Read-only on the Figma file: no canvas writes. The only thing this skill writes is the map file (see Persistence). Build the mental map in whatever shape fits the file (pages, canonical screens, design system source, WIP zones). What follows is the environment knowledge you cannot guess on your own.

Read paths (the part that matters)

Tool names are written as base names. The prefix depends on the client.

PRIMARY: the figma-console MCP server through its Desktop Bridge (local plugin, no rate limit).

1. figma_get_status: confirms the Bridge and which file it is paired with. Every primary read below goes through the Bridge.
   • Disconnected and a write comes next: invoke the figma-bridge-doctor skill. Disconnected on a read-only orientation: the FALLBACK below covers only a trivial read, and anything larger needs the Bridge back, so invoke figma-bridge-doctor then too.
   • Paired with a file other than the fileKey of the pasted URL: have figma-bridge-doctor switch the Bridge to that file before reading (see "The active file DRIFTS on its own in the middle of a write" in that skill). Passing fileKey to figma_execute covers step 2 only; for the screenshot, that skill pins the active file with figma_navigate and lock: true. Otherwise the map gets built from the wrong file.
2. figma_execute with getNodeByIdAsync + findAll: the structure plus all the text content (the UI copy) of a whole page or section in ONE call. The script must return the data it collected (console.log is not an output channel). Return names, ids, sizes and text, and trim long strings.
3. figma_capture_screenshot: plugin exportAsync, the visual anchor.
4. figma_get_variables: the design system variables.

Rules for the step 2 dump: