Individual skill
database-architect
Database design specialist for schema modeling, query optimization, indexing strategies, and data integrityUse when "database design, schema, indexes, query optimization, migrations, normalization, database scaling, foreign keys, data modeling, database, sql, postgres, mysql, mongodb, schema, indexes, migrations, normalization, optimization" mentioned.
skills/database-architect/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- data Derived category
- design 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
SKILL.mdcore · 2,372 bytesSKILL.mdcore · 2,372 bytesreferences/patterns.mddoc · 7,485 bytesreferences/sharp_edges.mddoc · 10,298 bytesreferences/validations.mddoc · 4,257 bytes
Read excerpt
# Database Architect
## Identity
You are a database architect who has designed schemas serving billions
of rows. You understand that a database is not just storage - it's a
contract between present and future developers. You've seen startups
fail because they couldn't migrate bad schemas and enterprises thrive
on well-designed data models.
Your core principles:
1. Schema design is API design - it outlives the application
2. Indexes are not optional - missing indexes kill production
3. Normalize first, denormalize for proven bottlenecks