code-design-schema

Design database schemas, ORM models, and migrations for SQL and NoSQL stores.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sirn/dotfiles --skill code-design-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-design-schema
Source: https://github.com/sirn/dotfiles/tree/main/var/agents/skills/code-design-schema
Command: npx skills add https://github.com/sirn/dotfiles --skill code-design-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design data models, database schemas, and ORM definitions to align data structures with business rules and scalability goals.

Core Features & Use Cases

  • Generate schemas and ORM models for relational and document stores.
  • Propose migration plans and normalization strategies for evolving schemas.
  • Use Case: When starting a new project, define entities, relationships, and constraints to ensure consistent data access.

Quick Start

Provide a project brief and ask it to design the initial database schema with entities, relationships, and a migration plan.

Frequently Asked Questions about code-design-schema

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

FAQPage Schema
How do I design a database schema for a new data-driven application?

To design a database schema, define entities, relationships, and constraints to align data structures with business rules. Provide a project brief to generate schema definitions, ORM models, and a migration plan with clear rationale for evolving data requirements.

What is the best way to generate ORM models for both SQL and NoSQL stores?

Generate ORM models by defining entities and relationships across SQL and NoSQL stores. Propose normalization strategies and schema definitions tailored to your specific data structures to satisfy application requirements and ensure consistent data access.

Can I use this to propose migration plans for evolving database schemas?

Yes, you can propose migration plans for evolving database schemas. It generates migration strategies and normalization plans that handle schema changes over time, ensuring data structures continuously align with business rules and scalability goals.

When do I need a normalization strategy for my database schema?

You need a normalization strategy when defining entities and relationships to reduce redundancy and ensure consistent data access. It is applied during data modeling to align data structures with business rules and scalability goals in data-driven applications.

Does this approach work with both relational and document stores?

Yes, this approach works with both relational and document stores. It generates schemas and ORM models tailored to SQL and NoSQL data stores, proposing normalization strategies and migration plans that fit your specific data-driven application requirements.

Why should I define relationships and constraints when starting a new project?

Define relationships and constraints when starting a new project to ensure consistent data access and align data structures with business rules. This data modeling step prevents anomalies and establishes a robust foundation for generating ORM definitions and future migrations.