> For the complete documentation index, see [llms.txt](https://docs.avastudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avastudio.com/ingredients/naming-conventions.md).

# Naming conventions

Good ingredient names make projects easier to read, remix, and scale.

Use names that describe the role of the ingredient, not just its order. Prefer `@Body_ProductDemo` over `@Body_1`. Prefer `@Broll_AppWalkthrough` over `@Video`.

* Use `@Actor` for the main person.
* Use `@Product` for the product reference.
* Use `@Hook_[angle]` for testable hooks.
* Use `@Body_[scene_role]` for dialogue or narration by scene.
* Use `@CTA_[action]` for final action language.
* Use `@Broll_[subject]` for cutaway footage.

Keep text ingredient values concise. One spoken text ingredient should usually map to one scene, not an entire ad script.
