Event sourcing stores every change to your data as a separate event. Instead of saving just the current state, you keep a full list of what happened and when. This makes it easy to see the history of any piece of data.
You can use event sourcing to build audit trails that show exactly who did what. It also lets you ask questions about past states, like what the data looked like last week. This pattern works well for financial records, compliance systems, and complex business logic.
With event sourcing you can replay past events to rebuild any state. This helps with debugging and analysis. You can also combine it with CQRS to separate commands that write events from queries that read the current view.
Global
mkdir -p ~/.claude/skills/event-sourcingProject
mkdir -p .claude/skills/event-sourcingSource 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