database-engineer

Design database schemas and plan migrations across PostgreSQL, MySQL, MongoDB, and Redis.

21|3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/JochenYang/Jochen-ai-rules --skill database-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-engineer
Source: https://github.com/JochenYang/Jochen-ai-rules/tree/main/.claude/skills/database-engineer
Command: npx skills add https://github.com/JochenYang/Jochen-ai-rules --skill database-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables robust database architecture design, performance tuning, and migration planning across relational and NoSQL systems. It helps teams design scalable schemas, optimize queries, implement indexing strategies, and plan zero-downtime migrations.

Core Features & Use Cases

  • Database Design: Schema design, normalization vs denormalization, partitioning and sharding, and data model decisions across relational and NoSQL stores.
  • Performance Optimization: Query analysis, EXPLAIN usage, index optimization, and execution plan tuning to meet performance targets.
  • Data Migration & High Availability: Migration planning (upgrades and cross-engine moves), replication strategies, backup/restore, and failover considerations.
  • Cross-Platform Guidance: Supports PostgreSQL, MySQL, MongoDB, Redis, and time-series databases with practical workflows.
  • Use Case: Migrating a large e-commerce database from MySQL to PostgreSQL with minimal downtime while preserving data integrity.

Quick Start

Define your target schema and run the migration plan script to outline steps for an offline/online migration and indexing optimization.

Frequently Asked Questions about database-engineer

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

FAQPage Schema
How do I design a scalable database schema for both relational and NoSQL stores?

Scalable database schema design requires evaluating normalization versus denormalization, partitioning, and sharding across PostgreSQL, MySQL, MongoDB, and Redis to meet specific data model and access pattern requirements.

What's the best way to plan a zero-downtime database migration from MySQL to PostgreSQL?

Zero-downtime database migration from MySQL to PostgreSQL requires script-driven workflows outlining offline or online steps to preserve data integrity while upgrading or moving across engines.

How do I optimize slow database queries using execution plans and indexing strategies?

Database query optimization uses EXPLAIN analysis, execution plan tuning, and index optimization strategies to identify bottlenecks and meet performance targets across supported database engines.

Does this database design approach support time-series databases and Redis?

Yes, cross-platform database design and optimization supports time-series databases and Redis alongside PostgreSQL, MySQL, and MongoDB with practical workflows for schema and performance tuning.

How do I manage database replication, backup, and failover for high availability?

Database high availability management involves configuring replication strategies, backup and restore procedures, and failover considerations to ensure continuous operation across relational and NoSQL stores.

When should I use denormalization versus normalization in my database architecture?

Normalization versus denormalization decisions depend on specific use cases ranging from transactional integrity to read-heavy access patterns, requiring data model decisions tailored across relational and NoSQL stores.