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 — are required; script prompt and the real-media policy are 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 — the required trio. Each must be non-empty; they are the core instructions the pipeline reads for visuals, writing, and shot planning.
• ·script_prompt — optional, seeded with a default. Shapes how scripts are generated for this style.
• ·real_media — optional, empty by default. Leaving it empty keeps real-media sourcing off; writing a policy into it switches on real photo and b-roll sourcing for storyboards.

Built-in fields can be edited freely but never deleted. The required trio must stay non-empty; real_media may be left empty, which just means the switch is 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.