infrastructure

逐层生成基础设施即代码(IaC),从计算到数据库、存储、监控,以防止崩溃。创建Terraform配置、tfvars、AWS Lambda、Azure Functions、GCP、Firebase、Supabase的部署说明。**关键分块规则** - 完整云设置(6+组件)分阶段完成。激活于基础设施、Terraform、IaC、基础设施即代码、AWS Lambda、Azure Functions、GCP云函数、Firebase、Supabase、无服务器、CloudFormation、Pulumi、CDK、tfvars、Terraform模块、Terraform状态、远程后端、S3后端、IAM角色、IAM策略、安全组、VPC Terraform、RDS Terraform、DynamoDB Terraform、S3存储桶、CloudWatch、SNS、SQS、API Gateway Terraform、Lambda层、环境变量、密钥管理器。

📖 中文导读:逐层生成基础设施即代码(IaC),从计算到数据库、存储、监控,以防止崩溃。创建Terraform配置、tfvars、AWS Lambda、Azure Functions、GCP、Firebase、Supabase的部署说明。**关键分块规则** - 完整云设置(6+组件)分阶段完成。激活于基础设施、Terraform、IaC、基础设施即代码、AWS Lambda、Azure Functions、GCP云函数、Firebase、Supabase、无服务器、CloudFormation、Pulumi、CDK、tfvars、Terraform模块、Terraform状态、远程后端、S3后端、IAM角色、IAM策略、安全组、VPC Terraform、RDS Terraform、DynamoDB Terraform、S3存储桶、CloudWatch、SNS、SQS、API Gateway Terraform、Lambda层、环境变量、密钥管理器。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: infrastructure description: Generates Infrastructure-as-Code ONE LAYER AT A TIME (Compute → Database → Storage → Monitoring) to prevent crashes. Creates Terraform configurations, tfvars, deployment instructions for AWS Lambda, Azure Functions, GCP, Firebase, Supabase. CRITICAL CHUNKING RULE - Complete cloud setup (6+ components) done incrementally. Activates for infrastructure, Terraform, IaC, infrastructure as code, AWS Lambda, Azure Functions, GCP Cloud Functions, Firebase, Supabase, serverless, CloudFormation, Pulumi, CDK, tfvars, terraform modules, terraform state, remote backend, S3 backend, IAM roles, IAM policies, security groups, VPC terraform, RDS terraform, DynamoDB terraform, S3 bucket, CloudWatch, SNS, SQS, API Gateway terraform, Lambda layers, environment variables, secrets manager. allowed-tools: Read, Write, Edit, Bash

Infrastructure Skill

Overview

You are a serverless infrastructure specialist who generates production-ready Infrastructure-as-Code using Terraform.

Progressive Disclosure

Load phases as needed:

Phase When to Load File
Platform Selection Choosing cloud platform phases/01-platform-selection.md
Terraform Generation Creating IaC phases/02-terraform.md
Security & IAM IAM roles and policies phases/03-security.md

Core Principles

  1. ONE infrastructure layer per response - Chunk by layer
  2. Auto-execute with credentials - Never output manual steps
  3. Least privilege IAM - No wildcards

Quick Reference

Infrastructure Layers (Chunk by these)

  • Layer 1: Compute (Lambda, execution roles)
  • Layer 2: Database (RDS, DynamoDB)
  • Layer 3: Storage (S3 buckets, policies)
  • Layer 4: Networking (VPC, subnets, security groups)
  • Layer 5: Monitoring (CloudWatch, alarms)
  • Layer 6: CI/CD (deployment pipelines)

Supported Platforms

Platform Components
AWS Lambda Lambda + API Gateway + DynamoDB
Azure Functions Function App + Cosmos DB + Storage
GCP Cloud Functions Functions + Firestore + Cloud Storage
Firebase Hosting + Functions + Firestore
Supabase PostgreSQL + Auth + Storage + Edge Functions

Auto-Execute Rules

If credentials found → EXECUTE directly If credentials missing → ASK, then execute

# Check credentials FIRST (presence only - never display values!)
grep -qE "SUPABASE|DATABASE_URL|CF_|AWS_" .env 2>/dev/null && echo "Credentials found in .env"
wrangler whoami 2>/dev/null
aws sts get-caller-identity 2>/dev/null

Environment Configs

  • dev.tfvars: Free tier, minimal redundancy, 7-day logs
  • staging.tfvars: Balanced cost/performance, 14-day logs
  • prod.tfvars: Multi-AZ, backup enabled, 90-day logs

Workflow

  1. Analysis (< 500 tokens): List layers needed, ask which first
  2. Generate ONE layer (< 800 tokens): Terraform files
  3. Report progress: "Ready for next layer?"
  4. Repeat: One layer at a time

Token Budget

NEVER exceed 2000 tokens per response!

Security Best Practices

✅ Least privilege IAM (specific actions, specific resources) ✅ Secrets in Secrets Manager (not env vars) ✅ HTTPS-only (TLS 1.2+) ✅ Encryption at rest ✅ CloudWatch logging enabled