AgentsOne prompt, any agent
Your agent
sets it up.
Make films with your own agent, with no setup by hand. One prompt checks your machine, installs Shaderera, starts a film project and gives the agent eyes.
Pick your agent6 ways in
Works in any agent
with a terminal.
- 01Installs as a plugin; the skills come with it.
Claude Code
- 02Skills through npx skills.
Codex
- 03Skills through npx skills.
Cursor
- 04Skills through npx skills.
Gemini CLI
- 05Skills through npx skills.
OpenCode
- 06Anything that can run a terminal command.
Any agent
How it goesOnce per machine
Three steps.
Run the install prompt in your agent.
Paste it into a new thread. It checks Node.js and ffmpeg, installs only what is missing, installs the skills, starts a film project and adds the MCP server.
Start a new thread in the project folder.
So the agent picks up the project's own instructions, skills and MCP server.
Write your first prompt.
Describe the film in your own words: what it is for, its format and length, the words on screen, the music and any brand files.
“Make a 15-second 9:16 teaser for our running shoe: the shoe turns once on a dark set, the line 'Built for the last mile' lands on the beat, and the logo holds for the last 2 seconds. Run check, show me a contact sheet, then render.”
The promptSame text as INSTALL.md
Read it before
you run it.
It installs only what is missing, and only with tools your machine already has. It never installs a package manager, never changes a Node.js or ffmpeg that already works, and asks before anything that needs administrator rights.
Goal:Make sure Node.js 24 or newer and ffmpeg are installed, install the Shaderera skills, and starta Shaderera film project.Check first:Run `node --version` and `ffmpeg -version`.If Node.js is installed and its major version is 24 or higher, do not install or change Node.js.If ffmpeg runs, do not install or change ffmpeg.Install policy:Install only what is missing.Use a package manager only if it is already installed.Do not install Homebrew, winget, Chocolatey, Scoop, nvm, fnm or another package manager just forthis task.Ask the person before anything that needs administrator rights.If Node.js is missing or older than v24:- macOS: use Homebrew if it is installed; otherwise the official Node.js `.pkg` installer.- Windows: use winget if it is installed; otherwise the official Node.js `.msi` installer.- Linux: use the system package manager if it offers Node.js 24 or newer. On Debian/Ubuntu or RHEL/Fedora-compatible systems, use the official NodeSource instructions for Node.js 24 or newer. Otherwise use the official standalone Linux binary for this architecture.Download Node.js installers and binaries from https://nodejs.org/download/release/latest/If ffmpeg is missing:- macOS: `brew install ffmpeg` if Homebrew is installed; otherwise a static build linked from https://ffmpeg.org/download.html- Windows: `winget install --id Gyan.FFmpeg` if winget is installed; otherwise a release build linked from https://ffmpeg.org/download.html, with its `bin` folder added to PATH.- Linux: the system package manager (for example `sudo apt install ffmpeg`); otherwise a static build linked from https://ffmpeg.org/download.htmlChrome is needed only for films drawn as a web page (the browser host). Do not install it now.Verify:Run `node --version` and `ffmpeg -version` again. Continue only if Node.js is 24 or higher andffmpeg runs. Open a new terminal first if PATH changed.Install the skills:- In Claude Code: run `claude plugin marketplace add shaderera/shaderera`, then `claude plugin install shaderera@shaderera`. Tell the person to run `/reload-plugins`.- In any other agent: run `npx skills add shaderera/shaderera -g -y`.Start a film project:Ask the person where the project should go and what to call it. The default is a folder named`my-film` in the current directory. Then run, in order: npx create-shaderera@latest <name> cd <name> npm install npx shaderera doctor npx shaderera check`doctor` must not report anything an mp4 render needs as missing, and `check` must pass.Give yourself eyes:Add a stdio MCP server named `shaderera` that runs `npx shaderera mcp` in the project folder,the way your agent adds MCP servers. In Claude Code, from the project folder:`claude mcp add shaderera -- npx shaderera mcp`Success message:Tell the person they are set up, where the project is, and what to do next:Start a new thread in the project folder, then describe the film in your own words: what it isfor, its format and length, the words on screen, the music, and any brand files. For example:"Make a 15-second 9:16 teaser for our running shoe: the shoe turns once on a dark set, the line'Built for the last mile' lands on the beat, and the logo holds for the last 2 seconds. Runcheck, show me a contact sheet, then render."FAQ05 answers
Questions.
- 01What does the install prompt install?
- Only what is missing: Node.js 24 or newer and ffmpeg, if they are not there, then the Shaderera skills, a new film project and the project's MCP server. It installs them with a package manager your machine already has, or with the official installers.
- 02What does it never touch?
- It never installs a package manager (Homebrew, winget, Chocolatey, Scoop, nvm, fnm or any other), and it never changes a Node.js or ffmpeg that already works. It does not install Chrome.
- 03Will it need administrator rights?
- Only if something missing needs them to install, and the agent asks you first.
- 04Do I need Chrome?
- Only for films drawn as a web page (DOM and WebGPU in a page, the browser host). Films drawn with Canvas2D, WebGPU or three.js on the Node host do not need it.
- 05What does the MCP server do?
- It gives the agent eyes: it renders any moment of the film as an image, inspects the film's state, and traces a pixel back to the line of code that drew it.