# Hooks

Strong hooks usually name a problem, belief, result, or surprising observation. Examples: "I wish I knew this before buying another running supplement", "Stop doing this if your app onboarding leaks users", or "I tested three meal planning apps so you do not have to."

Create multiple `@Hook` ingredients for testing. Keep the rest of the ad structure stable so you can compare which opening changes the ad most.

Avoid generic hooks like "This product changed my life" unless the following scene immediately proves the claim. Specificity beats hype.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.avastudio.com/prompting/hooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.