PDCA methodology + Claude Code mastery for AI-native development
bkit is a Claude Code plugin that transforms how you build software with AI. It provides structured development workflows, automatic documentation, and intelligent code assistance through the PDCA (Plan-Do-Check-Act) methodology.
- PDCA Methodology - Structured development workflow with automatic documentation
- Evaluator-Optimizer Pattern - Automatic iteration cycles from Anthropic's agent architecture
- 9-Stage Development Pipeline - From schema design to deployment
- 3 Project Levels - Starter (static), Dynamic (fullstack), Enterprise (microservices)
- Multilingual Support - 8 languages (EN, KO, JA, ZH, ES, FR, DE, IT)
- 18 Commands - Automate common development tasks
- 18 Skills - Domain-specific knowledge for various development scenarios
- 11 Agents - Specialized AI assistants for different tasks
- Skills Frontmatter Hooks - Automatic triggers based on context (v1.2.0+)
Claude Code가 처음이신가요?
bkit-starter로 시작하세요!
- 완전한 한글 가이드
- 프로그래밍 경험 없이도 시작 가능
- 첫 프로젝트 만들기 체험
/plugin enable bkit-starterbkit은 bkit-starter를 마스터한 후 사용하는 고급 확장 버전입니다.
The easiest way to install bkit is through the Claude Code marketplace.
# Step 1: Add bkit marketplace
/plugin marketplace add popup-studio-ai/bkit-claude-code
# Step 2: Install bkit plugin
/plugin install bkitUse /plugin command and navigate to Marketplaces tab to manage your plugin sources:
- bkit-marketplace: Contains bkit and bkit-starter plugins
- claude-plugins-official: Official Anthropic plugins
Navigate to Discover tab to browse and install available plugins:
| Plugin | Description | Best For |
|---|---|---|
| bkit | Full PDCA methodology + Claude Code mastery | Experienced developers |
| bkit-starter | Korean learning guide for beginners | First-time Claude Code users |
Keep your plugins up-to-date automatically by configuring auto-update in your settings:
// ~/.claude/settings.json
{
"plugins": {
"autoUpdate": true
}
}Update Commands:
- Press
uin the Marketplaces view to update all plugins - Press
rto remove a marketplace - Use
Spaceto toggle plugin selection in Discover view
bkit-claude-code/
├── .claude-plugin/
│ ├── plugin.json # Plugin manifest
│ └── marketplace.json # Marketplace registry
├── commands/ # Slash commands
├── agents/ # Specialized AI agents
├── skills/ # Domain knowledge
├── hooks/ # Event hooks (hooks.json)
├── scripts/ # Hook scripts
├── lib/ # Shared utilities
├── templates/ # Document templates
└── bkit.config.json # Centralized configuration
Note: The
.claude/folder is not included in this repository. Plugin elements are located at the root level.
After installing bkit via the marketplace, you can customize any component by copying it to your project's .claude/ folder.
Comprehensive Guide: See CUSTOMIZATION-GUIDE.md for detailed instructions on customizing bkit for your organization, including platform-specific paths, component examples, and license attribution requirements.
Claude Code searches for configuration files in this priority order:
- Project
.claude/(highest priority - your customizations) - User
~/.claude/ - Plugin installation (default)
# Step 1: Find the plugin installation location
ls ~/.claude/plugins/bkit/
# Step 2: Copy only the files you want to customize
mkdir -p .claude/skills/starter
cp ~/.claude/plugins/bkit/skills/starter/SKILL.md .claude/skills/starter/
# Step 3: Edit the copied file in your project
# Your project's .claude/skills/starter/SKILL.md will override the plugin's version
# Step 4: Commit to version control (optional)
git add .claude/
git commit -m "feat: customize bkit starter skill"| Component | Location | Description |
|---|---|---|
| Commands | ~/.claude/plugins/bkit/commands/ |
Slash commands (e.g., /pdca-plan) |
| Skills | ~/.claude/plugins/bkit/skills/ |
Domain knowledge and context |
| Agents | ~/.claude/plugins/bkit/agents/ |
Specialized AI assistants |
| Templates | ~/.claude/plugins/bkit/templates/ |
Document templates |
| Scripts | ~/.claude/plugins/bkit/scripts/ |
Hook scripts |
| Config | ~/.claude/plugins/bkit/bkit.config.json |
Central configuration |
- Customized files don't receive plugin updates. When bkit is updated, your customized files remain unchanged while non-customized files are updated automatically.
- Check the CHANGELOG periodically for updates that might affect your customizations.
- Delete a customized file to revert to the plugin's default version.
- Attribution required: When creating derivative plugins, follow the License & Attribution guidelines.
/bkit:learn-claude-code/bkit:init-starter # Static website
/bkit:init-dynamic # Fullstack with BaaS
/bkit:init-enterprise # Microservices with K8s/bkit:pdca-plan {feature} # Create plan document
/bkit:pdca-design {feature} # Create design document
/bkit:pdca-iterate {feature} # Auto-fix with Evaluator-Optimizer pattern
/bkit:pdca-analyze # Run gap analysis
/bkit:pdca-report # Generate completion report| Level | Description | Stack |
|---|---|---|
| Starter | Static websites, portfolios | HTML, CSS, JS |
| Dynamic | Fullstack applications | Next.js, BaaS |
| Enterprise | Microservices architecture | K8s, Terraform, MSA |
bkit is primarily designed for software development. However, some components can inspire structured workflows beyond coding:
| Component | Beyond Development Uses |
|---|---|
| PDCA Methodology | Project management, process improvement |
| Document Templates | Planning any structured project |
| Gap Analysis | Comparing any plan vs. actual outcome |
Note: For general writing, research, or non-technical tasks, plain Claude Code (without bkit) is better suited.
- CUSTOMIZATION-GUIDE.md - Complete guide to customizing bkit for your organization
- Platform-specific configuration paths (macOS, Linux, Windows, WSL)
- Component customization (agents, skills, commands, hooks, templates)
- License attribution requirements for derivative works
- bkit design philosophy and architecture decisions
- System Architecture - Plugin structure and trigger system overview
- Core Mission & Philosophy - 3 core philosophies (Automation First, No Guessing, Docs=Code)
- AI-Native Principles - AI-Native development and 3 core competencies
- PDCA Methodology - PDCA cycle and 9-stage pipeline relationship
- Graph Index - Obsidian-optimized component graph
- Development Pipeline - 9-stage pipeline skill
- Commands Reference - 18 slash commands
- Skills Reference - 18 domain skills
- Agents Reference - 11 specialized agents
- Active PDCA - Current plan/design/analysis documents
- Archive - Completed PDCA + legacy documents
- Changelog - Version history and release notes
The bkit-system/ documentation is optimized for Obsidian's Graph View:
- Open
bkit-system/as an Obsidian vault - Press
Ctrl/Cmd + Gto open Graph View - Explore component relationships visually
See bkit-system/README.md for detailed instructions.
bkit automatically detects your language from trigger keywords:
| Language | Trigger Keywords |
|---|---|
| English | static website, beginner, API design |
| Korean | 정적 웹, 초보자, API 설계 |
| Japanese | 静的サイト, 初心者, API設計 |
| Chinese | 静态网站, 初学者, API设计 |
| Spanish | sitio web estático, principiante |
| French | site web statique, débutant |
| German | statische Webseite, Anfänger |
| Italian | sito web statico, principiante |
To set Claude's response language, add to ~/.claude/settings.json:
{
"language": "korean"
}| Language | Setting Value |
|---|---|
| Korean | "language": "korean" |
| Japanese | "language": "japanese" |
| Chinese | "language": "chinese" |
| English | "language": "english" (default) |
Note: Trigger keywords work in any language. The
languagesetting only affects Claude's response language.
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
- Only
adminteam members can merge tomain - All changes require pull request review
- Version releases are managed through Git tags
Copyright 2024-2026 POPUP STUDIO PTE. LTD.
Licensed under the Apache License, Version 2.0. See LICENSE for details.
You must include the NOTICE file in any redistribution.
- Issues: GitHub Issues
- Email: contact@popupstudio.ai
Made with AI by POPUP STUDIO