Agent skill · data analytics · aiskillstore
database-schema-designer
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable 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 Design production-ready database schemas with best practices built-in. --- Quick Start Just describe your data model: You'll get a complete SQL schema like: What to include in your request: Entities (users, products, orders) Key relationships (users have orders, orders have items) Scale hints (high-traffic, millions of records) Database preference (SQL/NoSQL) - defaults to SQL if not specified --- Triggers Trigger Example --------- --------- design schema "design a schema for user authentication" database design "database design for multi-tenant SaaS" create tables "create tables for a blog system" schema for "schema for inventory management" model data "model data for real-time analytics" I need a database "I need a database for tracking orders" design NoSQL "design NoSQL schema for product catalog" --- Key Terms Term Definition ------ ------------ Normalization Organizing data to reduce redundancy (1NF → 2NF → 3NF) 3NF Third Normal Form - no transitive dependencies between columns OLTP Online Transaction Processing - write-heavy, needs normalization OLAP Online Analytical Processing - read-heavy, benefits from denormalization Foreign Key (FK) Column that references another table's primary key Index Data structure that speeds up queries (at cost of slower writes) Access Pattern How your app reads/writes data (queries, joins, filters) Denormalization Intentionally duplicating data to speed up reads --- Quick Reference Task Approach Key Consideration ------ ---------- ------------------- New schema Normalize to 3NF first Domain modeling over UI SQL vs NoSQL Access patterns decide Read/write ratio matters Primary keys INT or UUID UUID for distributed systems Foreign keys Always constrain ON DELETE strategy critical Indexes FKs + WHERE columns Column order matters Migrations Always reversible Backward compatible first --- Process Overview --- Commands Command When to Use Action --------- ------------- -------- design schema for {domain} Startin …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/database-schema-designer--087949