Prompt·Start here·PG00
Make this database easier to trust and operate
The broad starting point when the database feels hard to trust or costly, and you can't yet name one problem.
Prompt
I want this PostgreSQL database to become easier to maintain, faster where it matters, less expensive to operate, and more trustworthy. Study how the database actually works today, including its schema, important relationships, data sources, reads, writes, background jobs, migrations and consumers. Use the real database state, repository and operational evidence rather than relying on documentation alone. Find the few underlying problems responsible for the greatest amount of unnecessary complexity, repeated work, data-quality risk and operational expense. I care especially about correctness of the underlying data, efficient and reliable writes, duplicated logic, unnecessary database objects, historical accuracy, and changes that make future development easier for coding agents. Rank the opportunities by actual impact. Distinguish demonstrated problems from theoretical concerns, and don't recommend a redesign just because an approach is unconventional. Make recommendations that simplify the existing system rather than introduce more infrastructure or recurring processes. Reuse evidence already gathered, investigate only what's needed to support a decision, and group related findings around their shared cause. Use read-only investigation initially. Don't modify production data, schemas or infrastructure. Give me the strongest findings, what proves them, and the smallest changes that would produce meaningful improvements.
- What it returns
- A short ranked list of confirmed problems, each with the tables, writers and consumers involved, and the proof: query plans, samples, counts or a check against the source.
- Skip it when
- You already know the specific problem. Go straight to the narrower prompt for it.
- Avoid
- Turning one look into a standing review, a new process or automated governance.
- Changes
- Changes nothing
- Sessions
- Look first, then fix in a new session
- Tools
- Needs: the repository and read-only database access. Helps: query statistics (pg_stat_statements) and, on Supabase, the built-in Advisors.
- Works on
- Any PostgreSQL host: Supabase, Neon, RDS, Cloud SQL or self-hosted.
Related prompts
- Can we independently prove these numbers?PromptImportant figures may be wrong even though their lineage is documented.
- Map every place that writes to the databasePromptSeveral jobs, functions, APIs or agents change the same data, or nobody is sure who owns it.
- Which database objects no longer earn their keep?PromptThe list of views, functions and triggers has grown hard to reason about.
- Find the true sources of database wastePromptThe bill is high, CPU or disk usage is high, storage keeps growing, or you suspect bloat.
More in Start here.