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

# Tips

> Get the most out of ami

## Start Fresh When Stuck

If a thread has too many failed attempts, the context gets noisy. A new thread with a clean prompt often works better.

## Be Specific About Testing

Tell ami exactly which test command to run:

| ❌ Avoid         | ✅ Preferred                                  |
| :-------------- | :------------------------------------------- |
| "Run the tests" | "Run `npm test -- --watch` and fix failures" |

## Include Lint Commands in AGENTS.md

ami runs lint commands automatically after making changes if it knows what commands to use.

## Use Plan Mode for Exploration

When you're unsure how to approach something, switch to Plan Mode first. Get a plan, review it, then switch to Agent Mode to execute.

## Attach Relevant Files Upfront

If you know which files matter, mention them in your first message. It saves ami from searching.

## Let ami See Your Errors

Paste error messages, stack traces, or screenshots directly. The more context, the better the fix.

## Support

* **Discord:** [ami.dev/discord](https://ami.dev/discord)
* **Documentation:** [ami.dev/docs](https://ami.dev/docs)