-
Notifications
You must be signed in to change notification settings - Fork 0
docs: copy-paste setup block for AI coding agents #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -73,6 +73,36 @@ node dist/cli/index.js doctor # check Chromium + ffmpeg are installed | |
|
|
||
| > Browser + video need Chromium and ffmpeg: `npx playwright install chromium` and an `ffmpeg` on your PATH. | ||
|
|
||
| ### 🤖 Or: let your coding agent set it up | ||
|
|
||
| Already living in **Claude Code, Codex, opencode, Cursor, or Cline**? Don't run the | ||
| steps by hand — paste the block below in as your task, fill in the two `<...>` | ||
| placeholders, and let the agent clone, build, install Chromium/ffmpeg, and film your app: | ||
|
|
||
| ```text | ||
| Set up and run supercut (https://github.com/Co-Messi/supercut) to make a launch | ||
| video of my app. Steps: | ||
|
|
||
| 1. git clone https://github.com/Co-Messi/supercut && cd supercut | ||
| 2. npm install && npm run build | ||
| 3. npx playwright install chromium | ||
| 4. Ensure ffmpeg is on PATH (install it if missing), then run: | ||
| node dist/cli/index.js doctor | ||
| 5. Ask me which LLM provider to use, then create a .env: | ||
| - DeepSeek: SUPERCUT_PROVIDER=deepseek + DEEPSEEK_API_KEY=... | ||
| - OpenRouter: SUPERCUT_PROVIDER=openrouter + OPENROUTER_API_KEY=... | ||
| 6. Film it (my app is running locally — fill these in): | ||
| node dist/cli/index.js generate --url <MY_APP_URL> --repo <MY_APP_SOURCE_DIR> --yes | ||
| 7. When it finishes, open out/final.mp4 and show me the result. | ||
|
|
||
| No API key handy? Skip the .env and use the no-LLM path instead: | ||
| node dist/cli/index.js record --recipe examples/demo.recipe.json --out out/take | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
In this pasted-agent workflow for filming “my app”, the no-LLM fallback stops using Useful? React with 👍 / 👎. |
||
| node dist/cli/index.js render --take out/take --out out/final.mp4 | ||
| ``` | ||
|
|
||
| Same block works in any agent — they all take a pasted task. `--repo` is optional but | ||
| makes the director read your routes so it films real panels, not just the landing page. | ||
|
|
||
| Help the director understand a deeper, multi-page app by pointing it at the source: | ||
|
|
||
| ```bash | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the agent workflow, the preceding
generatecommand does not pass--out, and the CLI defaultsgeneratetoout/generate(src/cli/index.ts:170) before writingfinal.mp4inside that directory (src/director/generate.ts:238). Following this instruction after a successful generate run will therefore try to open a missingout/final.mp4(or a stale file from another render); useout/generate/final.mp4here or pass--out outin the generate command.Useful? React with 👍 / 👎.