Studio craft — a technique on a node, not a wall of text in the prompt

A good shot is a craft: where the light stands, how the camera moves, when the scene falls silent. Usually that knowledge lives in your head and gets rewritten into every prompt from scratch — and differently for each model. Forget one line and the shot falls apart.

In the studio, that craft is moved into a skills library. A skill is a named unit of expertise: a short instruction you write once and reuse across every project. Not a "magic prompt," but a locked-in technique that gets applied when it’s needed.

vinistudio.app

Three layers of craft

The techniques are sorted by role, so you don’t assemble a wall of text by hand — you grab the layer you need with a single chip:

1. Studio base — the craft minimum for every model (Kling, Seedance, Grok, Gemini Omni): the prompt describes only what changes; the main action goes in the first words; emotion is shown through the body; silence has to be demanded in words. It attaches to the Director and the Scriptwriter on its own.
2. Per model — the syntax of a specific model: with Kling v3, dialogue only via a tag with quotes; with Gemini Omni, a single prose paragraph of 20–50 words. You add it when the shot goes to that model.
3. Craft — shooting techniques: "cinematographer’s lighting" (a named source, the role of each fixture), "camera language" (one movement per clip), "on-screen silence," "no fluff" (strips the prompt of empty quality boosters).

A technique is a baseline, not a command

A skill doesn’t force the model to work blind. The model receives the technique as a craft baseline, decides whether it fits the specific scene, and applies it — or honestly reports that it didn’t. No silent failures: you place techniques instead of writing a wall of text, and you see what actually landed.

A technique is a baseline, not a command. The model is free to skip one that breaks the scene — and it’ll say so.— the skills principle