database-architect

Design database architectures by selecting storage technologies and modeling schemas.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/gajjalaashok75-UI/GakrCLI --skill database-architect-gajjalaashok75-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/gajjalaashok75-UI/GakrCLI/tree/main/assets/skills/database-atlas/database-architect
Command: npx skills add https://github.com/gajjalaashok75-UI/GakrCLI --skill database-architect-gajjalaashok75-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps you design a database foundation before implementation so your application starts with the right data model, storage choice, and scaling strategy instead of costly redesigns later.

Core Features & Use Cases

  • Technology Selection: Compare relational, NoSQL, time-series, search, and multi-model options based on workload, consistency, and operational trade-offs.
  • Schema and Index Design: Model entities, relationships, constraints, partitions, and indexes for performance and maintainability.
  • Scale and Migration Planning: Plan replication, sharding, caching, zero-downtime migrations, backups, and rollback strategies.
  • Use Case: A team building a multi-tenant SaaS platform can use this Skill to choose PostgreSQL, design tenant-aware schemas, and plan safe growth from startup scale to enterprise traffic.

Quick Start

Ask for a database architecture recommendation for your product, including schema design, indexing, scaling, and migration considerations.

Frequently Asked Questions about database-architect

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

FAQPage Schema
How do I design a scalable database architecture for a new application?

To design a scalable database architecture, model schemas, select appropriate storage technologies, and plan scalable data layers including partitioning and replication before implementation begins.

How do I choose between relational and NoSQL databases for my workload?

Choosing between relational and NoSQL databases involves comparing storage options based on your specific workload, consistency requirements, and operational trade-offs to ensure optimal data architecture.

What is the best way to plan a zero-downtime database migration?

Planning a zero-downtime database migration requires strategizing replication, backups, rollback procedures, and operational safety to transition workloads without interrupting application availability.

How do I model schemas and indexes for a multi-tenant SaaS platform?

Modeling schemas and indexes for multi-tenant SaaS platforms requires designing tenant-aware entities, relationships, constraints, and index strategies that maintain performance and maintainability as traffic grows.

When should I use database sharding and caching in my data architecture?

You should use database sharding and caching when planning scalable data layers for evolving applications that require high throughput, partitioning, and operational safety during enterprise traffic growth.