design-data-model

Design database schemas with entities, relationships, constraints, and migration strategies.

6|3|Updated Apr 12, 2026

Search Tags:#database #schema #migration #sql #orm #modeling

Ready to run

npx skills add https://github.com/carson-sweet/sweetclaude --skill design-data-model

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-data-model
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/design-data-model
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill design-data-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the ambiguity and structural errors often found in manual database design by enforcing a systematic, artifact-driven approach to schema creation.

Core Features & Use Cases

Entity-Relationship Mapping: Automatically identifies core entities and their relationships from project documentation.
Schema Generation: Produces production-ready SQL DDL or ORM-specific migration code (Drizzle, Prisma, Alembic).
Migration Strategy: Provides structured guidance on destructive changes, backfills, and rollback plans.
Use Case: When starting a new feature, use this to generate a consistent schema that aligns with your existing project architecture and privacy requirements.

Quick Start

Invoke the design-data-model skill to generate a schema for a new user authentication system based on the existing project requirements.

Frequently Asked Questions about design-data-model

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

FAQPage Schema

How do I design a database schema for a new software feature?▼

Designing a database schema involves mapping entities and relationships from project documentation, then generating production-ready SQL DDL or ORM migration code to enforce constraints, optimize indexes, and plan safe database evolution.

Can I generate ORM migration code for frameworks like Drizzle or Prisma?▼

Yes, schema generation produces ORM-specific migration code for frameworks including Drizzle, Prisma, and Alembic, ensuring the database schema integrates with your existing ORM and project architecture.

What is the best way to plan database migrations for destructive schema changes?▼

The best way to handle destructive database migrations is to apply a structured migration strategy that includes backfill plans, rollback procedures, and safe evolution guidelines to prevent data loss during schema updates.

Does this database modeling approach work with existing project architectures?▼

Yes, the database modeling process takes your existing project documentation and requirements to generate a consistent schema that aligns with your current architecture, constraints, and privacy requirements.

How do you map entity relationships from technical requirements into a SQL schema?▼

Entity-relationship mapping automatically identifies core entities and their relationships from project documentation, translating them into a structured SQL schema with appropriate constraints and index optimization.

When should I use a structured data modeling approach instead of manual schema design?▼

You should use structured data modeling over manual schema design when you need to eliminate structural errors and ambiguity, requiring artifact-driven schema creation for complex software development lifecycles.