메뉴
Evaluates components, tasks, and modules for size and coupling, then identifies what must be split to maintain small blast radius. Use when planning or reviewing architecture, when a task feels too broad, when a module absorbs unrelated concerns, or when failures are hard to localize.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Evaluates and enforces layered middleware architecture for authentication, authorization, and usage enforcement on API routes. Use when building request middleware, enforcing plans or feature access, or attaching request context to downstream handlers.
Selects Cloudflare infrastructure services and LLM providers for a feature set based on dependency chains, storage needs, and settled policy. Use when assigning services (D1, KV, R2, Durable Objects, Queues, Workflows, Workers AI, Hyperdrive), evaluating whether a feature needs Workflows or Durable Objects, choosing between LLM providers, or confirming a build follows the Workers-first topology.
Audits request handling pipelines for explicit data flow, visible transformations, and traceability through logs. Use when designing request handling pipelines, reviewing code for debuggability, tracing production issues, or evaluating whether a new developer could follow the flow.
Audits stateful logic and error handling to verify single sources of truth, boundary-layer error handling, and explicit recovery paths. Use when designing APIs or workflows, refactoring stateful logic, or reviewing retries, fallback behavior, or recovery flows.
Traces feature implementation from UI through handlers, middleware, and storage to identify broken wiring, dead paths, and coverage gaps. Use when reviewing implementation completeness, validating frontend-to-backend wiring, or checking route/handler/middleware/storage consistency.
Audits authentication, authorization, and input validation boundaries to verify trust is established once at entry and not re-checked ad hoc throughout business logic. Use when building or reviewing auth, designing middleware, handling user/webhook/third-party input, or performing security-oriented review.
| name | enforce-blast-radius |
| description | Evaluates components, tasks, and modules for size and coupling, then identifies what must be split to maintain small blast radius. Use when planning or reviewing architecture, when a task feels too broad, when a module absorbs unrelated concerns, or when failures are hard to localize. |
Primary roles: architect, planner
Inspects components, tasks, and architectural boundaries for excessive scope, coupling, or complexity. Produces concrete split recommendations so that every unit can be explained simply, tested in isolation, and fails without taking down unrelated functionality.
Ask these about any component:
If "no" to any of these, the component is too large.
| Scope | Threshold |
|---|---|
| Function | < 50 lines |
| Class/Module | < 200 lines |
| File | < 500 lines |
| Service | < 2000 lines |
If a component exceeds these, decompose it. The system can be complex — the parts should not be.
Produce the following:
