Development

Skill for creating mockups with UI/UX trends without a designer. Designs HTML/CSS/JS prototypes that can be converted to Next.js components. Use proactively when user wants to validate UI/UX before implementation. Triggers: mockup, prototype, wireframe, UI design, 목업, モックアップ, 原型, maqueta, prototipo, diseño UI, maquette, prototype, conception UI, Mockup, Prototyp, UI-Design, mockup, prototipo, design UI Do NOT use for: production code, API development, or existing component modifications.

Skill for defining coding rules and conventions. Ensures consistent code style and specifies coding standards for AI collaboration. 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, reglas de nombrado, convention, style de codage, règles de nommage, Konvention, Coding-Stil, Namensregeln, convenzione, stile di codice, regole di denominazione Do NOT use for: exis...

Mobile app development guide for cross-platform apps. Covers React Native, Flutter, and Expo frameworks. Use proactively when user wants to build mobile apps or convert web apps to mobile. Triggers: mobile app, React Native, Flutter, Expo, iOS, Android, 모바일 앱, モバイルアプリ, 移动应用, aplicación móvil, app móvil, desarrollo móvil, application mobile, développement mobile, mobile Anwendung, mobile App, mobile Entwicklung, applicazione mobile, app mobile, sviluppo mobile Do NOT use for: web-only proje...

Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. For multi-feature initiatives spanning a release timeline, combine with /sprint master-plan (v2.1.13) to group features into a single 8-phase sprint container with shared scope/budget and 4 auto-pause triggers (QUALITY_GATE_FAIL / ITERATION_EXHAUSTED / BUDGET_EXCEEDED / PHASE_TIMEOUT). Triggers: microservices, k8s, terraform, monorepo, AI native

Fullstack development with bkend.ai BaaS — authentication, database, API integration. Triggers: fullstack, BaaS, login, signup, database, web app

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

Tech spec knowledge base. Full workflow from requirement analysis, code research to spec output.

Security review via Codex exec. Use when: OWASP Top 10:2025 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.

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. Use proactively when user requests feature development, code changes, or implementation tasks. Triggers: bkit, PDCA, develop, implement, feature, bug, code, design, document, 개발, 기능, 버그, 코드, 설계, 문서, 開発, 機能, バグ, 开发, 功能, 代码, desarrollar, función, error, código, diseño, documento, développer, fonction...

Request tracking knowledge base. Covers request structure, status tracking, document references, progress management.

bkend.ai onboarding — MCP setup, resource hierarchy, tenant/user model, first project. Triggers: bkend quickstart, bkend onboarding, bkend setup, bkend MCP

Project initialization inventory and cache generation (one-time intake). Use when first onboarding a project or after major structural changes.

bkend.ai project tutorials (todo to SaaS) and common error troubleshooting. Triggers: bkend tutorial, bkend cookbook, bkend troubleshooting

Project configuration initialization. Use when: first-time setup, auto-detecting framework, replacing CLAUDE.md placeholders. Not for: ongoing config checks (use claude-health), skill creation (use skill-creator). Output: configured CLAUDE.md + project settings + rules + hooks.

Post-development test completion. Analyzes developed features from context, checks integration/e2e test coverage, writes missing tests. Use after feature-dev, before /precommit.

Portfolio system knowledge base. Covers position queries, routing strategies, {PRIMARY_PROVIDER} integration, cache design.

GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + verdict assessment + investigation strategy.

Code investigation knowledge base. Covers code history tracking, issue introduction analysis, root cause diagnosis.

Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test. Not for: modifying data (use feature-dev), code review (use codex-review-fast), writing tests (use codex-test-gen), security audit (use codex-security).

Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.

Feasibility analysis from first principles. Use when: evaluating solutions before tech-spec, comparing approaches, risk assessment. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: quantitative comparison + recommendation.

Remove AI-generated artifacts from documents, including tool names, boilerplate patterns, over-structuring.

Create or update request documents. Auto-fills templates for new requests, updates progress based on implementation for existing ones.

Implement features via Codex exec. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.