Speckit.database
bro-skills - Spec-Driven Development CLI
npx -y skills add wedabro/bro-skills --skill speckit.databaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Database Architect - Design schemas, indexes, migrations, query optimization, and data integrity controls.
SKILL.md
1.8 KB, as published. Nobody here has run it
π― Mission
Design and optimize the data layer: reasonable standardized schema, effective indexing, safe migration, fast query, data integrity.
π₯ Input
.agent/knowledge_base/data_schema.md.agent/specs/[feature]/spec.md+plan.md(data model).agent/memory/constitution.md
π Protocol
1. Schema Design
- Normalize (3NF) default; Denormalize intentionally when performance is needed (specify the reason).
- Clear primary/foreign keys, constraints (NOT NULL, UNIQUE, CHECK) in the DB.
- Naming convention is consistent; update
data_schema.md.
2. Indexing & Performance
- Index according to actual query pattern (WHERE/JOIN/ORDER BY).
- Avoid over-indexing (slow writing). Composite index correct column order.
- Detect & process N+1, full table scan.
3. Migration (Safe)
- Migration versioned, reversible (up/down).
- Zero-downtime pattern: expand β migrate β contract.
- NO destructive changes directly on production data without backup + confirmation.
4. Integrity & Transaction
- Transaction isolation level is appropriate; avoid deadlock.
- Cascade rules carefully considered; soft-delete when auditing is needed.
5. Security
- Least-privilege DB user; DO NOT use root/admin for the app.
- Encryption at-rest for sensitive data; mask PII.
π€ Output
- Schema DDL + migration files.
- Update
knowledge_base/data_schema.md(ERD, index list).
π« Guard Rails
- DO NOT run destructive migration on prod without backup + confirmation.
- NO hard-code credential β ENV (
DB_*). - DO NOT drop index on FK/hot query columns.
- DO NOT save plaintext passwords (must be hashed).
- Use the language configured by the project or requested by the user.