Slidev: use the official scaffolder to make developer presentation slides

Who it is for

This skill fits when you want a developer presentation and want the official scaffolder to start a slide project locally at once. It is positioned as presentation slides for developers. The official local main path is only one: first meet Node.js >= 20.12.0, then run npm init slidev. The materials also have an online entry and editor notes, but do not put them beside local init as interchangeable main paths. If your Node is below 20.12.0, or you do not plan to generate a project on this machine, do not run init yet.

It is for people who can already run Node and only need a slide project they can preview. It is not for people who have not reached the required version and want to change themes or extensions first. On the editor side, the materials mention an integrated editor or a VSCode extension; that is the editing surface, not a second installer. You can init without a talk outline, but do not expect the scaffolder to write a full script for you.

First try in 3 minutes

Use only this official install command:

npm init slidev

Prerequisites: first confirm Node.js >= 20.12.0. The Node download page is

https://nodejs.org/

This pass only initializes one new project. Do not ship it. Do not connect an online entry that is not written as the main path.

The install location is the local directory that npm init will create. Before running it, have the assistant restate the target directory and the Node version; run only after you confirm, because this writes to disk.

Success signal: a new slide project appears locally, and you can open the preview by following the scaffolder's own prompts. If the command fails, check the Node version first; do not switch to online creation that is not the main path. The materials do not write a default theme name or PDF-export steps. If init asks for a project name, use an empty directory so you do not overwrite existing files.

Usage examples

Example 1: create a developer deck locally. After confirming the Node version, run the official init. Generate only one project and open it to see whether the home page appears. The evidence covers npm init slidev, but it does not give prompt items or a template list. Anything beyond that must stop at "can init and open". Initialize only one directory at a time.

Example 2: edit slides with the integrated editor or the VSCode extension. After the project is up, change one page in the editing surface the materials name. The evidence covers integrated editor and VSCode extension, but it does not write an extension-marketplace ID or keyboard shortcuts. Do not treat editor install as another project scaffolder. Before editing a page, confirm you are changing the project you just initialized. First change one title or one note, confirm the preview updates, then consider more pages.

Limits

The local main path is only npm init slidev, and it requires Node.js >= 20.12.0. The materials also show the online address

https://sli.dev/new

That is not the recommended main path this time; do not put it beside npm init. Editor docs point to

https://sli.dev/guide/index#editor

https://sli.dev/features/vscode-extension

They only describe the editing surface. The first try stops at init and preview. Do not invent an installer that is not written, and do not repeat init before the directory is confirmed. If the Node version does not meet the requirement, stop at the runtime requirement; do not downgrade to an old command that is not written.