# VEO Knowledge Pack — README
## Purpose
This folder contains the static knowledge files used by the Veo 3.1 meta-prompt and prompt
generation script. These files are read-only canonical resources: meta rules, templates, style
anchors, negative prompts, camera move glossary, character phrasing glossary, example
prompts, and an automated test-suite.
## Files (brief)
- `00_meta_prompt.txt` — canonical system instruction for the meta-prompt (load first).
- `01_prompt_template.txt` — the exact scaffold used to assemble final single-paragraph
prompts.
- `02_style_anchors.json` — approved style anchors, palettes, and substitution rules.
- `03_negative_prompts.txt` — concise negative prompts for technical artifact reduction.
- `04_camera_moves.csv` — camera move glossary with suggested lenses and usage notes.
- `08_test_suite.csv` — tests used for automated verification after script updates.
- `CHANGELOG.md` — version history and update notes.
## Usage & load order
1. Always read `00_meta_prompt.txt` first to set generation enforcement rules.
2. Load `01_prompt_template.txt` to know the exact output scaffold to fill.
3. Consult `02_style_anchors.json` and `05_character_gloss.csv` when mapping user words to
canonical phrases.
4. Apply `03_negative_prompts.txt` into the API `negativePrompt` if available, and include the
short inline Exclude from the template.
5. Use `04_camera_moves.csv` to validate requested camera language and ensure plausibility.
6. Run outputs through the tests in `08_test_suite.csv` when pushing updates.
## Maintenance
- Files are static and should only be updated via controlled commits.
- Any change to `00_meta_prompt.txt`, `01_prompt_template.txt`, or `02_style_anchors.json`
must also update `CHANGELOG.md` and re-run the test-suite.
## Notes
- Keep files small and focused; these are consulted at runtime and should not be overly large.
