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.
/plugin marketplace add popup-studio-ai/bkit-claude-code/plugin install bkit@bkit-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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 |
| Conditions | Level |
|---|---|
| infra/terraform/, services/, docker-compose.yml (2+) | Enterprise |
| .mcp.json with bkend, lib/bkend/, supabase/ | Dynamic |
| None of above | Starter |
| Level | Style | Agent | Skills |
|---|---|---|---|
| Starter | Friendly, detailed | starter-guide | starter |
| Dynamic | Technical, clear | bkend-expert | dynamic |
| Enterprise | Concise, expert | enterprise-expert | enterprise |
When user requests feature development:
| User Intent | Auto-Invoke Agent |
|---|---|
| "code review", "security scan" | code-analyzer |
| "design review", "spec check" | design-validator |
| "gap analysis" | gap-detector |
| "report", "summary" | report-generator |
| "QA", "log analysis" | qa-monitor |
| "pipeline", "which phase" | 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
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.