schema-design

Designs relational schemas with normalization, keys, and naming conventions from domain requirements.

Updated Mar 29, 2026

Search Tags:#design #database #schema #normalization #naming-conventions #multitenancy #er-diagrams

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill schema-design-marquesfelip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schema-design
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/schema-design
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill schema-design-marquesfelip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing relational schemas is error-prone and time-consuming, often leading to inconsistent keys, poor normalization, and maintenance headaches across evolving domains.

Core Features & Use Cases

Map domain entities to tables with clear primary keys and appropriate foreign keys.
Apply 1NF/2NF/3NF and document justified denormalization for performance.
Plan for cross-cutting concerns like multi-tenancy, audit history, and naming conventions.

Quick Start

Describe your domain and constraints to generate a normalized relational schema design plan.

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 relational database schema from domain requirements?▼

Designing a relational database schema involves mapping domain entities to tables with clear primary keys and appropriate foreign keys. You then apply 1NF, 2NF, and 3NF normalization rules while documenting justified denormalization for performance.

What is the best way to plan a multi-tenant relational schema?▼

Planning a multi-tenant relational schema requires incorporating cross-cutting concerns directly into your entity mapping. You establish tenant isolation strategies and foreign key relationships to support multi-tenancy alongside audit history considerations.

How do I apply normalization rules and handle denormalization trade-offs?▼

Applying normalization rules involves structuring tables to satisfy 1NF, 2NF, and 3NF standards to eliminate data anomalies. You handle denormalization trade-offs by documenting specific cases where you intentionally violate normalization for query performance.

How do I add audit history and temporal support to a database schema?▼

Adding audit history to a database schema requires planning temporal and history support during the initial entity mapping phase. You structure your tables and foreign keys to track historical data changes and support cross-cutting audit requirements.

When should I use denormalization in a relational schema design?▼

You should use denormalization in a relational schema design when query performance demands it, but the choice must be a justified trade-off. You document the specific reasons for violating normalization rules to ensure maintenance clarity.