database

Provides expert guidance on designing, optimizing, and migrating databases across relational and NoSQL engines.

Updated Aug 27, 2026

Search Tags:#query optimization #indexing #schema design #database #migration #sql #nosql

Ready to run

npx skills add https://github.com/sharkitect-solutions/sharkitect-claude-toolkit --skill database-sharkitect-solutions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database
Source: https://github.com/sharkitect-solutions/sharkitect-claude-toolkit/tree/main/skills/database
Command: npx skills add https://github.com/sharkitect-solutions/sharkitect-claude-toolkit --skill database-sharkitect-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on designing robust database schemas, optimizing query performance, selecting the right database engine, and managing migrations effectively, preventing common pitfalls and ensuring data integrity and speed.

Core Features & Use Cases

Schema Design: Guidance on normalization, composite keys, and temporal data patterns.
Query Optimization: Techniques for indexing, EXPLAIN ANALYZE interpretation, and N+1 detection.
Engine Selection: Frameworks and comparisons for choosing between SQLite, Postgres, MySQL, MongoDB, Redis, and DynamoDB.
Migration Architecture: Strategies for zero-downtime deployments and safe data backfilling.
Use Case: A developer needs to choose between Postgres and MongoDB for a new project, understand how to index their tables for faster queries, and plan a schema migration without downtime.

Quick Start

Use the database skill to help me choose between Postgres and MongoDB for a new project.

Frequently Asked Questions about database

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

FAQPage Schema

How do I choose between PostgreSQL and MongoDB for a new project?▼

Choosing between PostgreSQL and MongoDB depends on your workload characteristics and operational requirements. Decision frameworks compare relational versus NoSQL paradigms to match engine capabilities with your specific data access patterns and consistency needs.

How do I optimize slow SQL queries using EXPLAIN ANALYZE?▼

Optimizing slow SQL queries using EXPLAIN ANALYZE involves interpreting the execution plan to identify bottlenecks. Techniques include adding proper indexing strategies and resolving N+1 query problems to significantly improve database performance.

What is the best way to design a normalized database schema?▼

Designing a normalized database schema requires structuring tables to reduce data redundancy using composite keys and temporal data patterns. Proper schema design ensures data integrity and lays the groundwork for efficient querying.

How do I perform a zero-downtime database migration?▼

Performing a zero-downtime database migration requires specific migration architecture strategies. These patterns ensure safe data backfilling and seamless schema transitions during deployment without taking the application offline.

When should I use Redis or DynamoDB over a relational database?▼

Use Redis or DynamoDB over a relational database when your workload demands high throughput key-value access or specific operational requirements. Engine selection frameworks evaluate these NoSQL options against relational constraints to determine the right fit.

Why does my database have an N+1 query problem and how do I fix it?▼

An N+1 query problem occurs when an application executes individual queries for related records instead of a single joined query. Detection and resolution techniques involve query optimization and proper indexing to batch data retrieval.