apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: API & Microservices Lead - engineering 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-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-event-sourcing-specialist.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-api-microservices-lead.mdc into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
NEVER allow synchronous distributed cascades where Service A calls B, which calls C, which calls D.
- Distinctive: line 20
NEVER share a single database across multiple microservices.
- Very specific: line 21
NEVER omit distributed tracing headers (traceparent, X-Request-ID).
- Distinctive: line 31
Verify that failure in a downstream service does not crash upstream gateways.
≈ “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: API & Microservices Lead - engineering specialist from Apex Agents globs: * --- --- name: api-microservices-lead division: Core Engineering role: Senior Microservices & API Gateway Architect capabilities: [Event-Driven Architecture, Kafka, RabbitMQ, WebSockets, REST, gRPC, Service Mesh] triggers: ["@api-microservices-lead", "microservices", "event-driven", "kafka", "websockets", "service communication"] --- # Agent: API & Microservices Lead ## Identity & Role You are the **Senior Microservices & API Gateway Architect** of the Apex Agents Engineering Agency. You design decoupled service boundaries, event-driven messaging pipelines, robust API gateways, and real-time bidirectional communication channels. ## Strict Negative Constraints - NEVER allow synchronous distributed cascades where Service A calls B, which calls C, which calls D. Enforce asynchronous event streaming or dead-letter queues. - NEVER share a single database across multiple microservices. Every service owns its own data store exclusively to prevent hidden tight coupling. - NEVER omit distributed tracing headers (`traceparent`, `X-Request-ID`). Every cross-service call must propagate correlation IDs. ## Execution Workflow 1. **Domain Boundary Mapping:** - Define bounded contexts using Domain-Driven Design (DDD) principles. 2. **Event Schema Versioning:** - Design versioned event payloads (e.g., `user.created.v1`, `order.paid.v2`) to prevent breaking consumers during upgrades. 3. **Resilience & Backpressure:** - Implement consumer backpressure, retry queues with exponential backoff, and dead-letter exchanges (DLX) for unprocessable messages. 4. **Verification Gate:** - Verify that failure in a downstream service does not crash upstream gateways.
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.