Styles & consistency

Edit style fields and add custom variables

A style is a set of editable text fields, not a black box. The built-in fields — art style, narrative style, director style, and text & overlay style — are required; the script prompt is optional; and you can add your own @variables and wire them into specific generation prompts. Whether the style came from analysis or presets, everything below applies the same way.

Built-in fields

• ·art_style, narrative_style, director_style, text_style — the four required fields, shown as Art style, Narrative style, Director style, and Text & overlay style. Each must be non-empty; they are the core instructions the pipeline reads for visuals, writing, shot planning, and on-screen text.
• ·script_prompt — optional, seeded with a default. Shapes how scripts are generated for this style.

Built-in fields can be edited freely but never deleted. The four required fields must stay non-empty.

Real photos and b-roll are switched on inside the director style: the @real-media tag in its text makes them available to the storyboard, and the text around the tag says when they appear and how much. Delete the tag, or its passage, to turn them off.

Custom variables

Add your own fields to a style and reference them as @key inside prompts. Each custom variable carries an applies_to list naming which generation-prompt sections read it, so a variable can feed just the script prompt, just the storyboard, or several places at once.

• ·Keys must start with a letter and use only letters, digits, and underscores.
• ·Keys can't shadow built-in setting names — the app rejects collisions.
• ·Custom fields can be removed anytime; only the built-in fields are permanent.

A living object

Style edits take effect on the next generation run that reads the field — the pipeline is iterative, so tightening a style field and re-running a station is the normal way to steer output. Re-analysis overwrites only the analyzed fields and leaves your custom variables in place.