CQRS stands for Command Query Responsibility Segregation. It is a way to build software that handles lots of data. You separate the code that changes data from the code that reads data. This makes your system faster and easier to grow.
With CQRS you can scale read operations independently from write operations. You can also use different data models for reading and writing. This is very useful for complex reports or high traffic apps.
Many developers use CQRS with event sourcing. Events record every change. Then a separate process builds the read model from those events. This gives you a clear history of all changes.
Global
mkdir -p ~/.claude/skills/cqrs-implementationProject
mkdir -p .claude/skills/cqrs-implementationSource Repository
Lark Openapi Explorerlarksuite/cli
Discover and call native Lark OpenAPIs not covered by existing CLI commands
Supabasesupabase/agent-skills
Add a database auth and APIs to your app with Supabase
Design An Interfacemattpocock/skills
Generate many different interface designs and pick the best one
Convex Quickstartget-convex/agent-skills
Rapidly set up a Convex backend for new or existing apps with one command
Convex Create Componentget-convex/agent-skills
Create reusable Convex components with isolated tables and clear APIs
Convexget-convex/agent-skills
Use this router to find the perfect Convex skill for your task
Firebase Remote Config Basicsfirebase/agent-skills
Change your app's behavior instantly without a new update
Notion Apiintellectronica/agent-skills
Automate your Notion workspace with simple API calls