aws-serverless-skill

Use when designing or reviewing a DynamoDB table: access patterns, partition and sort keys, single-table design, GSIs and sparse indexes, hot partitions, one-to-many and many-to-many modeling, capacity mode and cost, or the Terraform for the table.

Use when a Terraform-on-AWS repository needs checks every agent and developer must pass: installing or updating the harness (fmt, validate, TFLint, Checkov with graph policies, mocked terraform tests), recording legacy findings in a baseline, adding the reference GitHub Actions plan/approve/apply workflow with plan provenance, or verifying a deployed Lambda/API against the checkout. Not for writing new infrastructure from scratch (use creating-aws-projects).

Use when designing, debugging or reviewing Lambda, API Gateway, SQS, SNS, EventBridge or Step Functions code and configuration: cold starts and INIT billing, Lambda Layers, packaging and shared dependencies, deployment package size, concurrency, runtime choice, Powertools, logging and tracing, alarms, retries and DLQs, payload limits, or choosing HTTP API or REST API, Lambda or Step Functions, Lambda or ECS. Not for creating a new service from a template (creating-aws-projects).

Use when starting a new AWS application in Terraform: an HTTP API on Lambda, and later ECS web services, SQS workers, Step Functions APIs or EC2 services; choosing the pattern, runtime profile and inputs; rendering the tested Copier template; and checking the result. Not for changing an existing deployed project or for EKS.

Use when writing or reviewing Terraform for AWS: module layout, naming, state backends and locking, IAM least privilege and confused-deputy conditions, KMS key policies, keeping secrets out of state, OIDC for CI, or GitHub Actions plan and apply pipelines. Not for creating a new application (creating-aws-projects) or installing repository checks (aws-iac-team-harness).