database-architect

Designs database schemas, selects storage technologies, and plans migrations for scalable data architectures.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill database-architect-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/Tgoldi/claude-skills/tree/main/database-architect
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill database-architect-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the wrong database technology or designing a poor schema early leads to costly rework, performance bottlenecks, and painful migrations. This Skill provides expert-level data layer architecture guidance, from technology selection through schema design, indexing, caching, and zero-downtime migration planning. ## Core Features & Use Cases - Technology Selection: Evaluates relational, NoSQL, time-series, graph, and NewSQL databases with clear trade-off analysis based on your access patterns and scale targets. - Schema & Index Design: Produces conceptual, logical, and physical data models with normalization strategies, index plans, and multi-tenancy patterns. - Migration & Scaling Planning: Designs zero-downtime migration strategies, sharding plans, replication topologies, and caching architectures. - Use Case: Ask it to design a multi-tenant SaaS e-commerce schema, and it will recommend a database engine, produce table designs with indexes, plan a caching layer, and outline a phased migration with rollback procedures. ## Quick Start Ask the assistant to design a database schema and migration plan for your application, describing your data domain, access patterns, and expected scale.

Frequently Asked Questions about database-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between PostgreSQL and MongoDB for my application?

PostgreSQL fits relational data with complex joins, strong consistency, and transactional workloads, while MongoDB suits flexible document schemas and high-write workloads. The Skill evaluates your access patterns, consistency requirements, and scale targets to recommend the right engine with documented trade-offs.

How to design a database schema for a multi-tenant SaaS application?

Multi-tenant design involves choosing between shared schema, schema per tenant, or database per tenant based on isolation, compliance, and cost requirements. The Skill produces table designs, relationships, constraints, and index strategies tailored to your tenancy model.

What is the best strategy for zero-downtime database migration?

Zero-downtime migration uses online schema changes, rolling deployments, or blue-green database patterns with chunked data migration for large tables. The Skill plans phased migrations with validation, rollback procedures, and cutover criteria, recommending tools like Flyway, Liquibase, or Alembic.

When should I denormalize a database schema?

Denormalization is appropriate for read-heavy workloads where JOIN complexity hurts performance, using selective denormalization, materialized views, or pre-computed aggregates. The Skill analyzes your read/write patterns and consistency requirements to recommend the right balance.

Does this Skill modify my database or run migrations directly?

No, it recommends schemas, architectures, and migration plans but does not modify files or execute migrations unless explicitly requested. It emphasizes validating migration plans in staging with backups and rollback procedures before production changes.