database

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

4|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/hiimtrung/coder --skill database-hiimtrung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/hiimtrung/coder/tree/main/.agents/skills/database
Command: npx skills add https://github.com/hiimtrung/coder --skill database-hiimtrung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design scalable data stores, manage migrations, and orchestrate data across PostgreSQL, MongoDB, and Redis for multi-application environments.

Core Features & Use Cases

  • Data Modeling & Schema Design for SQL and NoSQL
  • Migration Strategy & Versioning across multiple databases
  • Multi-Database Orchestration and Performance Tuning for distributed systems
  • Guidance on consistency, backups, and security across storage layers
  • Use Case: when migrating legacy schemas to a multi-database architecture, or designing a new scalable data layer.

Quick Start

Analyze an existing project’s data needs and propose a multi-database design with migration plan.

Frequently Asked Questions about database

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

FAQPage Schema
How do I design a scalable multi-database architecture using PostgreSQL, MongoDB, and Redis?

To design a scalable multi-database architecture, you model domain schemas across PostgreSQL, MongoDB, and Redis while enforcing cross-database consistency. This approach separates domain logic from persistence to optimize high-volume data workloads and multi-tenant systems.

What is the best way to plan legacy database migrations to a new SQL and NoSQL schema?

The best way to plan legacy database migrations is by creating versioned migration strategies and data mappings. This ensures strict separation between domain logic and persistence layers while maintaining data consistency during the transition to multi-database environments.

Can I use this approach for multi-tenant systems requiring cross-database consistency?

Yes, this approach explicitly supports multi-tenant systems requiring cross-database consistency. It provides resilience patterns and performance tuning to manage distributed data orchestration across PostgreSQL, MongoDB, and Redis for high-volume workloads.

How does multi-database orchestration handle performance tuning for distributed systems?

Multi-database orchestration handles performance tuning by applying resilience patterns and strict separation between domain logic and persistence. It optimizes data mappings and consistency across PostgreSQL, MongoDB, and Redis storage layers for distributed environments.

When do I need versioned migrations and data mappings for multi-database environments?

You need versioned migrations and data mappings when migrating legacy schemas or designing new scalable data layers. They ensure consistency, backups, and security across PostgreSQL, MongoDB, and Redis storage layers in multi-application environments.