원클릭으로 Manus에서 모든 스킬 실행

bkit-rules

스타64

포크14

업데이트2026년 3월 11일 04:41

Core rules for bkit plugin. PDCA methodology, level detection, agent auto-triggering, and code quality standards. Use proactively when user requests feature development or code changes. Triggers: bkit, PDCA, develop, implement, feature, bug, code, design, document, 개발, 기능, 버그, 코드, 설계, 문서, 開発, 機能, バグ, 开发, 功能, 代码, desarrollar, función, código, développer, fonctionnalité, code, entwickeln, Funktion, Code, sviluppare, funzionalità, codice Do NOT use for: general conversation, non-development tasks

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

popup-studio-ai

popup-studio-ai/bkit-gemini

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

bkit Core Rules

Rules that govern bkit behavior and PDCA methodology

Rule 1: PDCA First

For any feature request:

Check if Plan document exists
Check if Design document exists
If missing, suggest creating them first
Track phase in .pdca-status.json

Rule 2: Level Detection

Automatically detect project level:

Indicator	Level
kubernetes/, terraform/	Enterprise
api/, backend/, .mcp.json	Dynamic
Default	Starter

Rule 3: Task Classification

Lines Changed	Classification	PDCA Level
< 30	Trivial	None
30-100	Quick Fix	None
100-500	Minor Change	Light
500-1000	Feature	Standard
> 1000	Major Feature	Full

Rule 4: Agent Auto-Trigger

User Intent	Agent
Verify, check	gap-detector
Improve, iterate	pdca-iterator
Analyze, quality	code-analyzer
Report, summary	report-generator
Help, guide	starter-guide

Rule 5: Check-Act Loop

When gap analysis < 90%:

Auto-trigger pdca-iterator
Apply fixes
Re-run gap analysis
Repeat until >= 90% or max 5 iterations

Rule 6: Feature Usage Report

Include at end of every response:

─────────────────────────────────────────────────
📊 bkit Feature Usage
─────────────────────────────────────────────────
✅ Used: [features used]
⏭️ Not Used: [features not used] (reason)
💡 Recommended: [next recommended feature]
─────────────────────────────────────────────────

Rule 7: Multi-Language Support

Support 8 languages for triggers:

English (en)
Korean (ko)
Japanese (ja)
Chinese (zh)
Spanish (es)
French (fr)
German (de)
Italian (it)

Rule 8: Quality Standards

Never skip PDCA for features > 500 LOC
Always suggest gap analysis after implementation
Encourage design-first development
Track all phase transitions in history

이 저장소의 다른 Skills

같은 저장소

control

popup-studio-ai/bkit-gemini

View and change bkit automation settings. Shows current automation level, feature flags, trust score, and guardrail configuration. Use proactively when user asks about automation settings, trust level, or guardrails. Triggers: control, automation, settings, level, guardrail, trust, 제어, 자동화, 설정, 레벨, 가드레일, 신뢰도, 制御, 自動化, 設定, レベル, ガードレール, 控制, 自动化, 设置, 级别, 护栏, control, automatización, configuración, nivel, contrôle, automatisation, paramètres, niveau, Kontrolle, Automatisierung, Einstellungen, Stufe, controllo, automazione, impostazioni, livello Do NOT use for: deployment (use /deploy), code changes

2026-05-1564

batch

popup-studio-ai/bkit-gemini

Process multiple features or tasks in parallel. Batch execution of PDCA commands across features. Triggers: batch, parallel, bulk, multiple features, 배치, 병렬, 대량 처리, バッチ, 並列, 一括処理, 批量, 并行, 批处理, lote, paralelo, procesamiento masivo, lot, parallèle, traitement en masse, Stapel, parallel, Massenverarbeitung, batch, parallelo, elaborazione di massa

2026-05-1464

loop

popup-studio-ai/bkit-gemini

Run a prompt or command on a recurring interval. Useful for monitoring, polling, or periodic checks. Triggers: loop, recurring, interval, monitor, poll, cron, 반복, 주기적, 모니터링, ループ, 定期的, 監視, 循环, 定期, 监控, bucle, intervalo, monitorear, boucle, intervalle, surveiller, Schleife, Intervall, überwachen, ciclo, intervallo, monitorare

2026-05-1464

output-style-setup

popup-studio-ai/bkit-gemini

Install bkit output styles to your project or user directory. Copies output style files from bkit plugin to the appropriate location. Triggers: output style setup, install output style, setup style, 아웃풋 스타일 설치, 스타일 설정, 出力スタイル設定, スタイルインストール, 输出样式安装, 样式设置, instalar estilo, configurar estilo, installer le style, configurer le style, Stil installieren, Stil einrichten, installare stile, configurare stile

2026-05-1464

plan-plus

popup-studio-ai/bkit-gemini

Plan Plus — Brainstorming-Enhanced PDCA Planning. Combines intent discovery from brainstorming methodology with PDCA's structured planning. Produces higher-quality Plan documents by exploring user intent, comparing alternatives, and validating incrementally. Triggers: plan-plus, brainstorm plan, enhanced plan, deep plan, 플랜플러스, 브레인스토밍, 심층 기획, プランプラス, ブレインストーミング, 深度计划, 头脑风暴, plan plus, planificación avanzada, plan plus, planification avancée, Plan Plus, erweiterte Planung, plan plus, pianificazione avanzata

2026-05-1464

pm-discovery

popup-studio-ai/bkit-gemini

PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase. Triggers: pm team, product discovery, PM analysis, PM 분석, 제품 기획, PMチーム, PM分析, 产品分析, PM-Analyse, PM análisis, analyse PM, analisi PM

2026-05-1464

name	bkit-rules
classification	C
description	Core rules for bkit plugin. PDCA methodology, level detection, agent auto-triggering, and code quality standards. Use proactively when user requests feature development or code changes. Triggers: bkit, PDCA, develop, implement, feature, bug, code, design, document, 개발, 기능, 버그, 코드, 설계, 문서, 開発, 機能, バグ, 开发, 功能, 代码, desarrollar, función, código, développer, fonctionnalité, code, entwickeln, Funktion, Code, sviluppare, funzionalità, codice Do NOT use for: general conversation, non-development tasks
user-invocable	false
argument-hint
allowed-tools	["read_file","glob","grep_search"]
imports	[]
agents	{}
context	project
memory	project
pdca-phase	all

bkit Core Rules

Rules that govern bkit behavior and PDCA methodology

Rule 1: PDCA First

For any feature request:

Check if Plan document exists
Check if Design document exists
If missing, suggest creating them first
Track phase in .pdca-status.json

Rule 2: Level Detection

Automatically detect project level:

Indicator	Level
kubernetes/, terraform/	Enterprise
api/, backend/, .mcp.json	Dynamic
Default	Starter

Rule 3: Task Classification

Lines Changed	Classification	PDCA Level
< 30	Trivial	None
30-100	Quick Fix	None
100-500	Minor Change	Light
500-1000	Feature	Standard
> 1000	Major Feature	Full

Rule 4: Agent Auto-Trigger

User Intent	Agent
Verify, check	gap-detector
Improve, iterate	pdca-iterator
Analyze, quality	code-analyzer
Report, summary	report-generator
Help, guide	starter-guide

Rule 5: Check-Act Loop

When gap analysis < 90%:

Auto-trigger pdca-iterator
Apply fixes
Re-run gap analysis
Repeat until >= 90% or max 5 iterations

Rule 6: Feature Usage Report

Include at end of every response:

─────────────────────────────────────────────────
📊 bkit Feature Usage
─────────────────────────────────────────────────
✅ Used: [features used]
⏭️ Not Used: [features not used] (reason)
💡 Recommended: [next recommended feature]
─────────────────────────────────────────────────

Rule 7: Multi-Language Support

Support 8 languages for triggers:

English (en)
Korean (ko)
Japanese (ja)
Chinese (zh)
Spanish (es)
French (fr)
German (de)
Italian (it)

Rule 8: Quality Standards

Never skip PDCA for features > 500 LOC
Always suggest gap analysis after implementation
Encourage design-first development
Track all phase transitions in history