> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.

# Snippets: Save your best prompts and reuse them in seconds

> Save repeatable requests for hooks, scripts, and ad analysis, then insert them into Chat without rewriting your instructions.

Save a prompt as a **Snippet** when you want to repeat the same workflow with
another product, audience, or ad. Insert it into Chat with `/`, update the
details for the current job, and send it when the request is ready.

## Watch the walkthrough

<video controls playsInline preload="metadata" className="w-full h-auto rounded-xl" poster="/images/tutorials/qa/snippets-poster.jpg" alt="Snippets: Save your best prompts and reuse them in seconds" aria-label="Snippets: Save your best prompts and reuse them in seconds">
  <source src="https://stefanbrain.com/api/video/adaptive/tutorials/reuse-prompts-with-snippets/full-frame-2026-10-09.mp4" type="video/mp4" />

  <a href="https://stefanbrain.com/api/video/adaptive/tutorials/reuse-prompts-with-snippets/full-frame-2026-10-09.mp4">Watch the walkthrough</a>
</video>

[Watch on Loom](https://www.loom.com/share/42a5f52bac6c444896a95070f4dce884).
Jump to **0:45** for inserting a Snippet or **0:56** for the spoken-hook example.

## Practical use cases

<CardGroup cols={2}>
  <Card title="Start your next hook batch faster" icon="lightbulb">
    Save the instructions that give you useful spoken hooks, then change the
    product and audience instead of rebuilding the request for each campaign.
  </Card>

  <Card title="Compare ads using the same questions" icon="scan-search">
    Reuse an analysis prompt across your ads and competitor examples so your
    notes consistently cover the hook, promise, proof, and next test.
  </Card>

  <Card title="Repeat a script or native-ad workflow" icon="file-text">
    Keep your preferred structure and output format in one prompt so the
    next draft is easier to compare, refine, and hand to an editor.
  </Card>
</CardGroup>

## Save and use a Snippet

You need an active StefanBrain trial or plan to create Snippets. If your
library is read-only, check your account access or contact
[support@stefanbrain.com](mailto:support@stefanbrain.com).

<Steps>
  <Step title="Open Snippets">
    Open **Snippets** from the sidebar and select **New Snippet**.
  </Step>

  <Step title="Give the workflow a recognizable name">
    Use a name you will remember when searching, such as **Spoken hooks** or
    **Native ad analysis**. Add the prompt you want to reuse, then select **Save**.
  </Step>

  <Step title="Insert it into Chat">
    Open **Chat**, type `/`, and find the Snippet by name. Select it to add
    the saved instructions to your request.
  </Step>

  <Step title="Add this job's context">
    Select the relevant Product, attach the ad or file when needed, and
    supply the audience or angle for this request. Check the inserted prompt
    for details left over from a previous client before sending.
  </Step>

  <Step title="Review the output and improve the reusable prompt">
    Choose the strongest results and identify what needs changing. If the
    same correction helps every run, update the saved Snippet for next time.
  </Step>
</Steps>

## Start with a spoken-hook Snippet

This pattern gives you a varied batch to shortlist before writing a full
script. Replace the bracketed details when you use it.

```text theme={"system"}
Write 10 spoken opening hooks for the selected Product, aimed at [audience].
Focus on [angle or customer problem].

Make the hooks sound conversational and give each one a genuinely different
opening. Keep them easy to say aloud. Shortlist the three strongest options
and explain which audience concern each one addresses.
```

Keep the reusable instructions stable. Supply changing details—such as the
current offer, audience, source ad, or test angle—in the Chat where you use it.

## More Snippets worth saving

### Ad breakdown → new concepts

Save this to turn a source ad into distinct directions for your own product,
instead of copying a competitor's claims or changing only a few words.

```text theme={"system"}
Break down the attached ad's opening, promise, proof, and call to action.
Explain how the parts work together. Then give me 10 distinct concepts for
the selected Product that use the useful structure without copying its
wording or transferring claims our product cannot support. Shortlist three
and explain the customer motivation each one speaks to.
```

### Chosen hook → editor-ready brief

Use this after you have chosen a hook to reduce the back-and-forth between
copywriting and production.

```text theme={"system"}
Turn the chosen hook into an editor brief for [audience] and [placement].
Include the spoken script, hook-to-body transition, suggested visuals,
product shots, and call to action. Keep the selected Product and offer intact.
List the assets the editor needs and flag any missing product detail as a
question rather than inventing it.
```

### Approved brief → 20 genuinely different angles

Use this when you need a wider test plan, not 20 versions of the same headline.

```text theme={"system"}
Using the approved brief in this Chat, propose 20 distinct ad angles for
the selected Product. Vary the customer problem, desired outcome, objection,
and situation. Group overlapping ideas, then shortlist five directions.
For each shortlisted angle, give me an opening hook and the customer insight
that makes it worth testing.
```

Save separate Snippets for separate jobs. A hook generator, an ad breakdown,
and an editor brief are easier to reuse than one prompt that tries to do everything.

## Avoid carrying the wrong context forward

A Snippet saves instructions, not a reason to skip checking the brief. Before
sending, confirm the product, audience, attachments, and requested quantity.

If the output feels repetitive, ask for different approaches rather than
minor rewrites. For example:

```text theme={"system"}
Keep the same Product and audience. Give me 10 new hooks built around
different objections and desired outcomes, not synonyms of the last batch.
```

If you cannot find a Snippet in Chat, confirm it saved in **Snippets** and
search for its name after typing `/`.

## Next steps

* [Give Chat the right context](/knowledge-base/chat/give-chat-the-right-context)
* [Develop original hooks and ad copy](/knowledge-base/chat/develop-original-hooks-and-ad-copy)
* [Turn competitor ads into native ads for your product](/knowledge-base/chat/write-a-batch-of-native-ads)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.