mcpbeat

Cqrs Implementation

dokhacgiakhoa/cqrs-implementation

Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.

4k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill cqrs-implementation

What comes with it

15 546 bytes besides the instruction
sub-skills/implementation-playbook.md

The instruction itself

7 sections, as written by the author

CQRS Implementation

Comprehensive guide to implementing CQRS (Command Query Responsibility Segregation) patterns.

Use this skill when

  • Separating read and write concerns
  • Scaling reads independently from writes
  • Building event-sourced systems
  • Optimizing complex query scenarios
  • Different read/write data models are needed
  • High-performance reporting is required

Do not use this skill when

  • The domain is simple and CRUD is sufficient
  • You cannot operate separate read/write models
  • Strong immediate consistency is required everywhere

Instructions

  • Identify read/write workloads and consistency needs.
  • Define command and query models with clear boundaries.
  • Implement read model projections and synchronization.
  • Validate performance, recovery, and failure modes.
  • If detailed patterns are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed CQRS patterns and templates.

🧠 Knowledge Modules (Fractal Skills)

1. implementation-playbook

How to use it

Copy the folder

Take dokhacgiakhoa/cqrs-implementation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.