fullstack-starter / rules
Cursor rule223 starsChanged 28 days agoMITView on GitHub
Terraform infrastructure-as-code standards for multi-cloud (AWS, GCP, Azure, OCI) provisioning
We split this infrastructure.mdc into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 15
OIDC First: Use OIDC/IAM roles for CI/CD authentication instead of long-lived credentials
- Very specific: line 16
Plan Before Apply: Always run terraform validate, terraform fmt, terraform plan before apply
- Distinctive: line 19
No Secrets in Code: Never hardcode passwords, API keys, or tokens in .tf files
- Distinctive: line 21
Environment Sizing: Use environment-based sizing (smaller for dev/staging, production-grade for prod)
- Distinctive: line 22
Policy as Code: Run OPA/Sentinel and security scanning (Checkov, tfsec) in CI/CD before apply
- Very specific: line 25
No Auto-Approve: Never use auto-approve in production.
- Distinctive: line 26
Drift Detection: Never skip drift detection in production
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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: "Terraform infrastructure-as-code standards for multi-cloud (AWS, GCP, Azure, OCI) provisioning"
globs: "**/*.{tf,tfvars,hcl}"
alwaysApply: false
---
<!-- Generated by oh-my-agent. Source: .agents/rules/infrastructure.md -->
# Infrastructure Standards
## Core Rules
1. **Provider-Agnostic**: Detect cloud provider from project context before writing any HCL
2. **Remote State**: Store state in remote backend (S3, GCS, Azure Blob) with versioning and locking
3. **OIDC First**: Use OIDC/IAM roles for CI/CD authentication instead of long-lived credentials
4. **Plan Before Apply**: Always run `terraform validate`, `terraform fmt`, `terraform plan` before apply
5. **Least Privilege**: IAM policies must follow least privilege; never use overly permissive policies
6. **Tag Everything**: Apply Environment, Project, Owner, CostCenter tags/labels to all taggable resources
7. **No Secrets in Code**: Never hardcode passwords, API keys, or tokens in .tf files
8. **Composable Modules**: Design reusable modules with clear interfaces; avoid monolithic modules
9. **Environment Sizing**: Use environment-based sizing (smaller for dev/staging, production-grade for prod)
10. **Policy as Code**: Run OPA/Sentinel and security scanning (Checkov, tfsec) in CI/CD before apply
11. **Version Pinning**: Pin all providers and modules; use `for_each` over `count`
12. **Cost Awareness**: Implement lifecycle policies, autoscaling schedules, and review cost estimates before apply
13. **No Auto-Approve**: Never use `auto-approve` in production; never `terraform destroy` without backup
14. **Drift Detection**: Never skip drift detection in production
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 3,978 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 repository131 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/backend.mdcCursor rule
- .cursor/rules/branching-strategy.mdcCursor rule
- .cursor/rules/build-guide.mdcCursor rule
- .cursor/rules/commit.mdcCursor rule
- .cursor/rules/database.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/design.mdcCursor rule
- .cursor/rules/design-tokens-guide.mdcCursor rule
- .cursor/rules/dev-workflow.mdcCursor rule
- .cursor/rules/frontend.mdcCursor rule
- .cursor/rules/i18n-arb.mdcCursor rule
- .cursor/rules/i18n-guide.mdcCursor rule
- .cursor/rules/lint-format-guide.mdcCursor rule
- .cursor/rules/market.mdcCursor rule
- .cursor/rules/mobile.mdcCursor rule
- .cursor/rules/preferred-editing-tools.mdcCursor rule
- .cursor/rules/quality.mdcCursor rule
- .cursor/rules/test-guide.mdcCursor rule
- oma-academic-writingSkill
- oma-architectureSkill
- oma-backendSkill
- oma-brainstormSkill
- oma-coordinationSkill
- oma-dbSkill
- oma-debugSkill
- oma-deepsecSkill
- oma-designSkill
- oma-dev-workflowSkill
- oma-docsSkill
- oma-explanationSkill
- oma-frontendSkill
- oma-hwpSkill
- oma-imageSkill
- oma-marketSkill
- oma-mobileSkill
- oma-observabilitySkill
- oma-orchestrationSkill
- oma-pdfSkill
- oma-pmSkill
- oma-qaSkill
- oma-recapSkill
- oma-refactorSkill
- oma-scholarSkill
- oma-scmSkill
- oma-searchSkill
- oma-skill-creationSkill
- oma-slideSkill
- oma-tf-infraSkill
- oma-translationSkill
- oma-videoSkill
- oma-voiceSkill
- architectureSkill
- brainstormSkill
- commitSkill
- convertSkill
- coordinate-proSkill
- coordinateSkill
- debugSkill
- deepinitSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

