Use list_generators to list available generators when available, otherwise mix help. If you have to run generator tasks, pass --yes. Always prefer to use generators as a basis for code generation, and then modify afterwards.
Use tidewave MCP tools when available, as they let you interrogate the running application in various useful ways.
When you're done executing code, try to compile the code, and check the logs or run any applicable tests to see what effect your changes have had.
Use the project_eval tool to execute code in the running instance of the application. Eval h Module.fun to get documentation for a module or function.
Always use Ash concepts, almost never ecto concepts directly. Think hard about the "Ash way" to do things. If you don't know, often look for information in the rules & docs of Ash & associated packages.
Start with generators wherever possible. They provide a starting point for your code and can be modified if needed.
Always use package_docs_search to find relevant documentation before beginning work.
Never attempt to start or stop a phoenix application. Your tidewave tools work by being connected to the running application, and starting or stopping it can cause issues.