ahnyongjooandClaude Sonnet 5.5
964a841de1
- Code\rebar_pipeline, review_pipeline, pier-program을 정션에서 실제 폴더로 전환 - Code\rhino_mcp 및 CLAUDE_rhino배경.md 추가, .mcp.json은 PYTHONPATH로 새 위치 사용 - pier-program 내부 .git 제거(이력은 backup\pier-program_20261028.bundle에 보관) - worktree 가이드 반영(CLAUDE.local.md, HANDOFF.md) - D:\Rhino-MCP 경로 참조를 새 위치로 치환 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
144 lines
4.3 KiB
Markdown
144 lines
4.3 KiB
Markdown
---
|
|
name: phase-1-schema
|
|
classification: capability
|
|
classification-reason: Pattern guidance may overlap with model's built-in knowledge as it improves
|
|
deprecation-risk: medium
|
|
description: |
|
|
Define project terminology, data structures, entities, and relationships.
|
|
Triggers: schema, data model, entity, terminology, 스키마, 데이터 모델, 용어.
|
|
agent: hmcmkit:pipeline-guide
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Glob
|
|
- Grep
|
|
user-invocable: false
|
|
imports:
|
|
- ${PLUGIN_ROOT}/templates/pipeline/phase-1-schema.template.md
|
|
- ${PLUGIN_ROOT}/templates/shared/naming-conventions.md
|
|
next-skill: phase-2-convention
|
|
pdca-phase: plan
|
|
task-template: "[Phase-1] {feature}"
|
|
---
|
|
|
|
# Phase 1: Schema/Terminology Definition
|
|
|
|
> Define terminology and data structures used throughout the project
|
|
|
|
## Purpose
|
|
|
|
Unify the language of the project. Ensure all team members (or AI) communicate using the same terms and clearly understand data structures.
|
|
|
|
## What to Do in This Phase
|
|
|
|
1. **Build Glossary**: Map business terms + global standards
|
|
2. **Identify Entities**: Determine what "things" exist
|
|
3. **Define Relationships**: Relationships between entities
|
|
4. **Design Schema**: Define data structures
|
|
|
|
## Glossary
|
|
|
|
### Why is it Needed?
|
|
|
|
**Explaining business terms to Antigravity Platform every time is tedious**.
|
|
Creating a glossary allows:
|
|
- AI Agent to automatically reference for context understanding
|
|
- Team communication consistency
|
|
- Reduced onboarding time for new team members/AI
|
|
|
|
### Term Categories
|
|
|
|
| Category | Description | Example |
|
|
|----------|-------------|---------|
|
|
| **Business Terms** | Internal proprietary terms | "Caddy" (golf booking assistant) |
|
|
| **Global Standards** | Industry common or technical standard terms | "OAuth", "REST API" |
|
|
| **Mapping** | Business ↔ Global correspondence | "Member" = User, "Payment" = Payment |
|
|
|
|
### Glossary Template
|
|
|
|
```markdown
|
|
## Business Terms (Internal Terms)
|
|
|
|
| Term | English | Definition | Global Standard Mapping |
|
|
|------|---------|------------|------------------------|
|
|
| Caddy | Caddy | AI assistant that helps book golf rounds | Booking Assistant |
|
|
| Round | Round | One 18-hole golf play | Session, Booking |
|
|
| Green Fee | Green Fee | Golf course usage fee | Usage Fee |
|
|
|
|
## Global Standards
|
|
|
|
| Term | Definition | Reference |
|
|
|------|------------|-----------|
|
|
| OAuth 2.0 | Authentication protocol | RFC 6749 |
|
|
| REST | API architecture style | - |
|
|
| UUID | Universal Unique Identifier | RFC 4122 |
|
|
|
|
## Term Usage Rules
|
|
|
|
1. Use **English** in code (`Caddy`, `Round`)
|
|
2. Use **local language** in UI/docs (Caddy, Round)
|
|
3. API responses prioritize **global standards** (`booking_assistant`)
|
|
```
|
|
|
|
### Antigravity Platform Auto-Reference Setup
|
|
|
|
To have AI Agent automatically reference the glossary:
|
|
|
|
**Method 1**: Include in agents.md
|
|
```markdown
|
|
## Term Reference
|
|
For this project's term definitions, see `docs/01-plan/glossary.md`.
|
|
```
|
|
|
|
**Method 2**: Add term rules to project agents.md
|
|
```markdown
|
|
<!-- Add to agents.md -->
|
|
Project terms are defined in docs/01-plan/glossary.md.
|
|
Always reference when using business terms.
|
|
```
|
|
|
|
## Deliverables
|
|
|
|
```
|
|
docs/01-plan/
|
|
├── glossary.md # Glossary (recommended new)
|
|
│ ├── Business Terms
|
|
│ ├── Global Standards
|
|
│ └── Mapping Table
|
|
├── schema.md # Data schema
|
|
├── terminology.md # (existing) → recommend merging into glossary.md
|
|
└── domain-model.md # Domain model
|
|
```
|
|
|
|
## PDCA Application
|
|
|
|
- **Plan**: Identify what entities/terms are needed
|
|
- **Design**: Design schema structure, relationships
|
|
- **Do**: Write documentation
|
|
- **Check**: Review for omissions/contradictions
|
|
- **Act**: Finalize and proceed to Phase 2
|
|
|
|
## Level-wise Application
|
|
|
|
| Level | Application Level |
|
|
|-------|------------------|
|
|
| Starter | Simple (core terms only) |
|
|
| Dynamic | Detailed (all entities) |
|
|
| Enterprise | Detailed (per microservice) |
|
|
|
|
## Example Questions
|
|
|
|
```
|
|
"What are the core 'things' this project deals with?"
|
|
"What are the relationships between users, products, orders...?"
|
|
"Are 'member' and 'user' the same or different?"
|
|
```
|
|
|
|
## Template
|
|
|
|
See `templates/pipeline/phase-1-schema.template.md`
|
|
|
|
## Next Phase
|
|
|
|
Phase 2: Coding Convention → Now that terms are defined, define code rules
|