AthenodeAthenode

Back to Postgres

AGENTS.md

182 words1,091 of 50,000 characters

Instructions every agent in this setup follows. They're installed into your project as AGENTS.md.

Postgres

  • Through the dbhub MCP server run only reading statements (SELECT, EXPLAIN, catalog queries) unless the user asked for a specific write. Before any statement that changes data or schema, show it, name the database it will run on, and wait for a yes.
  • Never run EXPLAIN ANALYZE on a statement that writes, and ask before running it on a database that may be production: it executes the query.
  • Find out which database you are connected to before drawing conclusions: plans and row counts from a small development database do not predict production.
  • Look at the real schema (tables, indexes, constraints, row estimates) before writing or judging a query; do not assume it from the application's models.
  • Limit exploratory queries and select only the columns needed. Keep personal data out of the conversation: prefer counts and shapes to rows, and never copy row contents into code, commits or issues.
  • Schema changes go through the project's migration tool as migration files, never as statements run by hand.
  • Never print the connection string or its password.

Ready to ship better, together?

Spec it. Decompose it. Ship it. All with your AI agent.

Start for free

Join engineers building with Athenode today.