From bkit
Core rules for bkit plugin. PDCA methodology, level detection, agent auto-triggering, and code quality standards. These rules are automatically applied to ensure consistent AI-native development. Use proactively when user requests feature development, code changes, or implementation tasks. Triggers: bkit, PDCA, develop, implement, feature, bug, code, design, document, 개발, 기능, 버그, 코드, 설계, 문서, 開発, 機能, バグ, 开发, 功能, 代码, desarrollar, función, error, código, diseño, documento, développer, fonctionnalité, bogue, code, conception, document, entwickeln, Funktion, Fehler, Code, Design, Dokument, sviluppare, funzionalità, bug, codice, design, documento Do NOT use for: documentation-only tasks, research, or exploration without code changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bkit:bkit-rulesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Automatically applied rules that don't require user commands.
Automatically applied rules that don't require user commands.
No Guessing: If unsure, check docs → If not in docs, ask user SoR Priority: Code > CLAUDE.md > docs/ design documents
| Request Type | Claude Behavior |
|---|---|
| New feature | Check docs/02-design/ → Design first if missing |
| Bug fix | Compare code + design → Fix |
| Refactoring | Current analysis → Plan → Update design → Execute |
| Implementation complete | Suggest Gap analysis |
| Document Type | Template Path |
|---|---|
| Plan | ${CLAUDE_PLUGIN_ROOT}/templates/plan.template.md |
| Design | ${CLAUDE_PLUGIN_ROOT}/templates/design.template.md |
| Analysis | ${CLAUDE_PLUGIN_ROOT}/templates/analysis.template.md |
| Report | ${CLAUDE_PLUGIN_ROOT}/templates/report.template.md |
None of the above conditions met.
| Aspect | Starter | Dynamic | Enterprise |
|---|---|---|---|
| Explanation | Friendly, avoid jargon | Technical but clear | Concise, use terms |
| Code comments | Detailed | Core logic only | Architecture only |
| Error handling | Step-by-step guide | Technical solutions | Brief cause + fix |
| PDCA docs | Simple | Feature-specific | Detailed architecture |
| Primary Agent | starter-guide | bkend-expert | enterprise-expert |
| Reference Skill | starter | dynamic | enterprise |
project/
├── CLAUDE.md # Project-wide (always reference)
├── services/CLAUDE.md # Backend work context
├── frontend/CLAUDE.md # Frontend work context
└── infra/CLAUDE.md # Infrastructure context
Rule: Area-specific rules > Project-wide rules
When user requests feature development:
| User Intent | Auto-Invoke Agent |
|---|---|
| "code review", "security scan" | bkit:code-analyzer |
| "design review", "spec check" | bkit:design-validator |
| "gap analysis" | bkit:gap-detector |
| "report", "summary" | bkit:report-generator |
| "QA", "log analysis" | bkit:qa-monitor |
| "pipeline", "which phase" | bkit:pipeline-guide |
After completing major tasks, suggest relevant agents.
DRY: Extract to common function on 2nd use SRP: One function, one responsibility No Hardcoding: Use meaningful constants Extensibility: Write in generalized patterns
Classify tasks to apply appropriate PDCA level:
| Classification | Content Size | PDCA Level | Action |
|---|---|---|---|
| Quick Fix | < 50 chars | None | Execute immediately |
| Minor Change | 50-200 chars | Lite | Show summary, proceed |
| Feature | 200-1000 chars | Standard | Check/create design doc |
| Major Feature | > 1000 chars | Strict | Require design, user confirmation |
Quick Fix: fix, typo, correct, adjust, tweak Minor Change: improve, refactor, enhance, optimize, update Feature: add, create, implement, build, new feature Major Feature: redesign, migrate, architecture, overhaul, rewrite
npx claudepluginhub humanintheloo/bkit-claude-codeGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.