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

# Best Practices

> Tips for getting the most out of Astro

## Mentioning Executions

You can reference specific executions in your conversations with Astro using the `@` symbol. A quick menu will pop up showing your recent executions, making it easy to pick the right one. This is useful when you want Astro to analyze what happened during a particular run.

<Card title="Mentioning Executions" icon="at" img="/images/astro-mention-executions.png" horizontal>
  When you type `@` in the chat input, a menu appears showing your recent executions. Simply select the one you want Astro to analyze.
</Card>

The more context you give Astro, the better it can help you. When asking for improvements or building agents:

* **Describe your goal**: Explain what you're trying to achieve
* **Share examples**: If relevant, mention specific executions or scenarios
* **Be specific**: Ask targeted questions rather than very general ones

## Iterative Improvement

Astro works best when you iterate:

<Steps>
  <Step title="Ask for help">
    Start with a question or request
  </Step>

  <Step title="Review suggestions">
    Look at what Astro proposes
  </Step>

  <Step title="Provide feedback">
    Accept, reject, or ask for modifications
  </Step>

  <Step title="Refine">
    Continue the conversation to fine-tune the results
  </Step>
</Steps>

## Tips for Better Results

* **Be specific**: Instead of "make it better," ask "how can I make the form filling more reliable?"
* **Provide context**: Mention specific nodes, executions, or issues you're facing
* **Iterate**: Don't expect perfect results on the first try—refine through conversation
* **Review changes carefully**: Always review workflow changes before accepting them
* **Test after changes**: Run your agent after making changes to verify improvements

***

## Examples

<Tabs>
  <Tab title="Building an Agent from Scratch">
    <Callout icon="user" color="#EC4899" iconType="regular">
      I need to automate filling out a contact form on example.com. The form has name, email, and message fields.
    </Callout>

    <Callout icon="robot" color="#692FFF" iconType="regular">
      *Analyzes request and suggests workflow structure*
    </Callout>

    <Callout icon="user" color="#EC4899" iconType="regular">
      That looks good, but I also need to handle the captcha.
    </Callout>

    <Callout icon="robot" color="#692FFF" iconType="regular">
      *Suggests creating an agent profile with captcha solvers enabled*
    </Callout>
  </Tab>

  <Tab title="Improving Existing Prompts">
    <Callout icon="user" color="#EC4899" iconType="regular">
      Improve my prompts
    </Callout>

    <Callout icon="robot" color="#692FFF" iconType="regular">
      *Reviews all node prompts and suggests improvements*
    </Callout>

    <Callout icon="user" color="#EC4899" iconType="regular">
      I like the suggestions for the login node, but keep the original prompt for the data extraction node.
    </Callout>

    <Callout icon="robot" color="#692FFF" iconType="regular">
      *Updates only the login node prompt*
    </Callout>
  </Tab>

  <Tab title="Debugging an Execution">
    <Callout icon="user" color="#EC4899" iconType="regular">
      Why did this execution fail? `@execution-456`
    </Callout>

    <Callout icon="robot" color="#692FFF" iconType="regular">
      *Analyzes execution logs and identifies the issue*
    </Callout>

    <Callout icon="user" color="#EC4899" iconType="regular">
      How can I fix that?
    </Callout>

    <Callout icon="robot" color="#692FFF" iconType="regular">
      *Suggests specific changes to prevent the failure*
    </Callout>
  </Tab>
</Tabs>