openpress-create-slidelisted

# OpenPress Create Slide `openpress-create-slide` owns artifact creation. The `openpress` skill owns CLI lifecycle: build, render, PDF, image, deploy, doctor, upgrade. ## Boundary | Owner | Scope | | --- | --- | | `openpress-create-slide` | Create, add, edit, or revise slide decks: structure, Tailwind semantic styling, layouts, UI primitives, assets, narrative. | | `openpress-create-pages` | Page-based documents. | | `openpress` | CLI lifecycle. | | `openpress-deploy` | Public deploy after explicit user confirmation. | | `openpress-apply-comments` | Pending `@openpress-comment` markers. | --- ## Creation Workflow Every slide deck follows four repeating phases. This is the main axis of all work. ``` PROPOSE → REFINE → DOCUMENT → ALIGN ``` ### PROPOSE Generate content and visual composition from intake. Start producing — do not ask the user to write YAML first. Present the first version as something to redirect, not a final answer. - New deck: scaffold `press.tsx` as an ordered `<Slide id />` index, then create each `slides/<id>/slide.tsx` with `export const meta` and a layout stub. - New slide: use `open-press slide add <id>` so the folder and index marker stay consistent, then edit `slides/<id>/slide.tsx`. - Choose `ui/` primitives based on content type; do not force the user to specify them. - If the user provides a reference image, read it and generate a YAML description before writing JSX — the image is the source of truth for that slide. **Authoring constraints