Docs

Use Copy Prompt with your coding agent.

Copy Prompt gives your agent Slidev instructions, component code, usage examples, and no-fabrication rules in one payload.

Start here

Choose the route that matches what you have.

01 · PowerPoint

You have a PPT or PPTX

Give the agent the source file and a writable project folder. It should preserve the original PowerPoint, extract its structure and assets, then rebuild the content as a Slidev project before continuing the design.

02 · Existing project

You already have Slidev

Open the folder that contains slides.md and package.json, then paste the prompt there. The agent should inspect the existing theme, components, assets, and scripts before adding or replacing slides.

03 · New project

You have an empty folder

Use a dedicated writable folder. The agent can initialize Slidev in that folder, install dependencies, create the requested block or deck, and verify that it runs without touching unrelated files.

04 · No workspace

You have no folder or no write access

First create or select a dedicated folder and open it in your coding agent. If the agent cannot write there, it must say so and provide a file plan instead of claiming the project was saved. Continue only after you grant access or choose another folder.

Project lifecycle

From copied prompt to a project you can reopen.

01

1. Create and save

Paste the Copy Prompt into a coding agent that is opened on your project folder. A saved project is a real set of files on disk—not only a preview or chat response.

slides.mdcomponents/styles/public/package.jsonREADME.md

02

2. Run and check

Ask the agent to install dependencies and use the scripts in package.json. It should report the exact project path, preview URL, command, and any errors—not just say “done.”

npm installnpm run devnpm run build

03

3. Reopen and continue

Later, open the same folder in your editor or coding agent and say what you want to change. The agent should read the existing project first and continue from those files instead of generating an unrelated replacement.

04

4. Build and export

Keep the web project as the editable source. Build it for web delivery, or ask the agent to verify the project's PDF/PPTX export command. A Slidev PPTX export is image-based; animations and interactions remain available only in the web deck.

npm run exportnpm run export -- --format pptx

Delivery boundaries

Migration safeguards

PowerPoint migration is a rebuild

Slidev cannot faithfully import every PowerPoint layout, font, animation, chart, or embedded object as editable web components. The agent should preserve the source PPT/PPTX, document anything it cannot read, and recreate the narrative and visuals in the new project rather than overwrite the original.

Missing information stays visible

If source facts, assets, citations, or fonts are unavailable, the agent should use explicit placeholders and report the gap. It should never invent content merely to make the migrated or generated deck look complete.