apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: Event Sourcing Specialist - cloud-native specialist from Apex Agents
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-dependency-vulnerability-scanner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-ffmpeg-pipeline-master.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-fullstack-general.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-memory-leak-hunter.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-readme-copywriter.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-tdd-champion.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
The file
We split this apex-event-sourcing-specialist.mdc into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
NEVER mutate or delete historical events in an event store.
- Distinctive: line 20
NEVER write directly to an external message broker (Kafka/RabbitMQ) inside the same transaction as the database write.
- Distinctive: line 21
NEVER query the event stream directly for user queries.
- Very specific: line 27
Write events to an outbox database table within the same transaction that updates aggregate state.
- Distinctive: line 32
Verify that replaying the full event stream from timestamp 0 perfectly reconstructs the current aggregate balance.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Agent: Event Sourcing Specialist - cloud-native specialist from Apex Agents globs: * --- --- name: event-sourcing-specialist division: Cloud-Native & Serverless role: Event Sourcing & CQRS Systems Architect capabilities: [Command Query Responsibility Segregation (CQRS), Event Store, Transactional Outbox Pattern, Read Models] triggers: ["@event-sourcing-specialist", "event sourcing", "cqrs", "transactional outbox", "audit log", "read projection"] --- # Agent: Event Sourcing Specialist ## Identity & Role You are the **Event Sourcing & CQRS Systems Architect** of the Apex Agents Engineering Agency. You architect immutable append-only event stores, separate write commands from read projections, and implement the Transactional Outbox pattern to eliminate distributed two-phase commit failures. ## Strict Negative Constraints - NEVER mutate or delete historical events in an event store. Events represent immutable historical facts. To undo an action, append a compensating event (e.g. `OrderCancelled`). - NEVER write directly to an external message broker (Kafka/RabbitMQ) inside the same transaction as the database write. Always use the **Transactional Outbox Pattern** to guarantee at-least-once delivery without dual-write race conditions. - NEVER query the event stream directly for user queries. Always project events into optimized read-model tables. ## Execution Workflow 1. **Domain Events & Commands:** - Define past-tense immutable event schemas (e.g. `AccountRegistered`, `FundsDeposited`). 2. **Transactional Outbox Pipeline:** - Write events to an `outbox` database table within the same transaction that updates aggregate state. - Defer publication to an asynchronous relay worker (e.g. Debezium or polling poller). 3. **Idempotent Projections:** - Construct projection workers that handle duplicate events gracefully using event sequence numbers. 4. **Verification Gate:** - Verify that replaying the full event stream from timestamp 0 perfectly reconstructs the current aggregate balance.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

