Cqrs Design

Separate command (write) and query (read) models for complex domains. Use when read/write patterns diverge significantly or when audit/consistency requirements demand immutability.

48 stars 10 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill cqrs-design
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/cqrs-design ~/.claude/skills/cqrs-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# CQRS Design

Implement Command Query Responsibility Segregation (CQRS) to align data models with actual usage patterns and enable independent scaling of reads and writes.

## Context

You are designing or refactoring a system with complex read and write patterns. The user faces performance issues, audit requirements, or divergent read/write needs. Read their current data access patterns.

## Domain Context

Based on Greg Young's CQRS work and Fowler's research:

- **Command Side**: Optimized for writes; enforces business rules; maintains single source of truth
- **Query Side**: Optimized for reads; denormalized for performance; eventual consistency acceptable
- **Event Sourcing**: Often paired with CQRS; commands generate events, events drive queries
- **Read Models**: Projections built from events; can be recreated from command side state
- **Consistency Boundary**: Commands are strongly consistent within aggregate; queries lag slightly

## Instructions

1. **Analyze Read vs Write**: List all queries used; identify divergences from write model. Example: commands work with Orders (with line items), but queries need denormalized OrderSummary (customer name, total, status).

2. **Design Command Model**: Optimize for consistency and rule enforcement. Aggregate should protect invariants. Example: Order aggregate ensures total ≥ sum of items.
Read the full skill on GitHub

Details

Skill name
cqrs-design
Path
architect/system-design/skills/cqrs-design/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Cqrs Design skill do?

Separate command (write) and query (read) models for complex domains. Use when read/write patterns diverge significantly or when audit/consistency requirements demand immutability.

How do I install the Cqrs Design skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Cqrs Design popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.