Skip to content

Cursor · DevOps

Cursor rules for Terraform

Terraform rules encode your module structure, naming and tagging conventions, state and workspace strategy, and which provider patterns you trust. They keep Cursor generating HCL that plans cleanly against your existing state instead of inventing incompatible resource shapes.

Every .cursorrules and .mdc file below targets Terraformand is quality-scored from automated signals — freshness, schema completeness, and review activity — not star counts you can game. Each listing carries its real GitHub author and SPDX license, so you know exactly what you're pasting into your repo and under what terms. That's the difference between this and an awesome-cursor-rules link dump: here a stale or broken Terraform rule sinks to the bottom instead of sitting at the top because someone starred it in 2024.

Top Terraform Cursor rules by quality score

No Terraform Cursor rules published yet during beta — but the catalog is filling fast. The install guide below works for any Terraform rule, and you can be the first to publish one:

How to install a Terraform .mdc rule

  1. 1. Pick a rule above

    Open the highest quality-scored Terraform listing and read the preview — make sure its conventions match your stack before you copy it.

  2. 2. Choose a location

    Project-wide rules go in .cursorrules at your repo root. Scoped rules go in .cursor/rules/terraform.mdc and attach to file globs.

  3. 3. Paste and scope it

    Drop the contents in. For a .mdc file, set the frontmatter globs (e.g. globs: "**/*.ts") so Cursor auto-attaches it only for Terraform files.

  4. 4. Reload Cursor

    Reload the Cursor window so the rule is loaded, then confirm it appears under Settings → Rules in your active context.

# Project-wide rule
cp terraform.cursorrules ./.cursorrules

# Or a scoped .mdc rule (auto-attaches by glob):
mkdir -p .cursor/rules
cat > .cursor/rules/terraform.mdc <<'EOF'
---
description: Terraform project conventions
globs: "**/*"
alwaysApply: false
---
# ...paste the rule body here...
EOF

Terraform Cursor rules — frequently asked

What's the best Cursor rule for Terraform?

The best Terraform Cursor rule is the one that encodes your project's conventions — not a generic one-size-fits-all file. On RuleSell, Terraform rules are ranked by quality score (freshness, schema completeness, and review signals), so the top of this page is a defensible starting point. Open the highest-scored listing, then trim it to match your stack.

Where do Terraform .cursorrules files go?

Put a project-wide rule in a .cursorrules file at your repo root. For scoped rules, create .cursor/rules/terraform.mdc and attach it to the relevant file globs (for example **/*.ts) so Cursor only loads it when you're editing matching Terraform files. Commit both to git so your whole team gets the same context.

Do these Terraform rules work in Windsurf or Claude Code too?

Often, yes. A plain-markdown Terraform rule frequently works as-is in Windsurf (rename to .windsurfrules) and as project context for Claude Code (paste into CLAUDE.md). RuleSell dual-tags listings that are verified compatible across environments.

Are these Terraform Cursor rules free?

Yes — every listing is free to download during beta. Each Terraform rule keeps its original GitHub author attribution and SPDX license, so you always know the provenance. Paid publishing with creator payouts opens after beta.

More on RuleSell