Troubleshoot the actual file, runtime, or rendered result.
Start from the observed symptom. Ask the Agent for exact paths, commands, errors, and performed checks instead of accepting a generic completion message.
Files and projects
Check source access, write access, absolute paths, and the editable project before investigating presentation rendering.
The Agent cannot read my PPT or PPTX
Confirm the absolute source path and read permission. Ask which slides or objects could not be extracted. If direct parsing is unavailable, provide a PPTX, PDF, or rendered slide images. Keep the original PowerPoint unchanged and do not allow guesses about unreadable content.
The presentation was generated but not saved
Ask for the absolute project path and the files actually written. Verify that slides.md and package.json exist. If the Agent only returned code or a preview in chat, open a writable folder and ask it to create the project there.
I cannot find or reopen the project
Open the exact source folder previously reported by the Agent, not a PDF, PPTX, screenshot, portable directory, dist directory, or offline.html. Ask the Agent to inspect the existing project before it continues editing.
Runtime and outputs
Use the actual package scripts, distinguish direct-file output from HTTP builds, and inspect the real exported file.
Slidev does not start
Confirm that the project runtime and package manager are available, install dependencies from the project folder, and use the scripts in package.json. Ask for the exact command and complete development-server error.
Build or export fails
Run the normal build first and fix missing imports, fonts, local assets, or runtime errors. Verify the project’s actual export command and report the failing slide and complete error. A preview screenshot does not prove that build or export works.
offline.html does not open or is incomplete
Rebuild it from the current source with npm run build:offline. Copy the single file to another location and open that copy through file:// in a current Chromium browser. If assets or interactions fail, report the console error and rebuild rather than patching the HTML.
portable/index.html or dist/index.html does not open when double-clicked
This is expected. Keep the complete directory together and serve it over HTTP, for example with python3 -m http.server 4173 --directory portable. Use the verified single-file offline.html when direct file:// playback is required.
The exported PPTX has no interactions or editable text
This is expected for the Slidev PPTX compatibility copy: slide content is image-based. Use the Slidev web version or offline.html for interactions and keep the source project for editing.
Content and quality
Fix the narrative, evidence, layout, brand protection, or stale preview in the editable source and then rebuild outputs.
A slide is too dense
Ask the Agent to prioritize, compress, or split the content according to the requested scope. Do not solve density by shrinking text, stacking more bullets, or hiding important qualifiers.
Metrics or factual values are missing
Keep explicit placeholders until the source material provides real values. Report the missing evidence and do not insert plausible-looking numbers merely to complete the design.
My latest edits disappeared
Confirm that the Agent changed the same source folder and that the preview server is running from it. Ask for the changed file paths, restart the correct project command, and rebuild every delivery copy. Never continue from an old export when the source exists.
A logo is covered, cropped, stretched, or too close to the edge
Return to the editable source. Preserve the complete lockup and aspect ratio, reserve positive safe-zone clearance, use a compatible background, and keep page numbers, sources, controls, masks, and seams outside that zone. Verify the actual rendered and exported pixels.