First run
The goal of this step is setup. /start verifies the environment, asks which track you’ll use, and captures the channel identity. You don’t make a video yet. This goes as far as the track and channel being set.
1) Run Claude Code in the base folder
Section titled “1) Run Claude Code in the base folder”If you went as far as cd my-channel in clone-and-install, run this in the same spot.
claudeWhen the prompt comes up, it quietly reads CLAUDE.md and the automation rules. You may not see much output on screen, which is normal.
2) Start with one line
Section titled “2) Start with one line”/startOr in natural language, 프로젝트 시작, “let’s make the first one.” Either way triggers the start router.
3) Environment verification
Section titled “3) Environment verification”/start checks the environment read-only. It looks at the common tools (ffmpeg, OPENAI_API_KEY) first, then verifies only the tools for the track you picked.
| Item | Track | If missing |
|---|---|---|
| ffmpeg | common | install guidance |
| OPENAI_API_KEY | common | env-var setup guidance |
| codex CLI | generative | install guidance. Without it, generative entry is blocked |
| yt-dlp | remix | install guidance |
| whisper-cli | remix (optional) | falls back to the Whisper API if absent |
It doesn’t install external tools automatically. Missing ones are only guided, and you install them yourself (or after explicit approval).
4) git history separation, only if you cloned
Section titled “4) git history separation, only if you cloned”If you got the base with git clone, /start inspects the origin URL and asks once. If you got it by making your own repository via Template, it’s skipped automatically.
5) Picking a track
Section titled “5) Picking a track”/start asks which track you’ll use. Pick among generative only, remix only, and both. This choice splits the next step. Generative goes to first-generative-video, remix to first-remix-video.
6) Channel identity
Section titled “6) Channel identity”/start captures the channel identity. Things like the platform (TikTok, Reels, Shorts), language, monthly cadence, and IP or characters. The answers are planted in _workspace/channel.json and .claude/state/channel.json. From the next session, it reads these files and works on top of the same channel identity.
When this step is done, here’s where you are: the environment is verified, the track is set, and the channel identity is planted in channel.json. There’s still no video. That’s normal.
Once setup is done, go to the spot for your track. Generative is first-generative-video, remix is first-remix-video.