deck-setuplisted

# deck-setup — extracting a presentation template `/fig:deck` uses the team template's coordinates, colours, and typography exactly as they are. Where those values come from is this skill. **It does not read a remote template on every run** — it reads local assets extracted here once. **The premise**: never invent a value. Where an observation is ambiguous, leave it empty rather than fill it. An empty slot is read by `/fig:deck` as "that archetype does not exist", and it picks another. Mix up "not there" with "could not measure" and the deck quietly drifts away from the template. **Prerequisites**: always load `figma:figma-use` and `figma:figma-use-slides` before calling `use_figma`. Step 2 (measure) is **zero writes** — the script only `return`s a report. **Open with what this produces.** After this, `/fig:deck` builds slides from your own template's archetypes rather than a generic layout. Ten to fifteen minutes with the template to hand, and one thing is asked of you that MCP cannot do — applying the template. The template file itself is never touched. Name each step as it begins. ## When to invoke - Using `/fig:deck` for the first time in a new environment, at a new company - The team template has been revised and the values have moved - The assets folder is missing, or `/fig:deck` has stopped with "no assets" ## When NOT to invoke - Building the deck itself → `/fig:deck` - Extracting design-file conventions → `/fig:setup` (a separate thing. This one is for Slides