datagsm-server: Skill for Claude Code

Database Schema Design Guide

Before providing schema guidance, ask the user about their migration tooling:

AskUserQuestion: "DB 마이그레이션 도구로 무엇을 사용하고 있나요?"
options:
  - Flyway
  - Liquibase
  - 사용하지 않음 (JPA DDL auto)

Then provide the relevant migration section below along with the core conventions.

---

Naming Conventions

• Tables: snake_case, plural (users, api_keys)
• Columns: snake_case (created_at, is_active)
• FK columns: {referenced_table_singular}_id (user_id, club_id)
• Index names: idx_{table}_{columns} (idx_users_email)
• UK names: uq_{table}_{columns} (uq_users_email)

Standard Columns

Include in every entity table:

id         BIGINT       NOT NULL AUTO_INCREMENT PRIMARY KEY,
created_at DATETIME(6)  NOT NULL DEFAULT CURRENT_TIMESTAMP(6),
updated_at DATETIME(6)  NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6)

Index Strategy

• Single column used frequently in WHERE: simple index
• WHERE + ORDER BY combination: composite index (WHERE column first)
• Low-cardinality columns (is_active, status enum): indexing rarely helps

-- Composite index example
CREATE INDEX idx_posts_user_created ON posts (user_id, created_at DESC);

Migration — Flyway

(Include this section if the user selected Flyway)

File naming: V{version}__{description}.sql

db/migration/
  V1__create_users.sql
  V2__add_api_keys.sql
  V3__add_index_users_email.sql

-- V2__add_api_keys.sql
CREATE TABLE api_keys (
    id         BIGINT      NOT NULL AUTO_INCREMENT PRIMARY KEY,
    user_id    BIGINT      NOT NULL,
    key_value  VARCHAR(64) NOT NULL,
    created_at DATETIME(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6),
    updated_at DATETIME(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6),
    CONSTRAINT fk_api_keys_user FOREIGN KEY (user_id) REFERENCES users (id),
    CONSTRAINT uq_api_keys_value UNIQUE (key_value)
);

Migration — Liquibase

(Include this section if the user selected Liquibase)