What it does
The database-architect agent designs database schemas and writes or reviews migrations. It covers multi-tenant isolation with row-level security, indexes, constraints and choosing a database, and it defaults to PostgreSQL. The publisher says its migrations are meant to apply cleanly, keep data correct under concurrency and tenancy, and avoid locking production tables, and that they are tested against a real database before being returned.
It suits work such as designing tables for a new feature or app, reviewing a schema before launch, or changing an existing schema, including small or rushed changes. The publisher's examples include an online migration that adds a required column and renames one using lock timeouts and an expand/contract approach, and a review of a schema for tenant leaks, integrity gaps and missing indexes.
Running it means applying migrations to a real database for testing, with the publisher's examples using a scratch PostgreSQL instance. Query tuning is handed to the postgres-pro agent and Neon-specific work to the neon-database-architect agent.
Limitations and requirements
Testing is carried out against a real database. Query tuning and Neon-specific work are outside this agent's scope and are handed to other agents.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 12738
database-architect
MUST BE USED for any database schema work, including small changes and rushed requests: designing tables for a new feature or app, writing or reviewing migrations, multi-tenant isolation (row-level security), indexes and constraints, choosing a database, or reviewing a schema before launch. Produces migrations that apply cleanly, keep data correct under concurrency and tenancy, and do not lock production tables, and it tests them against a real database before handing them back. Defaults to PostgreSQL; hands query tuning to postgres-pro and Neon-specific work to neon-database-architect. <exam
As shown on www.aitmpl.com when we last read it