Automated summary
Guides the design of event-sourced and CQRS systems, including aggregate boundaries, projections, sagas, versioning, and snapshotting.
Strengths
- Covers end-to-end concerns from aggregate design and immutable events to projections, sagas, and schema evolution.
- Provides explicit safety rules for never mutating committed events and rebuilding projections in staging first.
- Includes practical guidance on idempotent handlers, correlation IDs, and snapshotting for long-lived aggregates.
Limitations
- Offers architectural guidance rather than language- or framework-specific implementation code.
- The approach adds significant complexity and is inappropriate for simple CRUD domains.
- Requires operational maturity for event store maintenance, projection rebuilds, and eventual consistency.
Use it when designing systems that need audit trails, temporal queries, complex workflows with compensating actions, or separate read and write models.
Avoid it for simple CRUD applications or when strong immediate consistency is required across the entire system.
Security analysis
SafeThis skill provides architectural guidance on event sourcing and CQRS without declaring or using any tools, scripts, or commands. It contains no destructive, exfiltration, or obfuscated actions, so it poses no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Design an event-sourced order management system with CQRS. Identify aggregate boundaries, define the core events, and propose projections for order history and current status.I have an event-driven checkout flow. Help me design a saga or process manager that coordinates payment, inventory reservation, and compensation when a step fails.Review my event-sourced aggregate design and propose a strategy for event schema versioning, snapshotting long-lived aggregates, and rebuilding projections safely.name: event-sourcing-architect description: "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e..." risk: unknown source: community
Event Sourcing Architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
Capabilities
- Event store design and implementation
- CQRS (Command Query Responsibility Segregation) patterns
- Projection building and read model optimization
- Saga and process manager orchestration
- Event versioning and schema evolution
- Snapshotting strategies for performance
- Eventual consistency handling
Use this skill when
- Building systems requiring complete audit trails
- Implementing complex business workflows with compensating actions
- Designing systems needing temporal queries ("what was state at time X")
- Separating read and write models for performance
- Building event-driven microservices architectures
- Implementing undo/redo or time-travel debugging
Do not use this skill when
- The domain is simple and CRUD is sufficient
- You cannot support event store operations or projections
- Strong immediate consistency is required everywhere
Instructions
- Identify aggregate boundaries and event streams
- Design events as immutable facts
- Implement command handlers and event application
- Build projections for query requirements
- Design saga/process managers for cross-aggregate workflows
- Implement snapshotting for long-lived aggregates
- Set up event versioning strategy
Safety
- Never mutate or delete committed events in production.
- Rebuild projections in staging before running in production.
Best Practices
- Events are facts - never delete or modify them
- Keep events small and focused
- Version events from day one
- Design for eventual consistency
- Use correlation IDs for tracing
- Implement idempotent event handlers
- Plan for projection rebuilding
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/event-sourcing-architect-mrwakcxm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/event-sourcing-architect-mrwakcxm/download' --output '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md.part' && mv '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md.part' '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md' && test -s '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/event-sourcing-architect' && cp -R '.skill-downloads/event-sourcing-architect-mrwakcxm' '.claude/skills/event-sourcing-architect'Cursor
test -f '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md' && test -s '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/event-sourcing-architect' && cp -R '.skill-downloads/event-sourcing-architect-mrwakcxm' '.cursor/skills/event-sourcing-architect'Codex
test -f '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md' && test -s '.skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/event-sourcing-architect' && cp -R '.skill-downloads/event-sourcing-architect-mrwakcxm' '.agents/skills/event-sourcing-architect'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/event-sourcing-architect-mrwakcxm'openskills read 'event-sourcing-architect-mrwakcxm'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/event-sourcing-architect-mrwakcxm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.