Cloud Infrastructure as Code (Terraform / IaC)

What it does

/cloud-infra is a Cursor slash command. Type it in chat to run a saved workflow: Cloud Infrastructure as Code (Terraform / IaC).

Generates Terraform or AWS CDK infrastructure scripts for provisioning production cloud infrastructure with security and high availability.

Terraform scripts for AWS Aurora, S3 buckets, VPCs, and Cloudflare DNS. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /cloud-infra for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /cloud-infra exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Engineering Kit. It is wired to the Cloud Infrastructure Architect (cloud-architect) and DevOps & Deployment Pro (devops-engineer) agents. Required skills: Terraform Infrastructure as Code (IaC); Observability, Telemetry & SRE Monitoring.

When to use it

• Use when setting up databases, cloud storage buckets, or serverless infrastructure.
• Use /cloud-infra when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just wrote marketing copy.

When not to use it

• Do not run /cloud-infra as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Configure cloud provider authentication and remote state storage
2. Define modular infrastructure resources (VPC, database, storage buckets)
3. Set up security groups, IAM least-privilege roles, and encryption keys
4. Generate variables.tf and terraform.tfvars template files

Example usage

Type this in Cursor chat: /cloud-infra Write Terraform config for AWS Aurora Postgres serverless cluster and S3 assets bucket

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: terraform/main.tf
• Expected artifact: terraform/variables.tf
• Expected artifact: terraform/outputs.tf

Best practices

• Keep the prompt specific. /cloud-infra Write Terraform config for AWS Aurora Postgres serverless cluster and S3 assets bucket is the shape: object, constraint, and outcome.
• Let the listed agents work in order: cloud-architect → devops-engineer.
• Save outputs in the repo. Chat-only answers evaporate.
• Engineering commands should leave tests or an audit note, not only implementation files.

Common mistakes

• Typing /cloud-infra with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Terraform Infrastructure as Code (IaC) skill that the command depends on.