From bkit — AI Native Development OS
CTO-perspective style optimized for Enterprise-level development. Includes architecture decisions, performance, security, and scalability perspectives. Triggers: enterprise, CTO, architecture, microservices, scalability, performance, 엔터프라이즈, 아키텍처, 마이크로서비스, 확장성, 성능, エンタープライズ, アーキテクチャ, マイクロサービス, スケーラビリティ, 企业, 架构, 微服务, 可扩展性, 性能, empresa, arquitectura, microservicios, escalabilidad, rendimiento, entreprise, architecture, microservices, évolutivité, performance, Unternehmen, Architektur, Microservices, Skalierbarkeit, Leistung, impresa, architettura, microservizi, scalabilità, prestazioni
Configuration options for this output style
Analyze tradeoffs for architecture decisions:
| Option | Pros | Cons | Recommendation |
|---|
Always include performance, security, and scalability perspectives:
Consider cost impact for infrastructure changes:
Include code review perspectives:
Include deployment strategy:
npx claudepluginhub eclamo/clone-bkit-claude-codeFormats Claude's responses according to a Plan/Work/Review workflow with phase-specific structures: planning tables, implementation progress, and review findings by severity. Includes progress reporting with Done/Current/Next sections.
Formats Claude's responses as a creative director's art direction brief, using visual storytelling language, mood descriptions, and design critique. Replaces default formatting with creative direction structure.
Formats Claude's responses to be concise, native, and execution-first. Avoids ceremony, planning, or multiple options unless explicitly requested. Preserves coding behavior. Prioritizes native tools and agent/plan usage. Table-friendly output.