SkillsAdd

ww-w-ai/bkit-claude-code

phase-1-schema

Define project terminology, data structures, entities, and relationships.

First seen Jan 30, 2026

Installation

$ npx skills add ww-w-ai/bkit-claude-code --skill phase-1-schema
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

apify-generate-output-schema Similar name
apify/agent-skills

Generate output schemas (dataset_schema.json, output_schema.json, key_value_store_schema.json) …

7.4K installs
mongodb-schema-design Similar name
mongodb/agent-skills

MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing sch…

4.9K installs
graphql-schema Similar name
apollographql/skills

Guide for designing GraphQL schemas following industry best practices. Use this skill when: (1)…

3.4K installs
dms-schema-conversion Similar name
aws/agent-toolkit-for-aws

Handles the full DMS Schema Conversion lifecycle including creating migration projects, convert…

3.2K installs
schema-exploration Similar name
langchain-ai/deepagents

Lists tables, describes columns and data types, identifies foreign key relationships, and maps …

1.3K installs
planetscale-schema-recommendations-agent-loop Similar name
planetscale/skills

Safely triage PlanetScale schema recommendations and turn them into reviewed branches, migratio…

1.1K installs

Also in this package

Other skills from ww-w-ai/bkit-claude-code · top by installs.

npx skills add ww-w-ai/bkit-claude-code
desktop-app 221 mobile-app 111 claude-code-learning 102 phase-3-mockup 100 pdca 90 phase-5-design-system 76 code-review 70 btw 63 enterprise 56 bkit-rules 55

Browse all from ww-w-ai/bkit-claude-code

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 594
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Glob, Grep
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,269 B
  • docs SUMMARY.md 145 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 47 installs

SKILL.md

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 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