schema-design

Design normalized relational database schemas up to 3NF with indexes and constraints.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill schema-design-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-design
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/datos/schema-design
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill schema-design-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating robust, well-documented, and performant relational database schemas that are maintainable and scalable.

Core Features & Use Cases

  • Database Schema Design: Guides users through designing normalized database schemas (up to 3NF).
  • Relationship Modeling: Helps define one-to-one, one-to-many, and many-to-many relationships with proper cardinality.
  • Index and Constraint Definition: Assists in creating appropriate indexes and integrity constraints (PRIMARY KEY, FOREIGN KEY, NOT NULL, UNIQUE, CHECK).
  • ORM Adaptation: Facilitates translation of the schema design to specific ORM syntaxes (Prisma, Drizzle, SQLAlchemy, etc.).
  • Documentation Generation: Ensures tables and columns are documented for clarity.
  • Use Case: A user needs to design a new database for an e-commerce platform, including tables for users, products, orders, and payments, ensuring data integrity and efficient querying.

Quick Start

Use the schema-design skill to create a normalized database schema for an online store, including tables for products, customers, and orders.

Frequently Asked Questions about schema-design

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

FAQPage Schema
How do I design a normalized database schema up to 3NF?

Designing a normalized database schema up to 3NF involves modeling domain entities, defining relationships with correct cardinality, and applying naming conventions. This ensures data integrity, performance, and maintainability for evolving business requirements.

How do I model one-to-many and many-to-many relationships with proper cardinality?

To model relationships with proper cardinality, define one-to-one, one-to-many, and many-to-many connections between domain entities. Applying correct integrity constraints like foreign keys ensures robust relationship mapping and data consistency.

What's the best way to translate a SQL schema design for ORMs like Prisma or SQLAlchemy?

Translating a SQL schema design for ORMs involves adapting the normalized schema to specific ORM syntaxes like Prisma or SQLAlchemy. This ensures the ORM correctly maps domain entities and relationships while maintaining data integrity.

How do I define appropriate indexes and integrity constraints for a relational database?

Defining appropriate indexes and integrity constraints requires applying PRIMARY KEY, FOREIGN KEY, NOT NULL, UNIQUE, and CHECK constraints to your tables. This ensures efficient querying and robust data integrity across the relational database.

Does schema design support generating documentation for tables and columns?

Schema design supports generating comprehensive documentation for tables and columns. Documenting your normalized relational database schema ensures clarity and maintainability for evolving business requirements and team collaboration.

When should I use 3NF normalization for my database schema?

You should use 3NF normalization for your database schema when creating robust, performant, and maintainable relational structures. It eliminates data redundancy and ensures data integrity for evolving business requirements like e-commerce platforms.