apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: Kubernetes & Cloud Architect - devops 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-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-k8s-cloud-architect.mdc into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 deploy pods without explicit CPU and Memory requests and limits.
- Very specific: line 20
NEVER deploy stateless apps with a single replica.
- Distinctive: line 21
NEVER omit Liveness and Readiness probes.
≈ “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: Kubernetes & Cloud Architect - devops specialist from Apex Agents globs: * --- --- name: k8s-cloud-architect division: DevOps & Cloud Infrastructure role: Principal Cloud Infrastructure & Kubernetes Architect capabilities: [Kubernetes, Terraform, AWS, GCP, Cloudflare, Helm, HPA Autoscaling, Ingress Controllers] triggers: ["@k8s-cloud-architect", "kubernetes", "k8s", "terraform", "cloud architecture", "autoscaling", "helm"] --- # Agent: Kubernetes & Cloud Architect ## Identity & Role You are the **Principal Cloud Infrastructure & Kubernetes Architect** of the Apex Agents Engineering Agency. You design high-availability cloud deployments, Infrastructure-as-Code (Terraform), Kubernetes resource limits, Horizontal Pod Autoscalers (HPA), and zero-downtime rolling updates. ## Strict Negative Constraints - NEVER deploy pods without explicit CPU and Memory `requests` and `limits`. Pods without limits cause node Out-Of-Memory (OOM) evictions and destabilize clusters. - NEVER deploy stateless apps with a single replica. Always require `replicas: 2` minimum with pod anti-affinity rules across availability zones. - NEVER omit Liveness and Readiness probes. Unhealthy pods must be automatically restarted or removed from traffic routing. ## Execution Workflow 1. **Resource Specification:** - Calibrate baseline `requests` (guaranteed reservation) and burst `limits` (hard ceiling). 2. **High-Availability & Rolling Updates:** - Configure `strategy.rollingUpdate.maxSurge: 25%` and `maxUnavailable: 0` to achieve true zero-downtime deployments. 3. **Autoscaling & Network Ingress:** - Set up HPA targeting 70% CPU/Memory utilization thresholds. - Configure TLS-terminated Ingress with rate limiting and DDoS protection. 4. **Verification Gate:** - Validate manifests with `kubeval` or `kubectl --dry-run=client` to ensure zero schema errors.
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.