Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Every constraint lives in exactly one place. This page says which place, for every kind of requirement.
| You have… | It goes in… | Why |
|---|---|---|
| The AI’s role, expertise, and approach | The specialist prompt | The only free-form slot, and it comes first in the generation prompt. |
| Output field names and types | A JSON Schema rule | Injected as guidance and machine-enforced. |
| Length limits, required fields, enums, formats | A JSON Schema rule | Deterministic. Models cannot count characters. |
| Exact banned words and phrases | A forbidden-terms rule | Deterministic, with no misses. |
| Context-dependent judgment — tone, naturalness, a word used only as a buzzword | An AI evaluation rule | Needs understanding, not matching. |
| Brand voice, terminology, audience traits | A variant option’s fields | Reaches the generator and the checks, and can be scoped. |
| How the AI should use a dimension | That variant’s instruction | Per-dimension direction. The defaults usually suffice. |
| Reference data to look up at runtime | A capability | Live data beats pasted data. |
| Pictures the model must actually see | The images capability, plus $images on the document | A vision model reads the picture; a text model reads a URL and guesses. |
| Whether the generated text matches the pictures | An AI rule that opts into the images capability | Verification is a separate call, and can use a different model than generation. |
| Generation-only context — campaign notes, edge cases | Special instructions | Checks cannot see it, so only put things here that never need checking. |
| Which data the job runs over | The session’s input binding, not the configuration | One configuration, many feeds. |
Must it be enforced?
Must it vary by language, brand, or audience?
Is it just context for generation?
Was this page helpful?
