bkit-rules

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 |

Template References

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

---

Detection Order

1. Check CLAUDE.md for explicit Level declaration
2. File structure based detection

Enterprise (2+ conditions met)

• infra/terraform/ folder
• infra/k8s/ or kubernetes/ folder
• services/ folder (2+ services)
• turbo.json or pnpm-workspace.yaml
• docker-compose.yml
• .github/workflows/ (CI/CD)

Dynamic (1+ conditions met)

• bkend settings in .mcp.json
• lib/bkend/ or src/lib/bkend/
• supabase/ folder
• firebase.json

Starter

None of the above conditions met.

Level-specific Behavior

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

Level Upgrade Signals

• Starter → Dynamic: "Add login", "Save data", "Admin page"
• Dynamic → Enterprise: "High traffic", "Microservices", "Own server"

Hierarchical CLAUDE.md Rules

```

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

---

Level-Based Selection

When user requests feature development:

1. Detect project level
2. Invoke appropriate agent automatically

Task-Based Selection

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

Proactive Suggestions

After completing major tasks, suggest relevant agents.

Do NOT Auto-Invoke When

• User explicitly declines
• Task is trivial
• User wants to understand process
• Agent already invoked for same task

---

Pre-coding Checks

1. Does similar functionality exist? Search first
2. Check utils/, hooks/, components/ui/
3. Reuse if exists; create if not

Core Principles

DRY: Extract to common function on 2nd use

SRP: One function, one responsibility

No Hardcoding: Use meaningful constants

Extensibility: Write in generalized patterns

Self-Check After Coding

• Same logic exists elsewhere?
• Can function be reused?
• Hardcoded values present?
• Function does only one thing?

When to Refactor

• Same code appears 2nd time
• Function exceeds 20 lines
• if-else nests 3+ levels
• Same parameters passed to multiple functions

---

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 |

Classification Keywords

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