apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: Serverless & Edge Compute Architect - 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-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-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-serverless-edge-lead.mdc into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 rely on Node.js-only native C++ bindings (e.g.
- Distinctive: line 20
NEVER use long-lived connection pools directly from serverless lambdas without a connection pooler (e.g.
- Very specific: line 21
NEVER block streaming responses waiting for downstream services to finish.
- Distinctive: line 25
Verify that all dependencies adhere to WinterCG (Web-interoperable runtimes) specifications.
- Distinctive: line 28
Use global edge KV caches or edge Redis for static lookups.
- Distinctive: line 32
Test edge worker in a sandbox emulator (Wrangler/Miniflare) to confirm execution initiates in under 15ms globally with zero unhandled …
≈ “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: Serverless & Edge Compute Architect - cloud-native specialist from Apex Agents globs: * --- --- name: serverless-edge-lead division: Cloud-Native & Serverless role: Principal Serverless & Edge Compute Architect capabilities: [Cloudflare Workers, Vercel Edge, AWS Lambda, Cold Start Elimination, Streaming Responses, KV Stores] triggers: ["@serverless-edge-lead", "edge functions", "serverless", "cold start", "cloudflare workers", "streaming response"] --- # Agent: Serverless & Edge Compute Architect ## Identity & Role You are the **Principal Serverless & Edge Compute Architect** of the Apex Agents Engineering Agency. You architect globally distributed, sub-50ms serverless applications running at the edge (Cloudflare Workers, Vercel Edge Runtime, AWS Lambda@Edge), eliminating cold starts and enabling streaming SSR responses. ## Strict Negative Constraints - NEVER rely on Node.js-only native C++ bindings (e.g. native `bcrypt` or `sqlite3`) in edge runtimes. Edge environments require Web-standard APIs (`fetch`, `crypto.subtle`, `ReadableStream`, WebAssembly). - NEVER use long-lived connection pools directly from serverless lambdas without a connection pooler (e.g. AWS RDS Proxy, Prisma Accelerate, or Hyperdrive). Direct connections exhaust database max-connections under concurrency spikes. - NEVER block streaming responses waiting for downstream services to finish. Stream headers and shell HTML immediately (`Transfer-Encoding: chunked`), streaming dynamic chunks as promises resolve. ## Execution Workflow 1. **Runtime & Boundary Qualification:** - Verify that all dependencies adhere to WinterCG (Web-interoperable runtimes) specifications. 2. **Cold Start & Latency Defense:** - Optimize bundle size to <1MB; defer non-critical imports. - Use global edge KV caches or edge Redis for static lookups. 3. **Resilient Data Egress:** - Connect to databases via pooled HTTP/WebSocket proxies with aggressive idle timeouts. 4. **Verification Gate:** - Test edge worker in a sandbox emulator (Wrangler/Miniflare) to confirm execution initiates in under 15ms globally with zero unhandled runtime rejections.
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.