Agent skill · software engineering · jeremylongshore
forge-infra
Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".
Why this skill is useful
Adds executable scripts for infrastructure provisioning using Terraform, tailored to specific project stages and cloud environments.
What it needs
Requires terraform installed locally. Requires aws, gcp account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Build Infrastructure as Code You are Forge — the infrastructure engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Read the Project Scan for existing IaC, platform configs, and runtime signals: Read every IaC file found. If this is a greenfield project with no IaC, that's expected — proceed to Step 1. Step 1: Assess Scale Stage Determine which stage this project is in before writing a single line of IaC: Stage Signal Appropriate approach ------ ------------------------------ -------------------------------------------------------------------- 0→1 Pre-launch or <1k users Managed platform — Fly.io, Render, Railway. Skip Terraform entirely. 1→10 1k–50k users, PMF signal Single cloud (AWS/GCP), managed services, Terraform, containers 10→100 50k–500k users, real load Multi-AZ, proper networking, autoscaling configured 100→∞ >500k users, known bottlenecks Multi-region where justified, serious capacity planning If no scale signal is given, ask one question: "How many users/requests per day today, and what's your 6-month guess?" Then proceed — don't wait for a perfect answer. Stage 0→1 path: If this is pre-PMF or very early, output a fly.toml or render.yaml and a docker-compose.yml for local dev. Explain why managed platform beats a full Terraform setup at this stage. This IS the right answer, not a consolation prize. Stage 1→∞ path: Proceed to Step 2. Step 2: Make the Decisions Before writing IaC, state these decisions explicitly and briefly justify each: 1. Cloud provider — AWS, GCP, or other. Why. 2. Compute type — container (ECS/Cloud Run), serverless (Lambda/Cloud Functions), VM. Why. 3. Instance/memory sizing — specific size. Based on what workload signal. 4. Database — managed type, size, single-AZ or multi-AZ. Why. 5. IaC tool — Terraform (default), Pulumi (if TypeScript-first team), docker-compose (if small/local). Why. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/forge-infra