Content Studio¶
A creative production system you use through Claude Code. Open this repository in your session, describe the work, and keep briefs, prompts, takes, decisions and handoffs in an external workspace. Studio and Review are optional interfaces over the same files and shared operations.
This release is for internal team adoption. It is an intact source checkout, not a standalone Python package. Public packaging and the future app redesign are separate work.
Start here¶
Follow Setup, then the internal first-session guide. For directing in plain language, read Directing from the chair.
You need Git, Python 3.13+ and Claude Code. Setup, planning and supplied-media decisions require no provider credentials, Node build, Pillow, app server or GPU. Software video export additionally needs ffmpeg and ffprobe on PATH. Optional dependencies and the verified platform are listed in Installation.
What you can do in a session¶
Capture a brief; create a production and shots; preserve prompt versions and preflight results; record questions and held cues; import and bind supplied media; record take verdicts, notes and live selection; edit a cut; explicitly export it; and resume from durable files in another session. Review questions, proposals and comments also have session commands.
You can think out loud about campaign content, a visual mood, a world or a story. Planning does not authorize generation. The shared workflow retains its cost, cue, identity, prompt, phase, finishing and publish requirements; opening or closing an app changes none of them. An approved take, a selected live take, an encoded cut and a published artifact are distinct states.
| Start with | Reference |
|---|---|
| Workspace choice and read-only diagnostics | Setup commands |
| Briefs, scenes, shots and gates | Administration |
| Immutable prompt versions | Prompts |
| Questions and held cues | Cues and asks |
| Supplied media and provenance | Media |
| Verdicts, notes and live selection | Decisions |
| Cut editing and resumable software exports | Cuts |
Where things live¶
The repository contains shared instructions, skills, code and repository-owned shared context. Your chosen workspace contains production documents and media together, along with receipts and recovery journals. Resolve it with python -m studio.paths root; a teammate does not need the original machine's drive letter.
The private Intuition/ vault is local-only and gitignored. A clone receives repository-owned context/, not that vault or anyone's private session memory. The context provisioning guide explains maintainer approval, freshness and identity dependencies. Private vaults cannot override the shared pack sources.
Shared doctrine and methods belong in the repository; personal notes belong to their owner. Shared knowledge and personal vaults documents the boundary, a workspace capture path for new teammates, and the repository-owned source/update contract.
CLAUDE.md and its area files route the shared instructions. Other clients (Codex, Hermes) are set up from docs/clients/; AGENTS.md adapts them to those same sources.
Optional apps and verification¶
The Studio and Review apps were deleted in packs phase 4 (restore point: git tag parked-apps-2026-10-16). Team review runs on Review Room (0xIntuition/review-room) and FreeFrame (bin/freeframe.py); the working path is the session commands (bin/studio_decisions.py). None of them is an onboarding prerequisite or an authority for creative approval.
Run the no-provider rehearsal to exercise the supported workflow in an isolated workspace. It retains example decisions and a handoff; an optional CPU-only export creates a one-second fixture cut. Human adoption and fresh-client resumption are tracked in the internal pilot. Automated success does not certify either client's runtime interception or the usability of the apps.
Originally built from the reusable higgsfield-studio-starter template.
Reporting a suspected violation¶
If you believe something generated, published or distributed with this studio violates a model licence or an acceptable-use policy - an undisclosed machine-generated publish, an unauthorized likeness, or any other misuse - report it to the studio maintainer (the contact is in the active pack's README). Reports are acted on promptly.
This is a standing, reasonably accessible reporting mechanism, and it exists because it is a licence condition rather than a courtesy: the MiniMax H3 authorization this studio's local video lane renders under is conditioned on our continued compliance with the commitments in our request, and commitment (d) is exactly this (docs/doctrine/minimax_h3.md). Lapse the condition and the authorization lapses with it.
License¶
Free to use for your own projects. A credit back is appreciated if you share it.