pneuma-slide

Automating slide deck design involves enforcing a file architecture with workspace, manifest.json, slides, and assets directories. The workflow applies structured phases from writing a design outline to scaffolding slides and filling content, ensuring consistent presentation composition.

The best way to structure a presentation workspace is enforcing a file architecture with workspace, manifest.json, slides, and assets directories. This organization supports design workflow phases from outlining to scaffolding and content population within a visual environment.

Create a slide deck design outline by writing a design_outline.md file. This initiates the workflow phases, guiding layout, typography, and accessibility guidelines before you proceed to scaffold the slides and populate the final presentation content.

Yes, the slide design workflow enforces accessibility and typography guidelines. During the review and content filling phases, it applies reusable design guidelines and layout patterns to maintain visual consistency and accessibility across the entire deck.

Yes, you can use existing design references and layout patterns for slide composition. The workflow provides reusable design guidelines ensuring consistency, allowing you to apply established layout patterns during the content filling and review phases.

Scaffolding slides with a structured file architecture requires strict adherence to the workspace, manifest.json, slides, and assets directories, alongside YAML frontmatter requirements in SKILL.md. Deviating from this structure disrupts the automated design workflow phases.