Agent skill

cqrs-event-sourcing

Quellcode ansehen: nickcrew/claude-cortex

#124Globales Ranking · von 124 SkillsSafe

Installation

npx skills add nickcrew/claude-cortex --skill cqrs-event-sourcing

68

Installationen

EU-hosted inference API

Power your AI agent skills with open-source models.

Drop-in OpenAI-compatible API. No data leaves Europe.

MiniMax

MiniMax M3

$0.50 / $1.90

per M tokens

Z.ai

GLM 5.3 Flash

$0.20 / $0.60

per M tokens

MoonshotAI

Kimi K3

$4.00 / $18.00

per M tokens

DeepSeek

DeepSeek V4.1 Flash

$0.40 / $1.42

per M tokens

CQRS and Event Sourcing Patterns

Expert guidance for implementing Command Query Responsibility Segregation (CQRS) and Event Sourcing patterns to build scalable, auditable systems with complete historical tracking and optimized read/write models.

When to Use This Skill

  • Building systems requiring complete audit trails and compliance
  • Implementing temporal queries ("show me the state at time T")
  • Designing high-scale applications with complex domain logic
  • Creating systems with significantly different read and write patterns
  • Building event-driven architectures with historical replay capability
  • Implementing systems requiring multiple read model projections
  • Designing applications where understanding "what happened" is critical
  • Building collaborative systems with conflict resolution needs

Core Principles

1. Command Query Separation

Separate operations that change state (commands) from operations that read state (queries).

Commands (Write) Queries (Read)
Express intent (CreateOrder, UpdatePrice) Return data, never change state
Can be rejected (validation failures) Can be cached and optimized
Return success/failure, not data Multiple models for different needs
Change system state Eventually consistent with writes

2. Events as Source of Truth

Store state changes as immutable events rather than current state snapshots.

Traditional: Store what IS → UPDATE users SET email = 'new@email.com'
Event Sourcing: Store what HAPPENED → APPEND UserEmailChanged event

Result: Complete history, temporal queries, audit trail

3. Eventual Consistency

Accept temporary inconsistency between write and read models for scalability.

4. Domain-Driven Design Integration

  • Aggregates enforce business invariants
  • Events represent domain facts
  • Commands express domain operations
  • Bounded contexts define consistency boundaries

Quick Reference

Task Load reference
CQRS implementation patterns skills/cqrs-event-sourcing/references/cqrs-patterns.md
Event sourcing & snapshots skills/cqrs-event-sourcing/references/event-sourcing.md
EventStoreDB & Axon Framework skills/cqrs-event-sourcing/references/event-store-tech.md
Consistency patterns skills/cqrs-event-sourcing/references/consistency-patterns.md
Best practices checklist skills/cqrs-event-sourcing/references/best-practices.md

Workflow

  1. Identify if CQRS/ES is appropriate (high audit, temporal, or scale needs)
  2. Design commands expressing user intent
  3. Define events as immutable facts (past tense naming)
  4. Implement aggregates as consistency boundaries
  5. Create projections optimized for specific query needs
  6. Handle eventual consistency across bounded contexts

Common Mistakes

  • Using CQRS for simple CRUD applications (overkill)
  • Large aggregates that span multiple consistency boundaries
  • Modifying or deleting events after publication
  • Skipping command validation before aggregate processing
  • Missing idempotency in event handlers
  • No versioning strategy for event schema evolution
  • Tight coupling between aggregates (use ID references only)

Resources

  • Books: "Implementing Domain-Driven Design" (Vernon), "Event Sourcing & CQRS" (Betts et al)
  • Sites: cqrs.wordpress.com, eventstore.com/blog, axoniq.io/resources
  • Tools: EventStoreDB, Axon Framework, Marten, Eventuous
  • Patterns: Event Sourcing, CQRS, Process Manager, Saga, Snapshot

So verwenden Sie diesen Skill

  1. 1

    Install cqrs-event-sourcing by running npx skills add nickcrew/claude-cortex --skill cqrs-event-sourcing in your project directory. Führen Sie den obigen Installationsbefehl in Ihrem Projektverzeichnis aus. Die Skill-Datei wird von GitHub heruntergeladen und in Ihrem Projekt platziert.

  2. 2

    Keine Konfiguration erforderlich. Ihr KI-Agent (Claude Code, Cursor, Windsurf usw.) erkennt installierte Skills automatisch und nutzt sie als Kontext bei der Code-Generierung.

  3. 3

    Der Skill verbessert das Verständnis Ihres Agenten für cqrs-event-sourcing, und hilft ihm, etablierte Muster zu befolgen, häufige Fehler zu vermeiden und produktionsreifen Code zu erzeugen.

Was Sie erhalten

Skills sind Klartext-Anweisungsdateien — kein ausführbarer Code. Sie kodieren Expertenwissen über Frameworks, Sprachen oder Tools, das Ihr KI-Agent liest, um seine Ausgabe zu verbessern. Das bedeutet null Laufzeit-Overhead, keine Abhängigkeitskonflikte und volle Transparenz: Sie können jede Anweisung vor der Installation lesen und prüfen.

Kompatibilität

Dieser Skill funktioniert mit jedem KI-Coding-Agenten, der das skills.sh-Format unterstützt, einschließlich Claude Code (Anthropic), Cursor, Windsurf, Cline, Aider und anderen Tools, die projektbezogene Kontextdateien lesen. Skills sind auf Transportebene framework-agnostisch — der Inhalt bestimmt, für welche Sprache oder welches Framework er gilt.

Data sourced from the skills.sh registry and GitHub. Install counts and security audits are updated regularly.