slides

Attach the .pptx file and the skill calls importPptx with the file path in attached_assets. The import callback handles the entire conversion, so no manual slide building, templates, or content outlines are needed.

Request a presentation, pitch deck, or slides and the skill builds a React + Tailwind app with one component per slide in src/pages/slides. It writes all files in one batch, updates slides-manifest.json, then runs validate-slides before presenting.

The workspace visual editor must map each DOM element back to a specific line in the JSX source. Dynamic generation breaks that mapping, so every element must be written as static inline JSX with Tailwind spacing instead of <br/> tags.

Yes, the workspace UI provides PPTX export and the /allSlides route renders every slide for screenshot-based export to thumbnails, PDF, and PPTX. Slides must render all content visibly on load for export compatibility.

Slides must be statically visible on load for screenshot-based export, so buttons, hover effects, and animations are disabled by default. Animations are only added when explicitly requested, scoped per slide and disabled in the /allSlides view.

Files in public/ must be prefixed with import.meta.env.BASE_URL since decks are served under a dynamic base path. User-attached files imported via @assets/... are resolved by Vite and need no prefix.