Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
| File | Covers |
|---|---|
references/api-design.md | REST, GraphQL, gRPC — URL rules, status codes, protocol selection |
references/authentication.md | OAuth 2.1, JWT, RBAC, MFA, session management |
references/security.md | OWASP Top 10 (2025), rate limiting, headers, secrets |
references/performance.md | Indexing, caching patterns, load balancing, async processing |
references/architecture.md | Microservices patterns, event-driven, CQRS, scalability |
references/testing.md | TDD, test pyramid, contract testing, migration tests |
references/code-quality.md | SOLID, design patterns, refactoring signals |
| Need | Choose |
|---|---|
| Public / browser clients | REST or GraphQL |
| Internal high-throughput | gRPC |
| Flexible data fetching | GraphQL |
| Streaming | gRPC (bidirectional) or SSE |
| Single team, unclear domain | Monolith |
| Multiple autonomous teams | Microservices |
| Audit trail required | Event Sourcing |
| Read/write load imbalance | CQRS |
| Task >200ms off request path | Async queue |
| Session across instances | Redis (never in-process) |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.
日本語の概要は準備中です。原文の説明を表示しています。
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
日本語の概要は準備中です。原文の説明を表示しています。
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.
日本語の概要は準備中です。原文の説明を表示しています。
Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.
日本語の概要は準備中です。原文の説明を表示しています。