popup-studio-ai/phase-1-schema
skills/phase-1-schema/SKILL.md
Define project terminology, data structures, entities, and relationships. Triggers: schema, data model, entity, terminology, 스키마, 데이터 모델, 용어.
$ install --global
skillsauthnpx skillsauth add popup-studio-ai/bkit-claude-code phase-1-schemaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 7:25 AM197.4s1 file scanned
SKILL.md
- name:
- phase-1-schema
- context:
- fork
- classification:
- capability
- classification-reason:
- Pattern guidance may overlap with model's built-in knowledge as it improves
- deprecation-risk:
- medium
- effort:
- medium
- description:
- |
- Triggers:
- schema, data model, entity, terminology, 스키마, 데이터 모델, 용어.
- agent:
- bkit:pipeline-guide
- user-invocable:
- false
- 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
- 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
Related Skills
popup-studio-ai/sprint
testing
VerifiedTrustedCommunity
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
548SKILL.mdUpdated May 13, 2026
popup-studio-ai/cc-version-analysis
tools
VerifiedTrustedCommunity
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
545SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/rollback
testing
VerifiedTrustedCommunity
Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Rollback events are recorded via lib/audit/audit-logger ACTION_TYPES.rollback_executed. For sprint-level recovery, individual feature rollbacks may be triggered from within sprint phases (sprint itself is forward-only — terminal state is `archived`, not rolled back; v2.1.13). Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.
539SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/qa-phase
testing
VerifiedTrustedCommunity
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.
539SKILL.mdUpdated Apr 18, 2026