PostgreSQL Database Standards
SkillDatabases & dataApply PostgreSQL standards for migrations, indexing, transactions, and ORM boundaries. Use when editing entities, Prisma schema, migrations, RLS, or query-performance work for PostgreSQL.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the PostgreSQL Database Standards skill
What this skill tells your AI
The instructions your AI receives, as published by hoangnguyen0403/agent-skills-standard in skills/database/database-postgresql/SKILL.md and read by ahel’s review.
Priority: P0 (CRITICAL)
Rules
- Keep PostgreSQL choices driven by real read/write paths.
- Use explicit migrations; never rely on
synchronize: truein production. - Treat RLS, constraints, and indexes as first-class schema behavior; use
queryRunner.query()when raw migration SQL is required. - Enable RLS explicitly in a migration (
ALTER TABLE <table> ENABLE ROW LEVEL SECURITY) and create tenant policies before application rollout. - Put multi-step consistency inside one transaction boundary.
Verify
- Destructive schema change uses expand -> backfill -> contract rollout.
- Query shape has matching indexes for filter, join, and sort paths.
- Pagination strategy is explicit.
- Transaction boundary matches one business action.
- RLS or tenant predicates are supported by indexes.
Anti-Patterns
- No N+1 queries: Use query builders or eager-load relations instead of lazy-loading in loops.
- No heavy RLS joins: Keep RLS predicates simple; move complex logic to query/view layer.
- No synchronize in production: Always run explicit migrations;
synchronize: truedestructive. - No blind index sprawl: each index needs a query owner.
References
Signals
- GitHub stars
- 565
- Forks
- 164
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
database-postgresql- Source
- github.com/hoangnguyen0403/agent-skills-standard