database-schema-design

Automates PostgreSQL and MySQL schema validation for normalization, constraints, and indexing guidance.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ShadowAUS/chez-king-portal --skill database-schema-design-shadowaus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-schema-design
Source: https://github.com/ShadowAUS/chez-king-portal/tree/main/.tessl/tiles/secondsky/claude-skills/plugins/database-schema-design/skills/database-schema-design
Command: npx skills add https://github.com/ShadowAUS/chez-king-portal --skill database-schema-design-shadowaus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Database schema design and validation guidance for PostgreSQL and MySQL, emphasizing normalization, relationships, constraints, and audit patterns.

Core Features & Use Cases

  • Templates and references for normalization (1NF–5NF), relationship patterns, audit/versioning patterns, and best-practice constraints.
  • Guidance to prevent common design flaws, ensure data integrity, and improve maintainability across projects.
  • Use cases include starter schemas for new projects, safe migrations, and comprehensive schema reviews.

Quick Start

Apply the templates and references to bootstrap a production-ready schema design.

Frequently Asked Questions about database-schema-design

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

FAQPage Schema
How do I design a database schema with proper normalization and foreign keys?

To validate schema normalization, apply templates covering 1NF through 5NF, relationship patterns, and audit columns. These references prevent design flaws and ensure data integrity during new project bootstrapping or migrations.

What is the best way to add audit columns and jsonb constraints to an existing database?

The best way to add audit columns and jsonb constraints is to apply established versioning patterns and best-practice constraints during schema migrations. This maintains data integrity while extending PostgreSQL or MySQL functionality.

Does this schema validation approach work for both PostgreSQL and MySQL migrations?

Yes, this schema validation approach works for PostgreSQL and MySQL migrations. It provides indexing guidance and constraint validation to ensure safe structural changes and robust schema reviews across both database platforms.

How do I validate 3NF compliance and indexing strategies during a database schema review?

Validating 3NF compliance and indexing strategies during a schema review involves checking normalization levels, explicit foreign keys, and proper data types. Applying these references prevents common design flaws and improves maintainability.

When should I use explicit foreign keys and audit columns in my database schema design?

Explicit foreign keys and audit columns should be used in any production-ready database schema design. They enforce data integrity and provide versioning patterns necessary for safe migrations and comprehensive code reviews.