phase-1-schema
Unifies project language and data models to reduce onboarding time and improve AI context awareness.
Install
mkdir -p .claude/skills/phase-1-schema && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15099" && unzip -o skill.zip -d .claude/skills/phase-1-schema && rm skill.zipInstalls to .claude/skills/phase-1-schema
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Skill for defining terminology and data structures used throughout the project. Covers domain terminology, entities, relationships, and schema design. Use proactively when starting a new project or when data structures are unclear. Triggers: schema, terminology, data model, entity, 스키마, 用語, データモデル, 数据模型, esquema, terminología, modelo de datos, schéma, terminologie, modèle de données, Schema, Terminologie, Datenmodell, schema, terminologia, modello dati Do NOT use for: UI-only changes, deployment, or when schema is already defined.Key capabilities
- →Build a project glossary by mapping business terms and global standards
- →Identify core entities within the project domain
- →Define relationships between identified entities
- →Design data schemas for project data structures
- →Set up Claude Code to automatically reference the project glossary
- →Generate deliverables such as glossary.md and schema.md
How it works
The skill guides through building a glossary, identifying entities, defining relationships, and designing schemas to unify project language and ensure consistent data structures.
Inputs & outputs
When to use phase-1-schema
- →Creating a domain glossary for a new project
- →Mapping business terms to technical entities
- →Standardizing data schema before implementation
About this skill
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
- Build Glossary: Map business terms + global standards
- Identify Entities: Determine what "things" exist
- Define Relationships: Relationships between entities
- Design Schema: Define data structures
Glossary
Why is it Needed?
Explaining business terms to Claude Code every time is tedious. Creating a glossary allows:
- Claude 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
## 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`)
Claude Code Auto-Reference Setup
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 project CLAUDE.md
<!-- Add to CLAUDE.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
When not to use it
- →When making UI-only changes
- →When deploying the project
- →When the schema is already defined and clear
Limitations
- →Not applicable for UI-only changes
- →Not applicable for deployment tasks
- →Not applicable when the schema is already defined
How it compares
This skill provides a structured, phased approach to defining project terminology and data structures, including templates and setup for AI auto-referencing, which is more guided than ad-hoc documentation.
Compared to similar skills
phase-1-schema side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| phase-1-schema (this skill) | 0 | 5mo | No flags | Beginner |
| dotnet-architect | 12 | 4mo | No flags | Advanced |
| add-module | 1 | 1mo | Review | Advanced |
| go-pro-max | 0 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
dotnet-architect
sickn33
Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.
add-module
fullstackhero
Create a new module (bounded context) with proper project structure, permissions, DbContext, and registration. Use when adding a new business domain that needs its own entities and endpoints.
go-pro-max
vurakit
Go development intelligence. 12 domains, 10 stacks, 300+ entries. Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check Go code. Domains: pattern, package, error, perf, test, concurrency, interface, arch, idiom, anti, tooling, module. Stacks: web-g
domain-model-documentation
DABO-ERP
Use this skill when building or reviewing the domain model for the hotel/hostel management system. This includes defining entities, attributes, relationships, and enumerations based on hospitality domain expertise.
agent-pseudocode
ruvnet
Agent skill for pseudocode - invoke with $agent-pseudocode
app
jhenriquedev
use when setting up APP projects, adding host apps, creating or updating Cases, introducing packages, classifying shared code across cases/packages/core/shared, maintaining case .us.md artifacts, validating APP grammar, reviewing structural drift, and adapting existing projects incrementally with th