home / skills / shaul1991 / shaul-agents-plugin / dba-architect

dba-architect skill

/skills/dba-architect

This skill designs database schemas and models, creating ERDs, normalization plans, physical models, and migration strategies to support scalable data

npx playbooks add skill shaul1991/shaul-agents-plugin --skill dba-architect

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
458 B
---
name: dba-architect
description: DBA Architect Agent. 스키마 설계, 정규화, 데이터 모델링을 담당합니다.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
---

# DBA Architect Agent

## 역할
데이터베이스 스키마 설계 및 모델링을 담당합니다.

## 담당 업무
- ERD 설계
- 정규화
- 물리적 모델링
- 마이그레이션 계획

## 산출물 위치
- ERD: `docs/database/erd/`
- DDL: `database/migrations/`

Overview

This skill is the DBA Architect agent responsible for database schema design, normalization, and data modeling. It delivers ER diagrams, physical models, and migration-ready DDL tailored to application needs. Outputs are organized for easy handoff to engineering and deployment pipelines.

How this skill works

The agent analyzes requirements and existing data to produce conceptual and logical ERDs, applies normalization rules, and converts models into physical schemas. It generates migration plans and DDL files placed in the project migration folder for implementation. It can review schema changes for integrity, performance, and compatibility with deployment constraints.

When to use it

  • Starting a new application or feature that requires a persistent data model
  • Refactoring or normalizing an existing database to remove redundancy
  • Preparing schema migrations for production rollouts
  • Designing cross-service data contracts in a microservices environment
  • Reviewing schema changes for performance and integrity before deployment

Best practices

  • Begin with a clear set of domain entities and usage patterns before modeling
  • Normalize to the appropriate form, then denormalize selectively for performance
  • Keep ERDs and DDL in version control and tie migrations to tickets/releases
  • Document assumptions, foreign-key intentions, and indexing strategies
  • Validate schema changes with representative data and performance tests

Example use cases

  • Produce an ERD and normalized logical model from product and order requirements
  • Create a physical schema and DDL for a new billing service and place migrations in database/migrations/
  • Audit an existing schema for normalization violations and recommend fixes
  • Plan a zero-downtime migration strategy for adding a new required column
  • Design cross-database relationships and indexing strategy for reporting queries

FAQ

Where are generated artifacts stored?

ER diagrams are placed under docs/database/erd/ and DDL/migration files go to database/migrations/.

Does the agent handle deployment of migrations?

The agent produces migration plans and DDL; execution should be performed by your CI/CD pipeline or DBA with access to production systems.