From db-postgres
Use when scaffolding or reviewing PostgreSQL project layout — migration folder conventions, schema separation, extension management, seed data organization, and pgTAP test layout
How this skill is triggered — by the user, by Claude, or both
Slash command
/db-postgres:postgres-project-structureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
database/
├── migrations/
│ ├── V001__create_extensions.sql
│ ├── V002__create_orders_table.sql
│ ├── V003__create_auth_schema.sql
│ └── V004__add_rls_policies.sql
├── schemas/
│ ├── public/
│ │ ├── tables/
│ │ │ ├── orders.sql
│ │ │ ├── order_items.sql
│ │ │ └── customers.sql
│ │ ├── views/
│ │ │ └── active_customers.sql
│ │ ├── functions/
│ │ │ ├── get_order_by_id.sql
│ │ │ └── calculate_total.sql
│ │ ├── triggers/
│ │ │ └── trg_set_modified_at.sql
│ │ └── types/
│ │ └── order_status.sql
│ ├── auth/
│ │ ├── tables/
│ │ │ ├── users.sql
│ │ │ └── roles.sql
│ │ └── functions/
│ │ └── authenticate_user.sql
│ └── audit/
│ └── tables/
│ └── audit_log.sql
├── extensions/
│ └── required_extensions.sql
├── security/
│ ├── roles/
│ │ ├── app_read_role.sql
│ │ └── app_write_role.sql
│ └── rls/
│ └── tenant_policies.sql
├── seed/
│ ├── lookup/
│ │ ├── order_statuses.sql
│ │ └── countries.sql
│ └── dev/
│ └── sample_orders.sql
├── tests/
│ └── pgTAP/
│ ├── test_orders.sql
│ └── test_auth.sql
├── alembic/ # If using Alembic
│ ├── alembic.ini
│ ├── env.py
│ └── versions/
└── flyway.conf # If using Flyway
migrations/ for versioned change scripts (V001, V002, ...)extensions/ for PostgreSQL extension declarationssecurity/ for roles and RLS policiesseed/lookup/ for reference data (always applied)seed/dev/ for development-only sample datatests/pgTAP/ for in-database unit testspublic for core domain, auth for authentication, audit for loggingtypes/ subdirectory for custom ENUMs and composite typesnpx claudepluginhub gagandeepp/software-agent-teams --plugin db-postgresGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.