{"enrichment":{"faq":[{"a":"database-schema-design guides you through conceptual modeling, logical design, and physical optimization. Start by identifying entities and their relationships, apply normalization principles to eliminate redundancy, define primary and foreign keys, and add constraints. The skill covers relationship patterns (one-to-one, one-to-many, many-to-many), denormalization trade-offs, and indexing strategies to balance query performance with storage efficiency.","q":"How do I design a database schema?"},{"a":"database-schema-design emphasizes normalization to reduce data anomalies, explicit relationship definitions with foreign keys, appropriate constraint enforcement, and strategic indexing. Key practices include avoiding N+1 query patterns, choosing composite indexes wisely, designing for your access patterns, considering multi-tenancy isolation early, and planning schema evolution. Document your design decisions and validate them against real query workloads.","q":"What are database schema design best practices?"},{"a":"database-schema-design provides decision tables to guide your choice. Use SQL for structured data with complex relationships, ACID requirements, and evolving schemas. Choose NoSQL (document stores) for flexible schemas, horizontal scaling, and denormalized data patterns. Key-value stores suit caching and sessions. Consider your consistency needs, query patterns, team expertise, and growth trajectory. The skill covers schema design patterns specific to each engine.","q":"SQL vs NoSQL\u2014which should I use?"},{"a":"database-schema-design covers zero-downtime migration patterns and rollback strategies. Deploy schema changes separately from application code, use feature flags to gate new columns, backfill data in batches to avoid locking, and maintain dual-write periods during transitions. Always test migrations on production-like data volumes, monitor performance impact, and keep rollback procedures documented and practiced.","q":"How do I create database migrations safely?"},{"a":"database-schema-design teaches query pattern analysis to identify hot paths, then covers single-column indexes for WHERE and JOIN conditions, composite indexes for multi-column filters, and covering indexes to enable index-only scans. Avoid over-indexing\u2014each index slows writes. Monitor slow query logs, use EXPLAIN plans to validate index usage, and regularly remove unused indexes. Balance read optimization against write costs.","q":"What indexing strategy improves database query performance?"},{"a":"database-schema-design explains normalization principles (1NF through 3NF) to eliminate anomalies and redundancy, then covers denormalization trade-offs. Normalize by default for data integrity and storage efficiency. Denormalize strategically when query performance analysis shows repeated joins are bottlenecks, but accept increased storage and update complexity. Document denormalization decisions and validate them against real workloads before committing.","q":"Should I normalize or denormalize my database?"}],"shadow_tags":["data-modeling","schema-evolution","query-performance","migration-safety","normalization-strategy","index-optimization","relational-design","storage-engine-selection","zero-downtime-deployment","database-architecture"],"summary_rewrite":"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."},"files":[{"bytes":13215,"path":"templates/skills/database-schema-design/SKILL.md","sha256":"f21c998c0005b1766bba30c2f392570f1261ee37699159a3955c0c6d9d99162f","url":"https://skillfed.io/files/Pixel-Process-UG/superkit-agents/database-schema-design/7632df46/SKILL.md"}],"id":"Pixel-Process-UG/superkit-agents/database-schema-design","links":{"html":"https://skillfed.io/Pixel-Process-UG/superkit-agents/database-schema-design","md":"https://skillfed.io/Pixel-Process-UG/superkit-agents/database-schema-design.md","repo":"https://github.com/Pixel-Process-UG/superkit-agents"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":0,"language":"TypeScript","last_updated":"2026-03-16","license":"MIT","name":"database-schema-design","publisher":"Pixel-Process-UG","stars":1},"relations":{"categories":["database-engineering","backend-development","data-architecture"],"similar":[{"id":"curiositech/some_claude_skills/database-design-patterns"},{"id":"softaworks/agent-toolkit/database-schema-designer"},{"id":"srstomp/pokayokay/database-design"},{"id":"EliasOulkadi/shokunin/db-sculptor"},{"id":"CloudAI-X/claude-workflow-v2/database-design"},{"id":"softspark/ai-toolkit/database-patterns"},{"id":"martinholovsky/claude-skills-generator/database-design"},{"id":"first-fluke/oh-my-agent/oma-db"},{"id":"DanielPodolsky/ownyourcode/database"},{"id":"olehsvyrydov/AI-development-team/dba"}]},"slug":{"owner":"Pixel-Process-UG","repo":"superkit-agents","skill":"database-schema-design"},"version":"7632df46"}