database

Design migration-driven data persistence layers for PostgreSQL, MongoDB, and Redis.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/takayatomose/tas-agent-skills --skill database-takayatomose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/takayatomose/tas-agent-skills/tree/main/.agents/skills/database
Command: npx skills add https://github.com/takayatomose/tas-agent-skills --skill database-takayatomose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design scalable, resilient, and consistent data persistence layers across relational, document, and in-memory stores to prevent data loss, performance bottlenecks, and schema drift.

Core Features & Use Cases

  • Schema & Migration Planning: Provides migration-first workflows and naming conventions to safely evolve schemas without relying on unsafe auto-sync in production.
  • Multi-Database Architecture: Guides when to use PostgreSQL for transactional metadata, MongoDB for high-volume append-only data, and Redis for ephemeral state and rate limiting.
  • Operational Resilience: Recommends transaction patterns, connection pooling, timeouts, retry strategies, and anti-corruption mappers to maintain stability.
  • Use Case: For a SaaS multi-tenant backend, use this Skill to select a tenant isolation strategy, design ORM entities and migrations, and produce a migration rollout plan with rollback considerations.

Quick Start

Use the database skill to analyze your application's read/write patterns and produce a safe, migration-driven schema and deployment plan for PostgreSQL, MongoDB, and Redis.

Frequently Asked Questions about database

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

FAQPage Schema
How do I design a multi-tenant database architecture for a SaaS backend?

Multi-tenant database design requires selecting a tenant isolation strategy and mapping ORM entities to match your read/write patterns. Using PostgreSQL for transactional metadata and MongoDB for high-volume append-only data ensures scalable, resilient persistence.

What is the best way to manage database migrations without schema drift?

Database migrations should follow a migration-first workflow with strict naming conventions to safely evolve schemas. This approach prevents unsafe auto-sync in production and produces a rollout plan with rollback considerations to maintain transaction integrity.

When should I use PostgreSQL, MongoDB, and Redis together in a backend?

Use PostgreSQL for transactional metadata, MongoDB for high-volume append-only data, and Redis for ephemeral state and rate limiting. This multi-database architecture supports high-throughput event-driven systems by matching data persistence layers to specific read/write requirements.

How do I maintain operational resilience in a data persistence layer?

Operational resilience in a data persistence layer requires transaction patterns, connection pooling, timeouts, and retry strategies. Implementing anti-corruption mappers and parameterized queries maintains stability and prevents persistence leakage across your database architecture.

How do I plan a database migration rollout with rollback considerations?

A database migration rollout plan requires migration-driven schema changes and transaction integrity to ensure safe deployment. Establishing naming conventions and anti-corruption mapping layers maintains stability and enables safe rollback execution if issues arise.