database-manager

Manage PostgreSQL, MySQL, and MongoDB schema design, migrations, and queries.

3|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/TheArchitectit/awesome-cline-skills --skill database-manager-thearchitectit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-manager
Source: https://github.com/TheArchitectit/awesome-cline-skills/tree/main/skills/database-manager
Command: npx skills add https://github.com/TheArchitectit/awesome-cline-skills --skill database-manager-thearchitectit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the fragmented, error-prone workflow of managing multiple database systems (PostgreSQL, MySQL, MongoDB) with inconsistent tools and practices, reducing production incidents and manual overhead for development and operations teams.

Core Features & Use Cases

  • Cross-platform schema design: Provides normalization guidelines, table/collection design patterns, and relationship best practices for relational (PostgreSQL/MySQL) and document (MongoDB) databases, with clear guidance on denormalization and hybrid patterns for performance.
  • Safe migration workflows: Covers forward-only production migrations, reversible development migrations, and zero-downtime schema change patterns for Alembic, Prisma, Flyway, and native MongoDB migrations, with step-by-step safe change examples to avoid production outages.
  • Performance and administration: Includes slow query identification, EXPLAIN analysis, index strategy, backup/recovery configuration, and connection pooling setup for all three database platforms, plus troubleshooting for common connectivity and performance issues.
  • Use Case: A development team building a SaaS product with a hybrid PostgreSQL (user data) and MongoDB (content logs) architecture can use this skill to design consistent schemas, write non-blocking migrations for new features, and optimize slow reporting queries without downtime.

Quick Start

Use the database-manager skill to design a normalized users table schema for a new e-commerce feature and write a non-blocking migration to add it to the existing PostgreSQL database.

Frequently Asked Questions about database-manager

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

FAQPage Schema
How do I write zero-downtime database migrations for PostgreSQL and MySQL?

To write zero-downtime database migrations, use forward-only production patterns and reversible development workflows with tools like Alembic, Prisma, or Flyway to apply non-blocking schema changes safely. This prevents production outages during deployments.

What is the best way to design schemas for a hybrid PostgreSQL and MongoDB architecture?

Designing schemas for hybrid PostgreSQL and MongoDB architectures requires applying normalization guidelines for relational user data and specific relationship patterns for document content logs. This ensures consistent, performant data modeling across both database platforms.

How do I optimize slow queries using EXPLAIN analysis across PostgreSQL, MySQL, and MongoDB?

Optimizing slow queries involves running EXPLAIN analysis to identify bottlenecks and applying targeted index strategies across PostgreSQL, MySQL, and MongoDB. This resolves performance issues and improves reporting query execution times.

Can I manage backup configuration and connection pooling for multiple database systems together?

You can manage backup configuration and connection pooling setup for PostgreSQL, MySQL, and MongoDB together using unified administration workflows. This centralizes disaster recovery and resolves common connectivity and performance issues.

When do I need denormalization in MongoDB compared to normalized tables in PostgreSQL?

Denormalization in MongoDB is needed when optimizing document content logs for read performance, whereas normalized tables in PostgreSQL ensure data integrity for relational user records. Hybrid patterns blend both approaches for specific performance requirements.