Claude Cursor Skill

projection-patterns

Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_backend-development_skills_projection-patterns-554237f.zip · 3 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/backend-development/skills/projection-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Projection Patterns

Comprehensive guide to building projections and read models for event-sourced systems.

When to Use This Skill

  • Building CQRS read models
  • Creating materialized views from events
  • Optimizing query performance
  • Implementing real-time dashboards
  • Building search indexes from events
  • Aggregating data across streams

Core Concepts

1. Projection Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│ Event Store │────►│ Projector   │────►│ Read Model  │
│             │     │             │     │ (Database)  │
│ ┌─────────┐ │     │ ┌─────────┐ │     │ ┌─────────┐ │
│ │ Events  │ │     │ │ Handler │ │     │ │ Tables  │ │
│ └─────────┘ │     │ │ Logic   │ │     │ │ Views   │ │
│             │     │ └─────────┘ │     │ │ Cache   │ │
└─────────────┘     └─────────────┘     └─────────────┘

2. Projection Types

Type Description Use Case
Live Real-time from subscription Current state queries
Catchup Process historical events Rebuilding read models
Persistent Stores checkpoint Resume after restart
Inline Same transaction as write Strong consistency

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

  • Make projections idempotent - Safe to replay
  • Use transactions - For multi-table updates
  • Store checkpoints - Resume after failures
  • Monitor lag - Alert on projection delays
  • Plan for rebuilds - Design for reconstruction

Don'ts

  • Don't couple projections - Each is independent
  • Don't skip error handling - Log and alert on failures
  • Don't ignore ordering - Events must be processed in order
  • Don't over-normalize - Denormalize for query patterns
Files (agents)
  • references
    • details.md 13.9 KB
      Loading…
  • SKILL.md 2.6 KB
    ---
    name: projection-patterns
    description: Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
    ---
    
    # Projection Patterns
    
    Comprehensive guide to building projections and read models for event-sourced systems.
    
    ## When to Use This Skill
    
    - Building CQRS read models
    - Creating materialized views from events
    - Optimizing query performance
    - Implementing real-time dashboards
    - Building search indexes from events
    - Aggregating data across streams
    
    ## Core Concepts
    
    ### 1. Projection Architecture
    
    ```
    ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
    │ Event Store │────►│ Projector   │────►│ Read Model  │
    │             │     │             │     │ (Database)  │
    │ ┌─────────┐ │     │ ┌─────────┐ │     │ ┌─────────┐ │
    │ │ Events  │ │     │ │ Handler │ │     │ │ Tables  │ │
    │ └─────────┘ │     │ │ Logic   │ │     │ │ Views   │ │
    │             │     │ └─────────┘ │     │ │ Cache   │ │
    └─────────────┘     └─────────────┘     └─────────────┘
    ```
    
    ### 2. Projection Types
    
    | Type           | Description                 | Use Case               |
    | -------------- | --------------------------- | ---------------------- |
    | **Live**       | Real-time from subscription | Current state queries  |
    | **Catchup**    | Process historical events   | Rebuilding read models |
    | **Persistent** | Stores checkpoint           | Resume after restart   |
    | **Inline**     | Same transaction as write   | Strong consistency     |
    
    ## Templates and detailed worked examples
    
    Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates.
    
    ## Best Practices
    
    ### Do's
    
    - **Make projections idempotent** - Safe to replay
    - **Use transactions** - For multi-table updates
    - **Store checkpoints** - Resume after failures
    - **Monitor lag** - Alert on projection delays
    - **Plan for rebuilds** - Design for reconstruction
    
    ### Don'ts
    
    - **Don't couple projections** - Each is independent
    - **Don't skip error handling** - Log and alert on failures
    - **Don't ignore ordering** - Events must be processed in order
    - **Don't over-normalize** - Denormalize for query patterns
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.