Designing Schemas

Design normalized PostgreSQL schemas from technical specifications with constraints.

1|2|Updated Feb 5, 2026

Search Tags:#schema design #database #postgresql #data modeling #sql #normalization

Ready to run

npx skills add https://github.com/7a336e6e/skills --skill designing-schemas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Designing Schemas
Source: https://github.com/7a336e6e/skills/tree/main/database/designing-schemas
Command: npx skills add https://github.com/7a336e6e/skills --skill designing-schemas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of normalized, integrity-enforced PostgreSQL database schemas directly from technical specifications, ensuring data quality and maintainability.

Core Features & Use Cases

Schema Design: Translates requirements into normalized PostgreSQL tables.
Constraint Enforcement: Implements NOT NULL, UNIQUE, CHECK, and foreign key constraints.
Standardization: Ensures consistent naming conventions and includes standard columns (id, created_at, updated_at).
Use Case: When starting a new feature that requires database storage, use this Skill to generate the initial SQL schema definition based on the feature's data requirements.

Quick Start

Use the Designing Schemas skill to create a PostgreSQL schema for users and their associated profiles based on the provided tech spec.

Frequently Asked Questions about Designing Schemas

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

FAQPage Schema

How do I design a normalized PostgreSQL schema from a technical specification?▼

PostgreSQL schema design enforces data quality by implementing NOT NULL, UNIQUE, CHECK, and foreign key constraints. These constraints maintain integrity by strictly validating relationships and preventing invalid data entries during new feature development or schema refactoring.

How do I enforce data integrity during PostgreSQL data modeling?▼

PostgreSQL schema design enforces data integrity by implementing NOT NULL, UNIQUE, CHECK, and foreign key constraints. These constraints maintain integrity by strictly validating relationships and preventing invalid data entries during new feature development or schema refactoring.

What is the best way to refactor an existing PostgreSQL database schema?▼

Yes, PostgreSQL data modeling applies to both new feature development and schema refactoring. It reviews existing data models against technical specifications to update constraints, normalize tables to 3NF, and standardize required columns.

What standard columns should I include in PostgreSQL schema design?▼

Standard columns required in PostgreSQL schema design include id, created_at, and updated_at. Including these specific standard columns alongside proper foreign key relationships ensures consistent data tracking and structural integrity across all normalized tables.

Does PostgreSQL schema design require Third Normal Form by default?▼

Yes, PostgreSQL schema design requires adherence to Third Normal Form (3NF) by default. Normalizing tables to 3NF from technical specifications prevents data anomalies and ensures robust, maintainable database structures.