菜单
Project-aware expert-role database schema and modeling design. Reads project docs first, then produces a schema design, migration plan, or query optimization strategy consistent with the current repository constraints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Language-agnostic endpoint documentation generator. Reads routing and codebase to produce structured API contract documentation for existing endpoints.
Expert-role parity check across project docs, platform instruction surfaces, skills, reusable prompts, workflows, quick-reference material, and implementation evidence when authority depends on the current codebase. Use when checking whether the template system still agrees with itself or when preparing cleanup after major changes.
Project-aware expert-role contract design for APIs, interfaces, repositories, services, message schemas, and module boundaries. Reads project docs first, then produces or reviews a contract consistent with the current repository.
Project-aware expert-role broad verification that reads project docs first, classifies the verification target, and routes to the best specialist skill for executable or non-executable checks across code, contracts, docs, architecture, quality, security, reliability, and project health.
Project-aware expert-role for CI/CD pipeline design and implementation. Reads project docs first, enforces build caching, security gates, test execution, and deployment safety.
Project-aware expert-role for code refactoring. Reads project docs first, enforces TDD, and restructures code to reduce cyclomatic complexity and improve maintainability without altering external behavior.
| name | db-schema-design |
| description | Project-aware expert-role database schema and modeling design. Reads project docs first, then produces a schema design, migration plan, or query optimization strategy consistent with the current repository constraints. |
| argument-hint | Describe the domain entities, tables, relationships, or queries to design or review |
Produces a project-aware, expert-level database schema design or review by reading the repository's project docs first, then applying a rigorous data modeling method.
This skill is reusable across:
It should not assume a specific database engine, ORM, or normalization strategy until the project docs confirm them.
| Document | Why it matters |
|---|---|
docs/project-docs/development/database.md | Defines the actual database engines, ORMs, migration tools, naming conventions, and constraints. |
docs/project-docs/foundation/architecture.md | Defines where data logic lives (e.g., repository layer) and integration boundaries. |
docs/project-docs/foundation/prd.md | Clarifies the feature scale, expected data volume, and access patterns. |
docs/project-docs/development/testing.md | Defines how data layer code and migrations should be validated. |
If the repository lacks the database docs needed for the task, call that out and create or update the missing docs instead of inventing local rules in the skill.
Use this skill when designing or reviewing one of these boundary types:
| Boundary type | Typical artifacts |
|---|---|
| Schema Creation | Tables, columns, types, constraints, foreign keys, indexes |
| Migrations | Up/Down migration scripts, data backfills, zero-downtime strategies |
| Query Optimization | EXPLAIN plans, index selection, join reduction |
| Data Modeling | Domain entities, aggregates, document embedding vs referencing |
| Caching | Cache keys, TTL strategies, eviction policies |
Extract from database.md:
Extract from prd.md and feature docs:
Design the minimal schema that supports the required behavior. Specify:
UUID or TIMESTAMPTZ over generic strings if the engine supports it)Define the indexes required for the access patterns identified in Step 2.
Specify how the schema will be deployed safely:
Use testing.md to decide how this will be validated.
Examples:
Use this checklist when reviewing an existing schema or PR:
When using this skill, the output should include:
@agent use db-schema-design on [Target Feature/Entity] focusing on [Specific Requirement/Database Type].