database-design
Database Design guides you through schema normalization, indexing strategies, and query optimization for both SQL and NoSQL systems. It covers normalization forms, denormalization trade-offs, index types, and migration patterns to help you build performant, maintainable databases. Use it when designing tables, fixing performance issues, or planning data migrations.
Database Design helps you create normalized schemas, plan indexing strategies, and optimize queries for SQL and NoSQL databases.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-21
Database Design helps you create normalized schemas, plan indexing strategies, and optimize queries for SQL and NoSQL databases. Database Design guides you through schema normalization, indexing strategies, and query optimization for both SQL and NoSQL systems. It covers normalization forms, denormalization trade-offs, index types, and migration patterns to help you build performant, maintainable databases. Use it when designing tables, fixing performance issues, or planning data migrations.
Use it when
- Database Design covers N+1 optimization by teaching you to batch queries, use eager loading in your ORM, or restructure joins.
- Database Design guides index creation by analyzing your query patterns first.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
CloudAI-X/claude-workflow-v2/database-design · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I design a database schema that performs well?
Database Design helps you structure schemas through normalization principles, index strategies, and denormalization trade-offs. Start by identifying entities and relationships, apply normalization forms (1NF through 3NF) to eliminate redundancy, then selectively denormalize where query patterns justify it. Use composite indexes for common filter and join operations, and plan migrations carefully to avoid downtime.
What's the best way to fix an N+1 query problem?
Database Design covers N+1 optimization by teaching you to batch queries, use eager loading in your ORM, or restructure joins. The core issue is fetching a parent record then looping to fetch children individually. Solutions include JOIN operations, ORM relationship loading (like includes/joins in Rails), or query result caching with Redis for frequently accessed data.
How should I approach database indexing strategy?
Database Design guides index creation by analyzing your query patterns first. Create indexes on columns used in WHERE, JOIN, and ORDER BY clauses. Use composite indexes when multiple columns filter together. Monitor with EXPLAIN ANALYZE to confirm indexes are used. Avoid over-indexing—each index slows writes. Balance read performance against write costs based on your workload.
What are zero downtime database migration patterns?
Database Design teaches safe migration patterns: add new columns as nullable, deploy code reading both old and new columns, backfill data gradually, then remove old columns in a later deployment. For schema changes, use feature flags and blue-green deployments. Test migrations on production-scale data first. Connection pooling configuration ensures requests don't timeout during long operations.
When should I denormalize vs. normalize my database?
Database Design explains that normalization (1NF–3NF) eliminates redundancy and maintains consistency, ideal for transactional systems. Denormalize when read performance is critical and updates are infrequent—store computed aggregates or duplicate data strategically. Analyze query patterns: if you always join the same tables, denormalization may be justified. Use caching (Redis) as an alternative before denormalizing.
What ORM best practices should I follow?
Database Design covers ORM best practices including connection pooling configuration to reuse database connections, eager loading to prevent N+1 queries, and batch operations for bulk inserts. Use parameterized queries to prevent SQL injection. Understand your ORM's lazy vs. eager loading behavior. Monitor connection pool exhaustion and query counts in production to catch performance regressions early.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Database Design
When to Load
- Trigger: Schema design, migrations, query optimization, indexing strategies, data modeling, N+1 fixes
- Skip: No database work involved in the current task
Database Design Workflow
Copy this checklist and track progress:
Database Design Progress:
- [ ] Step 1: Identify entities and relationships
- [ ] Step 2: Normalize schema (3NF minimum)
- [ ] Step 3: Evaluate denormalization needs
- [ ] Step 4: Design indexes for query patterns
- [ ] Step 5: Write and optimize critical queries
- [ ] Step 6: Plan migration strategy
- [ ] Step 7: Configure connection pooling
- [ ] Step 8: Validate against anti-patterns checklist
Schema Design Principles
Normalization Forms
``` 1NF: Atomic values, no repeating groups 2NF: 1NF + no partial dependencies (all non-key columns depend on full PK) 3NF: 2NF +
(truncated - see the full file via the links below)
File tree — 1 file
skills/database-design/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Design normalized database schemas and plan table structures”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Database Fundamentals guides code review of schemas, queries, and migrations across SQL and NoSQL systems. It surfaces common pitfalls like N+1 queries, missing indexes, and unsafe string concatenation, while providing checklists for normalization, data types, and reversible migrations.
This skill guides you through the complete lifecycle of database schema design, from conceptual modeling and logical design through physical optimization and safe migrations. It covers normalization principles, relationship patterns, indexing strategies, and query optimization techniques, with decision tables for choosing between SQL, document, and key-value storage engines. Includes zero-downtime migration patterns and backfill strategies to evolve schemas safely in production.
oma-db guides you through relational, document, and vector data modeling with schema documentation, integrity rules, and transaction design. It covers normalization, indexing, capacity planning, backup strategy, and anti-pattern remediation, plus ISO 27001/27002-aligned recommendations for security and continuity.
Database Design teaches you to think through structural decisions rather than copy patterns. It covers schema normalization, relationship modeling, index strategies, and ORM selection across PostgreSQL, SQLite, and serverless options. Work through decision checklists and optimization techniques to build performant databases suited to your deployment context.
Master database migration techniques including expand-contract patterns, safe index creation, and batch processing for large tables. This skill covers zero-downtime schema changes, foreign key constraints, and rollback strategies using Alembic.
Database Design teaches schema fundamentals, ORM selection, and performance tuning through structured decision-making rather than rote patterns. It covers normalization, relationship design, indexing strategy, and query optimization across PostgreSQL, SQLite, and serverless databases.
More skills database-design (MIT)