Skill for defining terminology and data structures used throughout the project. Covers domain terminology, entities, relationships, and schema design. Triggers: schema, terminology, data model, entity, 스키마, 用語, データモデル, 数据模型
/plugin marketplace add popup-studio-ai/bkit-claude-code/plugin install bkit@bkit-marketplaceThis skill is limited to using the following tools:
Define terminology and data structures used throughout the project
Unify the language of the project. Ensure all team members (or AI) communicate using the same terms and clearly understand data structures.
Explaining business terms to Claude Code every time is tedious. Creating a glossary allows:
| 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 |
## 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`)
To have Claude automatically reference the glossary:
Method 1: Include in CLAUDE.md
## Term Reference
For this project's term definitions, see `docs/01-plan/glossary.md`.
Method 2: Add term rules to .claude/rules/
<!-- .claude/rules/terminology.md -->
Project terms are defined in docs/01-plan/glossary.md.
Always reference when using business terms.
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
| Level | Application Level |
|---|---|
| Starter | Simple (core terms only) |
| Dynamic | Detailed (all entities) |
| Enterprise | Detailed (per microservice) |
"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?"
See templates/pipeline/phase-1-schema.template.md
Phase 2: Coding Convention → Now that terms are defined, define code rules
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.