design-relational-schema

Designs normalized relational database schemas from functional requirements.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill design-relational-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-relational-schema
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/design-relational-schema
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill design-relational-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates common database design pitfalls like update anomalies, data redundancy, and poor query performance by guiding you through the creation of a logically sound, normalized relational model.

Core Features & Use Cases

  • Normalization & Modeling: Transforms raw requirements into 3NF/BCNF compliant tables with clear entity-relationship mapping.
  • Constraint Enforcement: Ensures data integrity by defining primary keys, foreign keys, check constraints, and exclusion rules directly in the DDL.
  • Use Case: Use this when you are starting a new project and need to define the database structure for a complex domain, ensuring that your schema is scalable, consistent, and optimized for your specific access patterns.

Quick Start

Use the design-relational-schema skill to model the database tables and constraints for a new e-commerce order management system based on these requirements.

Frequently Asked Questions about design-relational-schema

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

FAQPage Schema
How do I design a normalized relational database schema from functional requirements?

Designing a normalized relational database schema involves defining entities, relationships, and integrity constraints from raw requirements to ensure 3NF compliance and eliminate update anomalies or data redundancy.

What is the best way to enforce cardinality and data integrity in SQL DDL?

Enforcing cardinality and data integrity in SQL DDL requires defining primary keys, foreign keys, check constraints, and exclusion rules directly in the schema to prevent inconsistent relational states.

When should I use deliberate denormalization strategies in database modeling?

Deliberate denormalization strategies in database modeling should be used for read-heavy workloads where optimal physical modeling and query performance outweigh the strict 3NF compliance needed for write-heavy domains.

How do I select surrogate keys during relational schema modeling?

Selecting surrogate keys during relational schema modeling involves choosing artificial identifiers that maintain integrity constraints while ensuring clear entity-relationship mapping across normalized tables.

Does this database schema modeling approach support BCNF compliance?

Yes, this database schema modeling approach supports BCNF compliance by applying normalization techniques to transform raw domain requirements into logically sound relational tables with clear entity-relationship mapping.