Speckit.database

Skill wedabro/bro-skills/.agents/skills/speckit.database

bro-skills - Spec-Driven Development CLI

Install

npx -y skills add wedabro/bro-skills --skill speckit.database

Assembled 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, 403 tokens by cl100k_base, 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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most databases sql skills give in 403 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

Use parameterized queriesin 37 of 589, across 34 files
Use timestamptz for timestampsin 30 of 589, across 14 files
Index foreign keysin 29 of 589, across 18 files
Create indexes concurrentlyin 29 of 589, across 24 files
Use numeric type for moneyin 25 of 589, across 8 files
Use cursor pagination instead of offsetin 24 of 589, across 17 files
Select only required columnsin 24 of 589, across 20 files
Add indexes manually on foreign key columnsin 22 of 589, across 12 files
Normalize to third normal formin 19 of 589, across 10 files
Configure connection poolingin 19 of 589, across 17 files
Put equality columns before range columns in indexesin 18 of 589, across 10 files
Read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

define clear keys and constraints
hash stored passwords
update the schema documentation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.