← ClaudeAtlas

extract-figma-speclisted

Use before or during Figma-driven implementation to extract returned design properties into atomized checks, compare them with code, and write a canonical results table.
YasuakiOmokawa/skills · ★ 0 · Data & Documents · score 70
Install: claude install-skill YasuakiOmokawa/skills
Structured Figma metadata is the value source; screenshots are orientation evidence only. Figma review comments are out of scope when the available metadata capability cannot retrieve them. ## Resolve inputs Use an explicitly supplied node/URL and plan path first, then values present in the current non-delegated session. Normalize URL `node-id=1-234` to `1:234`. A delegated run does not infer files from its working directory. Without an output path, return the results table in the final response. Until node selection and extraction succeed, every supplied output path is metadata only: never create, replace, or append to it, including diagnostics or evaluation reports. Early-stop reporting goes only to the final response. Resolve a Figma metadata capability and list accessible pages. If no tool exists, report that and stop. Retry one transient call failure; do not retry a missing node, missing tool, or ambiguous selection. If no node was supplied, compare page/node names with the request's concrete keywords and inspect enough descendants to select safely. Choose only a unique match. Generic labels such as `v0`/`v1` are not evidence. If synchronous clarification is unavailable, return candidates and stop. Report `正本抽出結果: 未生成`, the unresolved reason, and for unreachable metadata ask the user to open the target file in the Figma desktop app; do not fabricate rows. ## Extract For each selected node, obtain the available equivalents of: - metadata tree: elements, names, typ