brutalist

The pared-down Brutalist video toolkit: builders, personas, and shared production doctrine, with local Kokoro voices (Onyx am_onyx, Bella af_bella).

Free by default — Kokoro, Manim, Remotion, no account required. Optional: a Higgsfield CLI login (higgsfield auth login) unlocks AI video beats. Absent = the free path (Ken Burns stills) runs silently. No ElevenLabs, ever.

Read HOW-TO.md — what Brutalist is, install, the three core builders, and the worked examples. CLAUDE.md has the session rules for agents.

./setup --install     # deps + Remotion node modules + the Kokoro model (~340MB, auto-downloaded)
./art --list          # the skills
./art keys            # check optional Higgsfield login + SI key

Builders

Brands (what a SEIS or Northeastern user needs, all in this repo)

Nothing else is needed from any laptop: clone, ./setup --install, and the SEIS skills run on these files.

Personas

Doctrine (not entry points — inherited by builders)

Game walkthroughs

Ask your agent: godot-waikthrough walker /path/to/walker-jumpman (or use the alias godot-walkthrough). Without walker, it opens on gameplay; with it, the Claude prompt asks Walker to convert the game’s GDD, and beat two summarizes what was actually built. Both use real gameplay, Liam’s on-screen riffs, and the regular outro—not a game-themed sound/voice ending. The skill renders locally for review; it does not publish.

./art godot-waikthrough --help and ./art riff --help show the agent workflows. ./art godot-waikthrough --check /path/to/reel runs the read-only coverage gate. As with the other builders, invoking ./art alone shows the skill to follow; it is not an autonomous film-render command.

Note: the Kokoro voice model is not in this repo (GitHub’s 100MB file limit) — ./setup --install fetches it once from the kokoro-onnx releases.

Game trailers

Ask your agent: godot-trailer /path/to/game-package (alias game-trailer). It reuses the walkthrough’s capture contract and any same-build walkthrough captures, but it selects: one hook, one idea escalated, gameplay in the first five seconds, cut to music, one call to action on the last card. No Claude bookends or channel outro; no AI footage; planned features never appear. Music-only by default; add voice for a few sparse lines in Liam’s voice (Kokoro am_onyx), each backed by something on screen. Music and a person who has never seen the game are the two inputs only a human supplies.

./art godot-trailer --check /path/to/reel --game /path/to/game-package   # read-only gate
./art godot-trailer --beat-grid music/track.wav --out music/beats.json   # tempo, beats, downbeats
./art godot-trailer --assemble /path/to/reel                              # trims, beat sheet, cards, voice, mix
./art godot-trailer --vo /path/to/reel                                    # just the Liam voice lines

The end card is the reusable GameTrailerCard scene (title, platforms, availability, one directive). The gate checks structure, honesty attestations and media evidence; it cannot judge legibility, music fit or whether a stranger understands the game.

Godot development films

Ask your agent: godot-gamedev walker /path/to/walker-jumpman. This is the component-by-component companion to the gameplay walkthrough: code, saved and runtime scenes, resources, assets, procedural art, tests, and export status. The walker modifier adds the Claude/GDD opening, built-result summary, verdict, Your Turn, and regular stock-only outro. Without it, open directly on the game.

./art godot-gamedev --help shows the workflow. The read-only source gate is:

./art godot-gamedev --check /path/to/reel --game /path/to/project-containing-project.godot

The reusable GodotDevWorkbench scene has code, tree, asset, and trace views, including native portrait layout. Its editor chrome is explicitly reconstructed; source excerpts, runtime observations and art previews must come from the actual game. It does not modify game code, pretend to export a game, or publish a film.

Blender films from rendered images

Two companion skills work from a model’s rendered images, public GitHub gallery or screenshots taken from its video. Neither requires the original model, private drawings or original build scripts.

• blender-walkthrough /path/to/gallery/ makes a narrated tour of the final model: forward quarter, side, rear, other available views, details and documented stats.
• blender-build /path/to/gallery/ teaches how a learner could build a similar model from those images, explaining Blender concepts and providing incremental prompts for a coding agent. A teaching reconstruction is labeled as such; it is not presented as the original build history.

Both use Liam and the existing Brutalist film pipeline, output to the subject’s own youtube/ folder, and do not upload. ./art points an agent to the workflow; it is not an autonomous film-generation command.

./art blender-walkthrough --help
./art blender-build --help

The separate building-walkthrough /path/to/model.blend workflow still renders a measured camera route from an actual model. For an explicit original-build record, use blender-build /path/to/model-folder record or build-breakdown and read the historical workflow. Its existing utilities are unchanged:

./art building-walkthrough --check /path/to/reel/walkthrough.json
./art building-walkthrough --render rigged.blend route.json --out renders
./art blender-build --check /path/to/build-record/record.json
./art blender-build --draft | --guide | --tape

Those checks validate historical records or model camera routes, not an image-based lesson. The latter is reviewed for source evidence, usable prompts, visible learning checkpoints and honest demonstration status.