Keep the source editable and rebuild every delivery copy.
A finished presentation is a real project folder, not only a preview or chat response. Review the source, rebuild current outputs, and keep the handoff explicit.
Move from request to a saved project
Create the source, inspect it in a real browser, repair the deck, and regenerate outputs from the final state.
Create and save
The Agent should write the Slidev project to a dedicated folder and report its absolute path and important files.
Run and inspect
Install dependencies, start the project with its actual package scripts, and inspect representative slides and interaction states in a browser.
Review and repair
Check story, evidence, visual system, typography, branding, motion, overflow, and export behavior. Fix observed defects before delivery.
Rebuild every requested output
After the final source or asset change, rebuild offline.html and every requested static or HTTP-hosted output. Do not reuse stale exports.
Report the handoff
Name the project path, development command and URL, offline.html, requested exports, performed checks, placeholders, and known limitations.
Review the deck as a presentation, not only as code
A successful build does not prove that the narrative, brand, evidence, or rendered slides are correct.
Story and decisions
Each slide should have one clear responsibility, and the sequence should lead the intended audience toward the requested conclusion or action.
Facts, sources, and uncertainty
Verify claims, labels, units, citations, and qualifiers. Keep missing values visible rather than replacing them with plausible-looking content.
Visual system and originality
Check whether typography, color, imagery, diagrams, and layout fit this subject and audience instead of falling back to a generic template.
Brand and logo integrity
Confirm complete logos, positive safe-area clearance, correct aspect ratio, suitable backgrounds, and no collision with page chrome or sources.
Rendered pages and states
Inspect representative slides at real viewports, interactions, reduced motion, print or static export, and offline playback. Check overflow and the browser console.
Deliver the right files for the job
The source project remains authoritative; offline, HTTP-hosted, PDF, and PPTX outputs are regenerated delivery copies.
| Output | Keep it for | Do not use it for |
|---|---|---|
| Slidev source project | Editing, rebuilding, reviewing, and future changes | Direct presentation on a machine that does not have the project environment |
| offline.html | A relocatable interactive single file that opens directly through file:// | Continuing to edit the presentation source |
| portable/ or dist/ | Interactive playback from a static HTTP server | Direct file:// playback or source editing |
| Static review, print, or distribution | Slidev interaction or continued editing | |
| PPTX compatibility copy | Static playback in presentation software | Native editable content, web interactions, or source continuation |
Resume from the source project
Open the same project folder, ask the Agent to inspect its current files, make the requested change, and rebuild affected outputs.
Do not continue from a PDF, PPTX, screenshot, portable directory, dist directory, or offline.html when the editable project exists. Those outputs do not contain the full authoring state.
Before changing anything, the Agent should identify the current project path, package scripts, source files, local assets, and existing conventions. After the change, it should rerun the affected browser, offline, and export checks.
- Keep one authoritative project folder.
- Record which files changed.
- Restart the correct preview if an old build is still open.
- Rebuild offline.html and requested exports after relevant source changes.