Lemo-Opuscar

The styles, guides and tools live in the Lemo-Opuscar library (github.com/lemomo-ai/lemo-opuscar). This skill fetches it and hands you over to it.

Get the library. Run sh "<skill base directory>/scripts/setup.sh". It clones or updates the library (default ~/lemo-opuscar; a clone the user is standing in is used as it is) and prints LIB=<path> on its last line.
Install the core tools early. Start sh "<skill base directory>/scripts/setup.sh" deps right away, in the background if you can: it takes a few minutes the first time. Add deps voice or deps music later, only if the film needs them ($LIB/TECHNIQUE.md §1). Report missing system tools (Node, ffmpeg, Python) in your one round of questions; don't install system software yourself. Packages a style needs (its STYLE.md lists them) you install yourself, into the project folder.
Follow the library. Read $LIB/AGENTS.md and do what it says: finding the style, the one round of questions, the treatment, production and delivery.

What changes in skill mode:


Project folder	`<name>/` in the folder the user started from (lowercase letters, digits, hyphens; avoid `#` and `?` in the path). Wherever the guides say `films/<name>/`, read this folder
Running tools	from `$LIB`, with the project's absolute path: `cd "$LIB" && node core/render/still.mjs "<project>" 1.5 3`
Library files in pages	absolute URLs: `/core/lib.js`, `/node_modules/three/…` (the project is served at `/@film/`)
Library files in scripts and `build.sh`	`$LIB/…`, with `LIB=<path>` at the top of `build.sh`; never `../..`
Demo source	not downloaded. `sh "<skill base directory>/scripts/setup.sh" demo <slug>`, only after your `TREATMENT.md` is written, to read its techniques; it is not meant to be rendered

Deliver what $LIB/DIRECTOR.md §11 lists, in the project folder, and tell the user where it is.