# Install neoslides

neoslides is a Claude Code skill: it turns a product idea into a clickable Next.js
prototype and an animated in-browser talk, and `npm run share` shares it as a link.

These steps are written for a coding agent; a human can follow them too.

## Requirements

- Node.js 20 or newer (`node -v`). If it is older or missing, tell the human and stop.
- git.
- Claude Code.

## Install or update (agent)

Run this; it clones the skill, or updates it if it is already there:

```bash
if [ -d ~/.claude/skills/neoslides/.git ]; then
  git -C ~/.claude/skills/neoslides pull --ff-only
else
  git clone https://github.com/maksspace/neoslides ~/.claude/skills/neoslides
fi
```

Then tell the human: the skill is picked up by new Claude Code sessions, so they
may need to start a new session (or restart Claude Code) before asking for it.

## Install as a plugin (human)

Plugin commands must be typed by the human in Claude Code, not run by the agent:

```
/plugin marketplace add maksspace/neoslides
/plugin install neoslides@neoslides
```

## Use it

Ask Claude Code to pitch or demo a product idea ("make slides for …"). In the
generated project, `npm run share` builds a static export, signs in through the
browser (Google, once), and prints a link like `https://k7f3x9q2ab.neoslides.app/`.

- `npm run share -- --new`: publish as a new deck instead of updating.
- `npm run share -- --delete`: delete the deck in `.neoslides.json`.
- `npm run share -- --list`: every deck on the account.
- `npm run share -- --logout`: forget the saved token.

An agent can run all of these for the person; only the Google sign-in in the browser
needs the person.

The project is built on your machine; only the static files in `out/` are uploaded.
For CI, create a token at https://neoslides.dev/account and set `NEOSLIDES_TOKEN`.

Decks are unlisted; anyone with the link can view. Limits: 20 decks per account,
50 MB and 2,000 files per deck. Manage decks at https://neoslides.dev/account.