design-slideslisted

# Slides A deck built on defaults is recognized at once: every slide on one template, the main point given the same weight as the minor ones, no product in sight, placeholders instead of data, an export nobody opened. This skill puts the story before the layout, takes the style from the person or the company, and checks the deck in the form it will be sent in. Text on slides follows the `writing-texts` skill, with the person's and the product's voice. The deck's state lives in `<project>/.claude/slides/<deck>.md`, one file per deck (format in `references/story.md`). ## Which branch | What exists | Branch | |---|---| | No deck | new deck | | A deck; asked to change part of it | partial edit | | A deck; asked to look at it or assess it ("what's wrong?") | review without edits | | A deck; asked to check it and hand it over or send it | pre-send check | | A deck; asked to redo it entirely | full rework | ## New deck Each step ends where it says "wait". The next step starts only after the person answers. 1. **First reply: questions and a plan, no slides.** One message: - questions the request does not answer: who is watching and what they decide; how the deck will be used (shown live, sent as a file, edited by others, printed, animated) and in which format; - a plan per `references/story.md`: a table "claim · slide job · layout"; - data questions: every claim without a number or a source becomes a question. Such a claim does not go on a slide until the data exists.