← ClaudeAtlas

openpress-create-slidelisted

Use when the user wants to create, draft, scaffold, edit, reorder, add, or revise an OpenPress slide deck or presentation from topic selection through outline, narrative, visual style, production, and tuning; create or revise slide-style templates; use the slide CLI to add/remove/reorder/skip template-backed slides; define slide theme tokens; convert data-prop layouts to frame/object JSX; or reference a specific slide, template, opener, or column page. This skill owns stable slide delivery workflow, slide Press creation, slide editing, slide-style template authoring, core Object API composition, theme token setup, Tailwind semantic slide styling, deck narrative, slide density, assets, motion discipline, and verification.
quan0715/open-press · ★ 14 · Data & Documents · score 73
Install: claude install-skill quan0715/open-press
# 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, template registry, theme tokens/CSS, Tailwind semantic styling, 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. | --- ## Delivery Workflow Every deck follows four delivery phases. Do not jump straight to JSX unless the user asks for a narrow code edit. ``` TOPIC → STORY → STYLE → PRODUCE ``` ### 1. TOPIC Lock the presentation intent. Output a short working brief, then proceed with reasonable assumptions unless a missing answer would materially change the deck. | Decision | What to capture | | --- | --- | | Topic | What the deck is about | | Audience | Who must understand or decide | | Objective | Inform, sell, align, teach, report, or persuade | | Core promise | The one sentence the deck must make believable | | Constraints | page count, deadline, assets, brand, export target | Do not ask the user to write YAML before seeing anything. If details are missing, state assumptions and keep moving. ### 2. STORY Create the content outline and narrative arc before desig