Install it once, then run the workflow

Requirements

Installing either kit is light. Building and rendering is not: it happens on your machine, so your machine needs the tools.

npx bountex-motion doctor checks every row above in one command and tells you what is missing.

Quickstart

Three steps, one of which you do in the terminal twice. Run them from the project you want the work to be about.

1. 01Activate the license

   Sends the key once, registers this machine as a device, and writes the credential to your user config. If this machine already holds a seat, this is a reactivation and costs nothing.

   $npx bountex-motion activate <license-key>Copy
   What you will see

   Copy

   ✓ License key accepted
     plan      Founding — $7.49/month
     status    active
     seats     0 of 3 devices
     license   BM-7K2M…4RZ6
   
   ✓ Device registered
     id        7F3A9C2E1B4D5068
     name      MacBook-Pro (darwin arm64)
     token     ~/.config/bountex-motion/config.json (0600)
   
   Next: npx bountex-motion install film

2. 02Install a kit

   Detects which AI coding tool this project uses, downloads that kit’s artifact for it, verifies every file against its SHA-256, and writes only the paths that tool reads. The kit argument is optional: install on its own installs film.

   $npx bountex-motion install filmCopy

   $npx bountex-motion install reelCopy
   install film — what you will see

   Copy

   ✓ Detected harness: OpenCode (.opencode)
   ✓ Downloaded film v1.1.0 for opencode
   ✓ Verified every file against its SHA-256 (digest 4a7c1e9b…)
     .opencode/skills/bountex-motion/SKILL.md
     .opencode/commands/bountex-motion.md
     .opencode/command/bountex-motion.md
     .opencode/plugins/bountex-motion.js
   ✓ Install receipt recorded for future updates
   
   Start a fresh session in OpenCode, then run /bountex-motion

   Installing the Reel Kit prints the same transcript with kit reel, skill bountex-motion-reel, and trigger /bountex-motion-reel.

3. 03Run it inside your tool

   Start a fresh session so the tool picks up the new files, then use the trigger for the kit you installed. Anything after the trigger is project input — a URL, a path, or a sentence.

   $/bountex-motion https://yourproduct.comCopy

   $/bountex-motion-reel https://yourproduct.comCopy

   With no input, the default flow of that kit starts by inspecting whatever is in front of it and asking you only what it cannot work out. The first command it runs on its own is a playbook fetch, not a build.

Supported harnesses

Both kits, 7 file layouts. The installer detects the tool from marker directories in your project and installs into the first match; force one with --harness, write every layout with --all. Each kit registers its own skill and its own trigger, so both can be installed into the same tool.

Everything is written inside those roots, plus two exceptions worth knowing: Cursor also reads each kit’s skill from .claude/skills/, and Codex CLI also reads an agent card from .codex/agents/. The only other write is the managed block in your tool’s own instruction file, bounded by markers so the rest of that file survives an update byte for byte.

The workflow

Both kits share the same shape — inspect, decide, write it down, build, hand it to an independent critic — but they differ in what leads: a story, or a beat. Each kit has its own phase table and its own order. Your agent loads each phase from the server immediately before it does that phase’s work; it does not improvise one from memory and it does not reuse one from a previous session.

Fetching a phase

Phase ids are exactly the ids in the tables above — nothing else is accepted, and a phase id belongs to one kit, so fetching a reel phase needs --kit reel. A mode is not a separate list either: it is every phase whose usedBy column names it, read from the selected kit — so --mode brief --kit film fetches exactly the phases marked brief in that kit.

The output is Markdown on stdout, held in memory. Do not redirect it into a file and do not paste it into a commit: the skill treats a fetch that cannot be made as a hard stop, and treats a copy of the playbook on disk as a licence breach.

Modes

A mode decides how far the workflow goes and which phases it loads. Pass it as the first word after the trigger, or to playbook --mode. Mode ids belong to one kit, so each kit has its own table below, ending with the empty invocation that runs the default flow.

Project files

Each kit keeps its state in files under its own directory in your repository — video-project/ or motion-project/ — because files are the source of truth and a chat log is not. The workflow creates only what the mode needs: no empty scaffolding.

video-project/
├── creative-brief.md      canonical brief (mode: brief)
├── production-prompt.md   filled universal prompt (mode: prompt)
├── storyboard.md          shots + per-ratio adaptation plan
├── critic-ledger.md       round / problem / change / result
├── quality-report.md      final critic verdict against the bar
├── human-review.md        what you should check with your own eyes
├── src/                   HyperFrames compositions
├── assets/                logos, UI, fonts, images, audio
├── references/            studied references (principles, never copies)
├── renders/               outputs
└── audio/                 music, SFX, mixes

motion-project/
├── concept.md           concept, devices, audio, beat sheet, storyboard
├── critic-ledger.md     round / problem / change / result
├── quality-report.md    final critic verdict against the bar
├── human-review.md      what the human should confirm personally
├── src/                 HyperFrames compositions
├── assets/              logos, UI, fonts, images
├── audio/               music, SFX
└── renders/             outputs

None of these files are playbook content and none of them leave your machine. They are yours to edit: they are also the first thing the workflow reads when you come back to a project weeks later.

CLI reference

Every command is run through npx, so there is nothing to keep up to date globally: npx bountex-motion <command>.

Flags

Exit codes

A non-zero exit means the command did not finish. Codes 3 and 4 print the server’s hint verbatim — that hint is the fix. Code 5 means nothing was written to disk.

Rate limits

Limits exist so one runaway session cannot exhaust a shared server. Exceeding one returns a message with the number of seconds to wait, and the CLI exits 1.

Devices & seats

Updating

Troubleshooting

The eight failures people actually hit, with the message each one prints and the fix. If none of them match, run npx bountex-motion doctor and send us what it says.

• 01 The terminal says the command does not exist

  The exact error

  Copy

  bash: bountex-motion: command not found

  There is nothing to install globally, so call it through npx: npx bountex-motion <command>. If npx itself is missing, Node is not on your PATH — install Node 20 or newer and open a new terminal. If npx refuses to fetch, add --yes.

• 02 A kit installed but my tool does not know about it

  The exact error

  Copy

  No skill named "bountex-motion" and no /bountex-motion command in the tool’s command list.
  No skill named "bountex-motion-reel" and no /bountex-motion-reel command in the tool’s command list.

  Check that the install root for your tool exists in the project (see the harness table above). Autodetection picks the first marker it finds, so a project that contains two tools needs --harness <id>. Both kits install into the same roots but register different skills and triggers, so a trigger that is missing usually means that kit was never installed here — install it, then reload. Most tools only scan at start-up: open a fresh session or reload the window. For the two plugin-based tools, run the plugin install step printed after install.

• 03 The trigger does not appear in the tool

  The exact error

  Copy

  /bountex-motion is not in the command or slash-command list.
  /bountex-motion-reel is not in the command or slash-command list.

  Not every tool uses a slash command. Film Kit: Codex CLI has none — ask it to run the bountex-motion skill by name; GitHub Copilot uses @bountex-motion; Kimi Code needs /plugins install .bountex-motion/film, a fresh session, and then /bountex-motion:film. Reel Kit: Codex CLI has none — ask it to run the bountex-motion-reel skill by name; GitHub Copilot uses @bountex-motion-reel; Kimi Code needs /plugins install .bountex-motion/reel, a fresh session, and then /bountex-motion:reel. For every other tool, reinstall with --harness <id> and reload. --global puts it outside the project, which some tools need.

• 04 The license is not recognised, or a phase is refused

  The exact error

  Copy

  Error: not_entitled — This license cannot fetch that phase. (code: not_entitled)

  Run npx bountex-motion status. If the key is unknown, re-check the receipt email — keys are Crockford base32, so an O is a zero, an I or an L is a one, and a U is a V. If the status is past_due, the subscription needs a payment: open the billing portal from the dashboard or the link in the receipt. If it reads revoked or expired, the license has ended.

• 05 Activation refuses with a seat error

  The exact error

  Copy

  Error: device_limit_reached — This license is active on 3 of 3 devices.

  Run npx bountex-motion devices to see which machines hold the seats, then npx bountex-motion deactivate <id> for one you no longer use. Reinstalling on a machine that already holds a seat never consumes an extra one, so activating the same laptop again will not hit this.

• 06 A phase fetch fails mid-session

  The exact error

  Copy

  Error: rate_limited — Too many playbook fetches for this device. Retry after 43 seconds. (limit: 60/hour)

  Wait for the Retry-After the message names, then fetch again, or fetch by mode to load several phases in one call. If the error is device_unknown or subscription_inactive instead, run npx bountex-motion status and fix the license first. Do not carry on without the phase: the skill tells the agent to stop rather than improvise it, and that instruction is the product working as intended.

• 07 The render fails with unknown HyperFrames flags

  The exact error

  Copy

  error: unknown option '--<flag>'

  The composition contract is written against a specific HyperFrames CLI surface, and an older or newer binary can have moved a flag. Run npx hyperframes --version, upgrade the renderer with npx hyperframes upgrade, and re-run the render spike on one composition before rendering the whole piece. If a flag genuinely no longer exists, the build phase is the place that has to change — say so rather than hand-editing the composition around it.

• 08 The build finishes but nothing renders

  The exact error

  Copy

  renders/ is empty after the render command exits 0. (Often preceded by: Could not find Chrome, or ffmpeg: command not found)

  Check the three render requirements: Node 22 or newer, FFmpeg on PATH, and a Chrome or Chromium binary. npx bountex-motion doctor tests all three in one command. Then re-run the render spike on the single hero composition before the full build, and read the quality report — if the spike never passed, the full render is the wrong next step.

Support