database-architect

Design database schemas, generate migrations, and define indexing strategies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TudeOrangBiasa/zenithgravity-kit --skill database-architect-tudeorangbiasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/TudeOrangBiasa/zenithgravity-kit/tree/main/.agent/skills/database-architect
Command: npx skills add https://github.com/TudeOrangBiasa/zenithgravity-kit --skill database-architect-tudeorangbiasa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of database design, ensuring efficient data storage, retrieval, and integrity, regardless of the underlying ORM.

Core Features & Use Cases

  • Schema Design: Enforces normalization rules (3NF default), appropriate data types, and consistent ID strategies.
  • Indexing: Automates the creation of necessary indexes for optimal query performance.
  • Optimization: Prevents common performance pitfalls like N+1 query problems and inefficient data fetching.
  • Use Case: When building a new feature that requires user profiles and associated posts, use this Skill to design a normalized schema with appropriate foreign key indexes and eager loading strategies to prevent performance issues.

Quick Start

Use the database architect skill to design a schema for a blog with posts and comments, ensuring foreign keys are indexed.

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 database schema that prevents N+1 query problems?

Schema design prevents N+1 query problems by defining appropriate foreign key indexes and guiding eager loading strategies. This optimizes data fetching to retrieve associated records efficiently without excessive separate queries.

What's the best way to decide between relational SQL and NoSQL database boundaries?

Deciding between SQL and NoSQL boundaries requires analyzing data structure and query patterns against normalization rules. The architecture process guides this decision by evaluating 3NF compliance, data types, and specific retrieval needs.

How do I generate database migrations with consistent ID strategies?

Generating database migrations with consistent ID strategies requires enforcing UUIDv4 or ULID formats during schema design. This process integrates ID strategies alongside audit columns to maintain data integrity and traceability across migrations.

When do I need to add indexing strategies for SQL query optimization?

Indexing strategies are needed when query performance analysis reveals slow data retrieval or inefficient fetching. The design process automates index creation based on foreign keys and query patterns to ensure optimal database performance.

Does schema design enforce specific normalization rules and data types?

Schema design enforces 3NF normalization rules, appropriate data types, and consistent ID strategies by default. These rules ensure efficient data storage, retrieval, and integrity regardless of the underlying ORM.