메뉴
Runs a Big Picture Event Storming session on a bounded context or the entire codebase (backend + frontend). Discovers domain events, commands, entities, context boundaries, frontend projections (hooks, presenters, views). Produces a structured document in docs/ddd/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audit naming quality (files, functions, types, variables, folders) without reading the code. Takes names as input and reports what Claude understands from each name alone. Judges three axes: Screaming Architecture (does the name reveal the domain?), Clean Code (full words, intention-revealing, no abbreviations), and Ubiquitous Language (vocabulary consistency across the codebase). Useful to validate that names self-document.
Extracts business rules from a module (backend + frontend) and produces three tables: Product view (business concepts), Backend dev view (type + source), Frontend dev view (type + source). Saves to docs/business-rules/.
Strategic DDD guide for this project (fullstack — backend + frontend share the same bounded contexts). Use to slice the domain into bounded contexts, define ubiquitous language, create a new business module, analyze boundaries between contexts. Tactical patterns follow Clean Architecture (see architecture-backend and architecture-frontend skills).
Autonomous frontend feature implementation via spec-driven development. Orchestrates a frontend-planner and a frontend-implementer with architecture-frontend preloaded. Applies Humble Object pattern to views, MVVM structure with Presenter classes + Zod ViewModels, singleton registry DI. Consumes specs produced by /product-manager. For backend features, use /implement-feature instead.
Feature challenge and specification. Use to define a feature, write acceptance criteria, scope a ticket, produce INVEST specs with custom DSL in docs/specs/. Refuses vague scopes and forces clarification.
Discover implicit team conventions (tribal knowledge) in a codebase. Spawns parallel sub-agents to analyze 6 axes: naming, error handling, testing, architecture, git workflow, and code idioms. Generates a structured report in docs/tribal-knowledge/.
| name | event-storming |
| description | Runs a Big Picture Event Storming session on a bounded context or the entire codebase (backend + frontend). Discovers domain events, commands, entities, context boundaries, frontend projections (hooks, presenters, views). Produces a structured document in docs/ddd/. |
| triggers | ["event.?storming","domain.*events","context.*map","bounded.*context.*analyse"] |
Runs a Big Picture Event Storming session on a bounded context or the entire codebase (backend + frontend). A Bounded Context spans both workspaces — the event-storming deliverable covers the backend domain (events, commands, entities) AND the frontend projections (hooks, presenters, views) that consume them.
/event-storming <bounded-context> — analyze an existing BC in the code/event-storming audit — global analysis of all BCs/event-storming explore <brief> — pre-code exploration from a functional briefDetermine the mode:
Spawn the event-storming agent with this prompt:
Mode: <target|audit|exploration>
Bounded Context: <name or "all">
Brief: <functional brief if exploration mode>
Execute the Big Picture Event Storming according to your mission.
Use subagent_type: "event-storming" and model: "opus".
Display the agent result as-is.
Documents are written by the agent in docs/ddd/event-storming/.
The agent enriches docs/ddd/ubiquitous-language.md with the discovered terms.
After the agent completes, invoke the /wiki skill to push the updated DDD documentation to the GitHub wiki.
/wiki <bounded-context>/wiki (full sync)/event-storming shipping
/event-storming audit
/event-storming explore "The system must allow tracking packages in real time"