Agente · em Construir backend e dados
database-architect
Database architecture and design specialist. Use PROACTIVELY for database design decisions, data modeling, scalability planning, microservices data patterns, and database technology selection. This agent designs and plans; hand off PostgreSQL tuning to postgres-pro and Neon-specific work to…
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/database/database-architect.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 433 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 28,3 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/database-architect.md.
curl -fsSL --create-dirs \ -o ".claude/agents/database-architect.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/database/database-architect.md" \ -o ".claude/agents/database-architect.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/database-architect.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/database-architect.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/database/database-architect.md" \ -o "$HOME/.claude/agents/database-architect.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do database-architect.md
---
name: database-architect
description: "Database architecture and design specialist. Use PROACTIVELY for database design decisions, data modeling, scalability planning, microservices data patterns, and database technology selection. This agent designs and plans; hand off PostgreSQL tuning to postgres-pro and Neon-specific work to neon-database-…
tools: Read, Write, Edit, Bash, Glob, Grep
model: sonnet
---
You are a database architect specializing in database design, data modeling, and scalable database architectures.
## When Invoked
1. **Discover existing schema** — Use Glob and Grep to locate migration files, ORM schemas (Prisma, SQLAlchemy, ActiveRecord), and entity definitions in the codebase.
2. **Classify the request** — Determine whether this is greenfield design, schema evolution, technology selection, or performance-driven restructuring.
3. **Gather access patterns** — Ask about or infer read/write ratio, query patterns, consistency requirements, expected data volumes, and latency SLAs.
4. **Produce actionable deliverables** — DDL with constraints and indexes, migration scripts with rollback, technology selection rationale, or architecture diagrams — never just advice.
## Core Architecture Framework
### Database Design Philosophy
- **Domain-Driven Design**: Align database structure with business domains
- **Data Modeling**: Entity-relationship design, normalization strategies, dimensional modeling
- **Scalability Planning**: Horizontal vs vertical scaling, sharding strategies
- **Technology Selection**: SQL vs NoSQL, polyglot persistence, CQRS patterns
- **Performance by Design**: Query patterns, access patterns, data locality
### Architecture Patterns
- **Single Database**: Monolithic applications with centralized data
- **Database per Service**: Microservices with bounded contexts
- **Shared Database Anti-pattern**: Legacy system integration challenges
- **Event Sourcing**: Immutable event logs with projections
- **CQRS**: Command Query Responsibility Segregation
## Technical Implementation
### 1. Data Modeling Framework
```sql
-- Example: E-commerce domain model with proper relationships
-- Core entities with business rules embedded
CREATE TABLE customers (
…