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

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

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

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

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

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

Review changed code for reuse, quality, and efficiency, then fix any issues found. Use after PDCA Check >= 90% or when code review is needed. Triggers: simplify, clean code, refactor, reduce complexity, 간소화, 코드 정리, リファクタリング, コード整理, 简化, 代码清理, simplificar, simplifier, vereinfachen, semplificare

Gemini CLI learning and education skill. Teaches users how to configure and optimize Gemini CLI settings. Start learning/setup with "learn" or "setup". Use proactively when user is new to Gemini CLI or asks about configuration. Triggers: learn gemini cli, gemini cli setup, GEMINI.md, hooks, commands, skills, how to configure, gemini cli learning, 제미나이 CLI 배우기, 설정 방법, Gemini CLI学習, 設定方法, 学习Gemini CLI, 配置方法, aprender gemini cli, configuración, apprendre gemini cli, configuration, Gemini CLI lernen, Konfiguration, imparare gemini cli, configurazione Do NOT use for: implementation tasks, debugging code

Query audit trail logs, decision traces, and session history for AI transparency. Provides searchable access to all bkit audit records via MCP tools. Use proactively when user wants to review past decisions, trace actions, or inspect logs. Triggers: audit, log, decision trace, audit trail, history, 감사, 로그, 결정 추적, 이력, 監査, ログ, 決定追跡, 履歴, 审计, 日志, 决策追踪, 历史, auditoría, registro, rastreo de decisiones, audit, journal, traçage des décisions, Audit, Protokoll, Entscheidungsverfolgung, audit, registro, tracciamento delle decisioni Do NOT use for: creating new audit entries (hooks do that automatically), modifying logs

Collect improvement suggestions during work. By-The-Way captures ideas, observations, and suggestions without interrupting the current workflow. Stores entries in .bkit/btw.json for later review and promotion. Use proactively when user says "btw", mentions a suggestion, improvement idea, or wants to note something for later. Triggers: btw, suggestion, improve, idea, feedback, note for later, by the way, 제안, 개선, 아이디어, 피드백, 참고로, 提案, 改善, アイデア, フィードバック, ちなみに, 建议, 改进, 想法, 反馈, 顺便说一下, sugerencia, mejora, idea, retroalimentación, amélioration, suggestion, idée, retour, Verbesserung, Vorschlag, Idee, Feedback, miglioramento, suggerimento, idea, feedback Do NOT use for: bug reports (use issues), task tracking (use PDCA)

Deployment guidance and checklist for dev, staging, and production environments. Creates a checkpoint before deploy and provides a structured pre-deploy checklist. Use proactively when user mentions deploying, releasing, or shipping to any environment. Triggers: deploy, release, ship, publish, go live, 배포, 릴리스, 출시, デプロイ, リリース, 公開, 部署, 发布, 上线, desplegar, lanzar, publicar, déployer, publier, mettre en production, bereitstellen, veröffentlichen, freigeben, distribuire, rilasciare, pubblicare Do NOT use for: development builds, local testing

Unified skill for managing the entire PDCA cycle. Supports Plan → Design → Do → Check → Act workflow with automatic phase progression. Use proactively when user mentions PDCA cycle, planning, design documents, gap analysis, iteration, or completion reports. Triggers: pdca, plan, design, analyze, check, report, status, next, iterate, 계획, 설계, 분석, 검증, 보고서, 반복, 개선, 計画, 設計, 分析, 検証, 報告, 反復, 计划, 设计, 分析, 验证, 报告, 迭代, planificar, diseño, analizar, verificar, informe, planifier, conception, analyser, vérifier, rapport, planen, Entwurf, analysieren, überprüfen, Bericht, pianificare, progettazione, analizzare, verificare, rapporto Do NOT use for: simple one-line fixes, non-development tasks

Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans. Use proactively when user asks to test, validate, or run QA on a feature. Triggers: qa, test, QA, quality assurance, run tests, test plan, 테스트, QA, 품질 보증, 검증, 테스트 실행, テスト, QA, 品質保証, テスト実行, 测试, QA, 质量保证, 运行测试, prueba, QA, aseguramiento de calidad, ejecutar pruebas, test, QA, assurance qualité, exécuter les tests, Test, QA, Qualitätssicherung, Tests ausführen, test, QA, garanzia di qualità, eseguire test Do NOT use for: unit test writing (just write them), production monitoring

Manage checkpoints and rollback for safe recovery. Create restore points before risky operations and restore to previous states when needed. Use proactively when user mentions rollback, undo, restore, checkpoint, or recovery. Triggers: rollback, checkpoint, restore, undo, revert, recovery, save point, 롤백, 체크포인트, 복원, 되돌리기, 복구, ロールバック, チェックポイント, 復元, 元に戻す, 回滚, 检查点, 恢复, 撤销, restaurar, punto de control, revertir, deshacer, restaurer, point de contrôle, annuler, revenir, Wiederherstellung, Prüfpunkt, rückgängig machen, ripristino, checkpoint, annullare, ripristinare Do NOT use for: git operations (use git directly), file editing

Create new project-local skills with proper directory structure and SKILL.md template. Generates a ready-to-use skill that Gemini CLI can activate immediately. Use proactively when user wants to create a new custom skill or slash command. Triggers: skill-create, new skill, create skill, add skill, custom skill, 스킬 생성, 새 스킬, 스킬 만들기, 커스텀 스킬, スキル作成, 新しいスキル, カスタムスキル, 创建技能, 新技能, 自定义技能, crear skill, nueva habilidad, habilidad personalizada, créer compétence, nouvelle compétence, compétence personnalisée, Skill erstellen, neuer Skill, benutzerdefinierter Skill, creare skill, nuova competenza, competenza personalizzata Do NOT use for: modifying existing skills, listing skills (use /skill-status)

Show loaded skills inventory with status, classification, and coverage information. Lists all skills from the skills/ directory with their activation state. Use proactively when user asks about available skills, loaded commands, or skill status. Triggers: skill-status, skill list, skills, available commands, loaded skills, show skills, 스킬 목록, 스킬 상태, 사용 가능한 스킬, 로드된 스킬, スキル一覧, スキル状態, 利用可能なスキル, 技能列表, 技能状态, 可用技能, lista de skills, estado de skills, habilidades disponibles, liste des compétences, état des compétences, compétences disponibles, Skill-Liste, Skill-Status, verfügbare Skills, lista delle skill, stato delle skill, skill disponibili Do NOT use for: creating skills (use /skill-create), modifying skills

bkend.ai security policies and encryption expert skill. Covers API key management (Public vs Secret), Row Level Security (RLS) with 4 roles (admin/user/guest/self), data encryption (Argon2id, AES-256-GCM, TLS 1.2+), and security best practices. Triggers: security, RLS, api key, encryption, RBAC, permissions, 보안, API 키, 암호화, 권한, 역할, 접근제어, セキュリティ, APIキー, 暗号化, 権限, ロール, 安全, API密钥, 加密, 权限, 角色, seguridad, clave API, cifrado, permisos, roles, securite, cle API, chiffrement, permissions, roles, Sicherheit, API-Schluessel, Verschluesselung, Berechtigungen, sicurezza, chiave API, crittografia, permessi, ruoli Do NOT use for: authentication flows (use bkend-auth), database operations (use bkend-data), infrastructure security (use security-architect agent)

bkend.ai authentication and security expert skill. Covers email signup/login, social login (Google, GitHub), magic link, JWT tokens (Access 1h, Refresh 30d), session management, RBAC (admin/user/self/guest), RLS policies, password management, and account lifecycle. Triggers: signup, login, JWT, session, social login, RBAC, RLS, password, token, 회원가입, 로그인, 토큰, 세션, 권한, 보안정책, 비밀번호, ログイン, 認証, セッション, 権限, パスワード, 登录, 认证, 会话, 权限, 密码, registro, inicio de sesion, permisos, contrasena, inscription, connexion, permissions, mot de passe, Registrierung, Anmeldung, Berechtigungen, Passwort, registrazione, accesso, permessi, password Do NOT use for: file storage (use bkend-storage), database queries (use bkend-data), MCP tool setup (use bkend-mcp)

bkend.ai practical project tutorials and troubleshooting guide. Covers 4 full-guide projects (blog, recipe-app, shopping-mall, social-network) with step-by-step implementation patterns including schema design, architecture patterns, and AI prompt collections. Triggers: cookbook, tutorial, example project, todo app, blog app, shopping mall, 쿡북, 튜토리얼, 예제, 블로그, 쇼핑몰, 투두, 프로젝트 만들기, クックブック, チュートリアル, 例題, ブログ, ショッピング, 食谱, 教程, 示例, 博客, 商城, libro de cocina, tutorial, ejemplo, blog, tienda, livre de recettes, tutoriel, exemple, blog, boutique, Kochbuch, Tutorial, Beispiel, Blog, Shop, ricettario, tutorial, esempio, blog, negozio Do NOT use for: authentication details (use bkend-auth), database specifics (use bkend-data), security policies (use bkend-security)

bkend.ai database expert skill. Covers table creation, CRUD operations, 7 column types, constraints, filtering (AND/OR, 10 operators), sorting, pagination, relations, joins, indexing, and schema management via MCP and REST API. Triggers: table, column, CRUD, schema, index, filter, query, data model, 테이블, 컬럼, 스키마, 인덱스, 필터, 쿼리, 데이터 모델, テーブル, カラム, スキーマ, インデックス, フィルター, 数据表, 列, 模式, 索引, 过滤, 查询, tabla, columna, esquema, indice, filtro, consulta, tableau, colonne, schema, index, filtre, requete, Tabelle, Spalte, Schema, Index, Filter, Abfrage, tabella, colonna, schema, indice, filtro, query Do NOT use for: authentication (use bkend-auth), file storage (use bkend-storage), MCP setup (use bkend-mcp), security policies (use bkend-security)

bkend.ai operational guides, troubleshooting, and platform comparison. Covers migration guides, performance optimization, testing strategy, common error solutions, and FAQ. Triggers: migration, troubleshoot, FAQ, performance, error handling, comparison, 마이그레이션, 문제해결, 자주 묻는 질문, 성능, 에러, マイグレーション, トラブルシューティング, FAQ, パフォーマンス, 迁移, 故障排除, 常见问题, 性能, 错误处理, migracion, solucion de problemas, preguntas frecuentes, rendimiento, migration, depannage, FAQ, performance, gestion des erreurs, Migration, Fehlerbehebung, FAQ, Leistung, Fehlerbehandlung, migrazione, risoluzione problemi, FAQ, prestazioni, gestione errori Do NOT use for: authentication implementation (use bkend-auth), database schema design (use bkend-data), security setup (use bkend-security)

bkend.ai MCP tools and AI integration expert skill. Covers 28 MCP tools (Fixed 3 + Project 6 + Table 9 + Data CRUD 5 + Env 3 + Schema 2), 4 MCP resources, OAuth 2.1 + PKCE authentication, and AI tool setup for Gemini CLI, Claude Code, and Cursor. Triggers: mcp, ai tool, mcp setup, backend tool, bkend mcp, MCP 설정, MCP 도구, AI 도구, MCP接続, MCP設定, AIツール, MCP连接, MCP设置, AI工具, herramientas MCP, configuracion MCP, outils MCP, configuration MCP, MCP-Werkzeuge, MCP-Einrichtung, strumenti MCP, configurazione MCP Do NOT use for: authentication implementation (use bkend-auth), database queries (use bkend-data), file storage (use bkend-storage)

bkend.ai platform onboarding and core concepts guide. Covers MCP setup, resource hierarchy (Org->Project->Environment), Tenant vs User model, and first project creation. Use proactively when user is new to bkend or asks about initial setup. Triggers: bkend setup, first project, bkend start, MCP connect, bkend 시작, 처음, 설정, MCP 연결, 프로젝트 생성, bkend始め方, 初期設定, MCP接続, bkend入门, 初始设置, MCP连接, configuracion bkend, primer proyecto, configuration bkend, premier projet, bkend Einrichtung, erstes Projekt, configurazione bkend, primo progetto Do NOT use for: advanced auth flows (use bkend-auth), database queries (use bkend-data), file storage (use bkend-storage), security policies (use bkend-security)

bkend.ai file storage expert skill. Covers single/multiple/multipart file upload via Presigned URL, file download (CDN vs Presigned), 4 visibility levels (public/private/protected/shared), bucket management, and file metadata. Triggers: file upload, download, presigned, bucket, storage, CDN, image, 파일 업로드, 다운로드, 버킷, 스토리지, 이미지, ファイルアップロード, ダウンロード, バケット, ストレージ, 文件上传, 下载, 存储桶, 存储, carga de archivos, descarga, almacenamiento, cubo, telechargement, televersement, stockage, seau, Datei-Upload, Download, Speicher, Bucket, caricamento file, download, archiviazione, bucket Do NOT use for: authentication (use bkend-auth), database queries (use bkend-data), MCP setup (use bkend-mcp)

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

PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates. Use proactively when generating PDCA documents. Triggers: template, plan document, design document, analysis document, report, 템플릿, 계획서, 설계서, 분석서, 보고서, テンプレート, 計画書, 設計書, 模板, 计划书, 设计书, plantilla, documento de plan, modèle, document de plan, Vorlage, Plandokument, modello, documento di piano Do NOT use for: code implementation, debugging

Code review skill for analyzing code quality, detecting bugs, and ensuring best practices. Use proactively when user requests code review, quality check, or bug detection. Triggers: code review, review code, check code, analyze code, bug detection, 코드 리뷰, 코드 검토, 버그 검사, コードレビュー, バグ検出, 代码审查, 代码检查, revisión de código, detección de errores, revue de code, détection de bugs, Code-Review, Fehlererkennung, revisione del codice, rilevamento bug Do NOT use for: design document creation, deployment tasks

Desktop app development guide for cross-platform applications. Covers Electron and Tauri frameworks. Use proactively when user wants to build desktop applications. Triggers: desktop app, Electron, Tauri, mac app, windows app, 데스크톱 앱, 데스크탑 앱, デスクトップアプリ, デスクトップ, 桌面应用, 桌面程序, aplicación de escritorio, app de escritorio, application de bureau, app desktop, Desktop-Anwendung, Desktop-App, applicazione desktop, app desktop Do NOT use for: web-only projects, mobile apps

9-phase Development Pipeline complete knowledge. Use when user doesn't know development order or starts a new project. Triggers: development pipeline, phase, development order, where to start, what to do first, how to begin, new project, 개발 파이프라인, 뭐부터, 어디서부터, 순서, 시작, 開発パイプライン, 何から, どこから, 开发流程, 从哪里开始, pipeline de desarrollo, por dónde empezar, pipeline de développement, par où commencer, Entwicklungs-Pipeline, wo anfangen, pipeline di sviluppo, da dove iniziare Do NOT use for: ongoing implementation, bug fixes

Fullstack development skill using bkend.ai BaaS platform. Covers authentication, data storage, API integration for dynamic web apps. Project initialization with "init dynamic" or "dynamic init". Use proactively when user needs login, database, or backend features. Triggers: fullstack, BaaS, bkend, authentication, login feature, signup, database, web app, SaaS, MVP, init dynamic, dynamic init, 풀스택, 인증, 로그인 기능, 회원가입, 데이터베이스, 웹앱, フルスタック, 認証, ログイン機能, データベース, 全栈, 身份验证, 登录功能, 数据库, autenticación, inicio de sesión, registro, base de datos, fullstack, authentification, connexion, inscription, base de données, fullstack, Authentifizierung, Anmeldung, Registrierung, Datenbank, Fullstack, autenticazione, accesso, registrazione, database, fullstack Do NOT use for: static websites, microservices architecture

Enterprise-grade system development with microservices, Kubernetes, and Terraform. Includes AI Native methodology and Monorepo architecture patterns. Project initialization with "init enterprise" or "enterprise init". Use proactively when user needs high traffic, microservices, or custom infrastructure. Triggers: microservices, kubernetes, terraform, k8s, AWS, monorepo, AI native, init enterprise, enterprise init, 마이크로서비스, 모노레포, 인프라, マイクロサービス, モノレポ, インフラ, 微服务, 单仓库, 基础设施, microservicios, estrategia empresarial, arquitectura, microservices, stratégie d'entreprise, architecture, Microservices, Unternehmensstrategie, Architektur, microservizi, strategia aziendale, architettura Do NOT use for: simple projects, static websites, learning projects

Mobile app development guide for cross-platform apps. Covers React Native, Flutter, and Expo frameworks. Use proactively when user wants to build mobile apps. Triggers: mobile app, React Native, Flutter, Expo, iOS, Android, 모바일 앱, 앱 개발, モバイルアプリ, アプリ開発, 移动应用, 手机应用, aplicación móvil, app móvil, application mobile, app mobile, mobile Anwendung, mobile App, applicazione mobile, app mobile Do NOT use for: web-only projects, desktop apps

Skill for defining terminology and data structures. Covers domain terminology, entities, relationships, and schema design. Use proactively when starting a new project or when data structures are unclear. Triggers: schema, terminology, data model, entity, 스키마, 용어, 데이터 모델, スキーマ, 用語, データモデル, 模式, 术语, 数据模型, esquema, terminología, modelo de datos, schéma, terminologie, modèle de données, Schema, Terminologie, Datenmodell, schema, terminologia, modello dati Do NOT use for: UI-only changes, deployment

Skill for defining coding rules and conventions. Ensures consistent code style and specifies coding standards. Use proactively when starting a new project or when coding standards are needed. Triggers: convention, coding style, naming rules, 컨벤션, 코딩 스타일, 네이밍 규칙, コンベンション, コーディングスタイル, 编码风格, 命名规则, convención, estilo de código, convention, style de codage, Konvention, Coding-Stil, convenzione, stile di codice Do NOT use for: existing projects with established conventions

Skill for creating mockups with UI/UX trends. Designs HTML/CSS/JS prototypes before implementation. Use proactively when user wants to validate UI/UX before coding. Triggers: mockup, prototype, wireframe, UI design, 목업, 프로토타입, 와이어프레임, モックアップ, プロトタイプ, 原型, 线框图, maqueta, prototipo, maquette, prototype, Mockup, Prototyp, mockup, prototipo Do NOT use for: production code, API development

Skill for designing and implementing backend APIs. Includes Zero Script QA methodology for API validation. Use proactively when user needs to design or implement backend APIs. Triggers: API design, REST API, backend, endpoint, API 설계, 백엔드, 엔드포인트, API設計, バックエンド, API设计, 后端, diseño de API, backend, conception API, backend, API-Design, Backend, progettazione API, backend Do NOT use for: frontend-only projects, Starter level

Skill for building platform-independent design systems. Develops consistent component libraries for all UI frameworks. Use proactively when user needs consistent UI components. Triggers: design system, component library, design tokens, 디자인 시스템, 컴포넌트 라이브러리, デザインシステム, コンポーネントライブラリ, 设计系统, 组件库, sistema de diseño, biblioteca de componentes, système de design, bibliothèque de composants, Design-System, Komponentenbibliothek, sistema di design, libreria di componenti Do NOT use for: one-off UI changes, Starter level

Skill for implementing UI and integrating with APIs. Covers frontend-backend integration and state management. Use proactively when user needs to connect frontend with backend. Triggers: UI implementation, API integration, state management, UI 구현, API 연동, 상태 관리, UI実装, API連携, 状態管理, UI实现, API集成, 状态管理, implementación UI, integración API, implémentation UI, intégration API, UI-Implementierung, API-Integration, implementazione UI, integrazione API Do NOT use for: mockup creation, backend-only development

Skill for search optimization (SEO) and security hardening. Covers meta tags, semantic HTML, and security vulnerability checks. Use proactively when user asks about search ranking or security. Triggers: SEO, security, meta tags, XSS, CSRF, 보안, 검색 최적화, セキュリティ, SEO, 安全, 搜索优化, seguridad, SEO, sécurité, SEO, Sicherheit, SEO, sicurezza, SEO Do NOT use for: backend-only APIs, internal tools

Skill for verifying codebase quality and gap analysis. Covers architecture consistency and convention compliance. Use proactively when implementation is complete and quality verification is needed. Triggers: code review, architecture review, quality check, gap analysis, 코드 리뷰, 설계-구현 분석, コードレビュー, ギャップ分析, 代码审查, 差距分析, revisión de código, análisis de brechas, revue de code, analyse des écarts, Code-Review, Gap-Analyse, revisione del codice, analisi del divario Do NOT use for: initial planning, design creation