database-skill

Select backend databases and define initial schemas with naming conventions.

44|11|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/jiushiwon/wg-skills --skill database-skill-jiushiwon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-skill
Source: https://github.com/jiushiwon/wg-skills/tree/main/backend-generate-skill/database-skill
Command: npx skills add https://github.com/jiushiwon/wg-skills --skill database-skill-jiushiwon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps backend teams make consistent database choices, design initial schemas, define table conventions, and avoid unsafe production database synchronization practices.

Core Features & Use Cases

  • Database Selection: Compare PostgreSQL, MySQL, MongoDB, and time-series databases based on data relationships, transaction requirements, team familiarity, and workload characteristics.
  • Schema and Naming Guidance: Define core entities, standard fields, soft-delete conventions, password hashing requirements, and the default wg table prefix.
  • Migration Planning: Select appropriate migration tools for Java, Python, Node.js, and Go while enforcing explicit, version-controlled, reversible migrations in production.
  • Use Case: For an e-commerce backend, establish a PostgreSQL schema with prefixed users, products, orders, and payment tables, then document the migration strategy for the selected technology stack.

Quick Start

Ask the database skill to recommend a database, design the initial schema, and choose a production migration strategy for your backend project.

Frequently Asked Questions about database-skill

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

FAQPage Schema
How do I choose between PostgreSQL, MySQL, and MongoDB for my backend project?

Database selection depends on data relationships, transaction requirements, team familiarity, and workload characteristics. PostgreSQL and MySQL suit structured relational data, while MongoDB fits document schemas. This skill compares these databases to recommend the optimal choice for your backend domain.

What's the best way to design an initial database schema for an e-commerce backend?

Initial database schema design requires defining core entities, standard fields, and soft-delete conventions. For an e-commerce backend, this skill establishes a PostgreSQL schema with prefixed users, products, orders, and payment tables to ensure consistent database architecture.

How do I set up reversible database migrations for a Node.js or NestJS project?

Reversible database migrations require explicit, version-controlled migration tools. This skill selects appropriate migration tools for Node.js, NestJS, Java, Python, or Go stacks, restricting MongoDB generation to supported stacks while enforcing safe production migration strategies.

Does this database schema design approach support time-series databases for IoT workloads?

Time-series databases are supported for IoT workloads. The database selection process evaluates PostgreSQL, MySQL, MongoDB, and time-series databases against your workload characteristics to recommend the correct database type for domains like IoT, SaaS, and social applications.

What table naming conventions should I use for backend database design?

Table naming conventions should use a default wg table prefix. This schema design skill specifies table prefixes, core entities, standard fields, connection conventions, and password hashing requirements to maintain consistent backend database architecture.