database-architect

Plan scalable data-layer architectures with schema design and migration planning.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/sixscripts-ai/ghostssh --skill database-architect-sixscripts-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/sixscripts-ai/ghostssh/tree/main/skills/database-architect
Command: npx skills add https://github.com/sixscripts-ai/ghostssh --skill database-architect-sixscripts-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires .

What problem does it solve?

Plans scalable data-layer architectures for modern applications, ensuring maintainability and future growth.

Core Features & Use Cases

  • Technology selection guidance across relational, NoSQL, and time-series databases.
  • Conceptual, logical, and physical data modeling with normalization and denormalization strategies.
  • Migration planning and zero-downtime approaches, with risk assessment and rollback plans.
  • Scaling patterns for multi-region and polyglot persistence.

Quick Start

Describe a data-layer design for a greenfield app to illustrate architecture decisions and migration strategy.

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 data-layer architecture for a new application?

To design scalable data-layer architecture, plan technology selection, schema design, and indexing strategies. This approach delivers conceptual, logical, and physical models ensuring maintainability and future growth for modern applications.

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

Plan database migration by generating migration-safe guidance with risk assessment and rollback plans. This approach ensures zero-downtime transitions during refactors by addressing data normalization and denormalization strategies proactively.

When do I need polyglot persistence for multi-region scaling?

You need polyglot persistence for multi-region scaling when a single database limits performance. It combines relational, NoSQL, and time-series databases to optimize data-layer architecture across distributed geographical regions.

How does physical data modeling differ from logical data modeling?

Physical data modeling defines exact table structures and indexing strategies, whereas logical modeling focuses on normalization and entity relationships. Both layers are essential to deliver a complete, maintainable schema design.

Can I use this to guide NoSQL and time-series database selection?

Yes, you can guide NoSQL and time-series database selection. The architecture planning covers technology selection across relational, NoSQL, and time-series databases to match your specific scaling and data-layer requirements.