From forge
Provides Event Storming workshop facilitation guidance โ discovering domain events, commands, aggregates, policies, and bounded contexts. Use when starting domain exploration, mapping business processes, finding aggregate boundaries, running an event storming session, or exploring how a system works from a DDD perspective.
npx claudepluginhub caiokf/forgeThis skill uses the workspace's default tool permissions.
This skill provides knowledge and facilitation guidance for Event Storming workshops โ a collaborative domain discovery technique invented by Alberto Brandolini that uses color-coded "sticky notes" to explore complex business domains.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Share bugs, ideas, or general feedback.
This skill provides knowledge and facilitation guidance for Event Storming workshops โ a collaborative domain discovery technique invented by Alberto Brandolini that uses color-coded "sticky notes" to explore complex business domains.
This skill should be used when:
| Element | Color | Format | Example |
|---|---|---|---|
| Domain Event | ๐ง Orange | Past tense fact | Order Placed |
| Command | ๐ Blue | Imperative action | Place Order |
| Actor | ๐ค Yellow | Person/system | Customer |
| Aggregate | ๐ Yellow rect | Entity boundary | Order |
| Policy | ๐ Lilac | When-then rule | When OrderPlaced then NotifyWarehouse |
| Read Model | ๐ข Green | Information view | Order Dashboard |
| External System | ๐ฉ Green | 3rd party | Payment Gateway |
| Hotspot | ๐ด Red/Pink | Question/conflict | Who owns pricing? |
Choose the appropriate depth before starting:
| Level | Scope | Detail |
|---|---|---|
| Big Picture | Entire value stream end-to-end | Events and hotspots only |
| Process Level | One bounded context or process | Commands, aggregates, policies |
| Design Level | Implementation-ready | Invariants, state machines, preconditions |
Establish scope, context, and depth level. Open with psychological safety โ quantity over quality in early phases.
Discover domain events as past-tense facts. Focus on happy paths first, then exceptions and compensations. Work forward from triggers or backward from outcomes.
Organize discovered events into a left-to-right timeline. Identify strict sequences vs. parallel processes.
Add commands (what triggers events), actors (who triggers commands), and external systems. Format: Actor performs Command โ results in Event.
Identify information actors need to see before performing commands. Format: View shows Data to help Actor decide Command.
Identify aggregates that handle commands and enforce invariants. Cluster related events and commands into entity boundaries.
Identify where language or ownership changes. Look for Upstream/Downstream, Shared Kernel, and Anti-Corruption Layer patterns.
Add automated reactions to events. Format: When [Event] then [Action]. Include compliance, notifications, and side effects.
Mark areas of confusion, conflict, or opportunity. Capture unanswered questions.
Summarize discoveries, validate with participants, identify follow-up sessions.
Generate a markdown document using templates/event-storming-board.md containing:
| File | Content |
|---|---|
references/facilitator-prompts.md | Detailed facilitator prompts for each session phase |
templates/event-storming-board.md | Output template for the event storming board artifact |