database

Design database schemas and migration plans with rollback guidance.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/hdtinh57/codex-orchestrated-project-template --skill database-hdtinh57
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/hdtinh57/codex-orchestrated-project-template/tree/main/.codex/skills/database
Command: npx skills add https://github.com/hdtinh57/codex-orchestrated-project-template --skill database-hdtinh57

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable relational data models and migration plans to ensure data integrity, performance, and maintainability.

Core Features & Use Cases

  • Schema design guidance including normalization decisions, data types, and relationships.
  • Migration planning and rollback strategies to minimize downtime and risk.
  • Indexing and query optimization recommendations for performance tuning.
  • Use cases include onboarding new features, refactoring existing schemas, or evaluating database technology choices.

Quick Start

Propose a normalized schema and index strategy for the new feature, including forward and rollback migrations.

Frequently Asked Questions about database

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

FAQPage Schema
How do I design a normalized database schema for a new application feature?

Database schema design for new features involves proposing a normalized structure, selecting appropriate data types, defining relationships, and implementing an index strategy to ensure data integrity and performance.

What is the best way to plan database migrations and rollbacks to minimize downtime?

Database migration planning minimizes downtime and risk by providing explicit forward and rollback DDL guidance, validation checks, and risk assessments before deployment across new features and legacy systems.

How do I optimize queries and implement indexing for performance tuning?

Query optimization and indexing recommendations analyze your schema to tune performance, ensuring efficient data retrieval and scalable application behavior under load.

Can I use this to refactor existing schemas in legacy systems?

Refactoring existing schemas in legacy systems is supported by evaluating normalization decisions, providing migration rollback strategies, and assessing deployment risks before applying structural changes.

What are the limitations or risks when applying schema migrations to legacy systems?

Schema migration risks in legacy systems include downtime and data integrity loss, mitigated by applying validation checks, risk assessments, and explicit rollback DDL guidance before deployment.