Individual skill
database-architect
Reviews database schemas, relationships, indexes, constraints, and data modeling decisions. Use when designing a new schema or reviewing an existing one for correctness and scalability.
skills/development/database-architect/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,407 bytesSKILL.mdcore · 2,616 bytesexamples/example.mddoc · 1,693 bytes
Read excerpt
## Purpose
Review or design database schemas for correctness (data integrity is actually enforced, not just assumed), scalability (queries stay fast as data grows), and sound relational/data modeling.
## When to Use
- Designing a new schema or table structure.
- Reviewing an existing schema before it grows harder to change.
- Diagnosing why queries are slow, and the cause looks like a modeling/indexing issue.
## What to Analyze / Do
1. **Normalization vs. denormalization** — is data duplicated in a way that risks inconsistency, or normalized past the point of being queryable without excessive joins? Neither extreme is automatically correct — judge against actual access patterns.
2. **Relationships & foreign keys** — are relationships modeled correctly (1:1, 1:many, many:many via join table), and are foreign key constraints actually declared, not just implied by naming?