mcpbeat

Database Postgresql

hoangnguyen0403/database-postgresql

Apply PostgreSQL standards for migrations, indexing, transactions, and ORM boundaries. Use when editing entities, Prisma schema, migrations, RLS, or query-performance work for PostgreSQL.

4k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill database-postgresql

What comes with it

12 528 bytes besides the instruction
evals/evals.json
references/anti-patterns.md
references/best-practices.md
references/checklist.md
references/implementation.md
references/sql-gotchas.md

The instruction itself

6 sections, as written by the author

PostgreSQL Database Standards

Priority: P0 (CRITICAL)

Rules

  • Keep PostgreSQL choices driven by real read/write paths.
  • Use explicit migrations; never rely on synchronize: true in 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: true destructive.
  • No blind index sprawl: each index needs a query owner.

References

  • Framework Map
  • Implementation Examples
  • SQL Gotchas (UPDATE FROM)

How to use it

Copy the folder

Take hoangnguyen0403/database-postgresql from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.