event-storming-modeling
Skill1 starsChanged 5 months agoNo licenceView on GitHub
Reference for modeling a domain with Event Storming and tactical/strategic DDD: the sticky-note color vocabulary, the command-aggregate-event-policy flow grammar, and the conflations to avoid. Use when building or reviewing an event-storming diagram or model, choosing colors/labels for domain concepts, deciding whether something is a Policy vs an Invariant, representing aggregates/commands/events/read models/external systems/actors, mapping a DDD domain, generating such diagrams from code, or recovering a model from annotated .NET assemblies with Hindstorm. Covers what a topological (code-derived) view loses versus a workshop wall, and when a domain is a streaming/dataflow transformation pipeline (where forcing the command/aggregate grammar is over-modeling). For those, names the second-plane vocabulary: CEP / event abstraction hierarchy, soft real-time, supporting vs core subdomain, data on the inside vs outside, domain event vs measurement, and Event Modeling's Automation and Translation patterns, joined to the domain at an anti-corruption seam.
In this repository51 other files it gives its agents.
- agent-standards-setupSkill
- aspire-deploymentSkill
- aspire-dotnet-gotchasSkill
- aspireifySkill
- aspire-initSkill
- aspire-monitoringSkill
- aspire-orchestrationSkill
- aspireSkill
- browser-verifySkill
- canvas-2d-render-perfSkill
- claude-agent-sdk-workerSkill
- contract-first-testsSkill
- csharp-doc-commentsSkill
- diataxisSkill
- disseminate-learningsSkill
- dotnet-cli-releaseSkill
- dotnet-inspectSkill
- dotnet-local-voiceSkill
- generative-svg-marksSkill
- github-cliSkill
- homelab-bootstrapSkill
- homelab-dashboardSkill
- homelab-local-inferenceSkill
- homelab-observabilitySkill
- infisical-cliSkill
- jira-apiSkill
- jpl-horizons-ephemerisSkill
- kroger-apiSkill
- litellmSkill
- manage-skillsSkill
- masstransit-nodejs-interopSkill
- matter-js-dom-physicsSkill
- nuget-trusted-publishingSkill
- obsidian-vaultSkill
- opencode-plugin-devSkill
- open-link-after-animationSkill
- orchestrated-deliverySkill
- orchestratorSkill
- osint-investigationSkill
- outlook-apiSkill
- playwright-cliSkill
- protostar-docs-deploySkill
- proxmox-apiSkill
- python-audio-vadSkill
- recursive-explorationSkill
- rmlSkill
- skill-finderSkill
- technitium-apiSkill
- web-asset-exportSkill
- windows-git-worktreeSkill
- windows-python-cudaSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.