Agent skill · data analytics · aiskillstore
database-schema-designer
Use this skill when designing database schemas for relational (SQL) or document (NoSQL) databases. Provides normalization guidelines, indexing strategies, migration patterns, and performance optimization techniques. Ensures scalable, maintainable, and performant data models.
Why this skill is useful
Provides specific normalization guidelines and indexing strategies that the AI wouldn't reliably generate on its own.
What it needs
About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Database Schema Designer Overview This skill provides comprehensive guidance for designing robust, scalable database schemas for both SQL and NoSQL databases. Whether building from scratch or evolving existing schemas, this framework ensures data integrity, performance, and maintainability. When to use this skill: Designing new database schemas Refactoring or migrating existing schemas Optimizing database performance Choosing between SQL and NoSQL approaches Creating database migrations Establishing indexing strategies Modeling complex relationships Planning data archival and partitioning Database Design Philosophy Core Principles 1. Model the Domain, Not the UI Schema reflects business entities and relationships Don't let UI requirements drive data structure Separate presentation concerns from data model 2. Optimize for Reads or Writes (Not Both) OLTP (transactional): Normalized, optimized for writes OLAP (analytical): Denormalized, optimized for reads Choose based on access patterns 3. Plan for Scale From Day One Indexing strategy Partitioning approach Caching layer Read replicas 4. Data Integrity Over Performance Use constraints, foreign keys, validation Performance issues can be optimized later Data corruption is costly to fix --- SQL Database Design Normalization Database normalization reduces redundancy and ensures data integrity. 1st Normal Form (1NF) Rule: Each column contains atomic (indivisible) values, no repeating groups. 2nd Normal Form (2NF) Rule: Must be in 1NF + all non-key columns depend on the entire primary key. 3rd Normal Form (3NF) Rule: Must be in 2NF + no transitive dependencies (non-key columns depend only on primary key). Denormalization (When to Break Rules) Sometimes denormalization improves performance for read-heavy applications. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/database-schema-designer