[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A31XWRMPDJV9WD1S9PE6RN":3,"skill-same:01M7A31XWRMPDJV9WD1S9PE6RN":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7A31XWRMPDJV9WD1S9PE6RN","amplify-app-deployer",null,"Provisions AWS Amplify applications with production defaults: Git-based deployments (CodeCommit, GitHub, GitLab, Bitbucket) with OAuth or service-role connection, build settings (amplify.yml buildspec with frontend and backend phases), custom headers, redirects (SPA rewrite for React Router \u002F Next.js), environment variables (plaintext and AWS Secrets Manager references), custom domain via Route 53 CNAME or CloudFront, rendering mode (SSR vs SSG vs SPA), Amplify Backend (auth with Cognito, API with AppSync GraphQL or REST, storage with S3, functions with Lambda), CI\u002FCD pipeline on every git push, branch-based environments, and the latest Amplify Gen 2 (TypeScript CDK-based defineBackend). Emits a READY_TO_DEPLOY checklist with prerequisites, build config, and verification commands. Use when creating an Amplify app, wiring a Git provider, configuring a custom domain, designing SSR\u002FSSG, deploying Amplify Gen 2, or generating provisioning CLI \u002F IaC templates.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: amplify-app-deployer\ndescription: 'Provisions AWS Amplify applications with production defaults: Git-based deployments (CodeCommit, GitHub, GitLab, Bitbucket) with OAuth or service-role connection, build settings (amplify.yml buildspec with frontend and backend phases), custom headers, redirects (SPA rewrite for React Router \u002F Next.js), environment variables (plaintext and AWS Secrets Manager references), custom domain via Route 53 CNAME or CloudFront, rendering mode (SSR vs SSG vs SPA), Amplify Backend (auth with Cognito, API with AppSync GraphQL or REST, storage with S3, functions with Lambda), CI\u002FCD pipeline on every git push, branch-based environments, and the latest Amplify Gen 2 (TypeScript CDK-based defineBackend). Emits a READY_TO_DEPLOY checklist with prerequisites, build config, and verification commands. Use when creating an Amplify app, wiring a Git provider, configuring a custom domain, designing SSR\u002FSSG, deploying Amplify Gen 2, or generating provisioning CLI \u002F IaC templates.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with amplify, cloudfront, route53, iam, secretsmanager, cognito-idp, appsync, lambda, s3, and codeconnections access. Works with Terraform aws_amplify_app \u002F aws_amplify_branch \u002F aws_amplify_domain_association resources, CloudFormation AWS::Amplify::App templates, and the Amplify Gen 2 TypeScript CDK backend (amplify defineBackend).'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: DevTools\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, amplify, devtools, deploy, cicd, git, codecommit, github, frontend, serverless\n  dependencies: aws-orchestrator\n  keywords: aws, amplify, amplify gen 2, git-based deploy, codecommit, github, gitlab, bitbucket, buildspec, amplify.yml, custom headers, redirects, SPA rewrite, environment variables, custom domain, route 53, cloudfront, SSR, SSG, SPA, amplify backend, cognito auth, appsync api, lambda functions, s3 storage, cicd pipeline, branch environments, cloudops, deploy, devtools\n  when_to_use: Invoke when the user wants to create a new Amplify application, wire a Git provider (CodeCommit, GitHub, GitLab, Bitbucket) for CI\u002FCD, configure a custom domain via Route 53 \u002F CloudFront, design SSR vs SSG vs SPA rendering, deploy an Amplify Gen 2 (TypeScript CDK-based) backend, wire Cognito auth \u002F AppSync API \u002F S3 storage \u002F Lambda functions, configure buildspec.yml (amplify.yml), set custom headers \u002F redirects (SPA rewrite), manage environment variables, or generate provisioning CLI commands \u002F IaC templates. Do NOT invoke for self-managed Next.js on EC2 \u002F ECS \u002F Fargate, CloudFront static site without Amplify, or AppSync-only deployments without the Amplify build pipeline.\n---\n\n# Amplify App Deployer\n\nAn AWS CloudOps agent skill that provisions Amplify applications with\ncorrect defaults across Git provider, rendering mode, build settings,\ncustom domain, backend, and CI\u002FCD. The skill walks a 10-step\nprovisioning procedure, captures the operator's framework, Git, and\nbackend decisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## What this skill does\n\nProvisions Amplify applications with production-grade defaults across\nGit-based deployments (CodeCommit \u002F GitHub \u002F GitLab \u002F Bitbucket),\nrendering mode (SSR \u002F SSG \u002F SPA), build settings (amplify.yml), custom\nheaders and redirects, environment variables, custom domain (Route 53 \u002F\nCloudFront), Amplify Backend (auth, API, storage, functions), and CI\u002FCD\npipeline on every git push. The output is a READY_TO_DEPLOY checklist\nwith verification commands.\n\n## STRICT output contract\n\nWhen this skill is invoked with an app-provisioning request (app name,\nframework, Git provider, region, or a partial configuration), the agent\nMUST respond with the READY_TO_DEPLOY checklist defined in §\"Output\nformat\" using the literal all-caps labels `APP:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and\ndownstream provisioning pipelines rely on; deviating from the literal\nlabels breaks automation silently.\n\n## Mindset\n\n**One-line takeaway:** Amplify is Git-driven infra — every push triggers\na build, every branch is an environment, and the buildspec is the source\nof truth for build, env vars, and redirects. Get the buildspec right at\ncreation; retrofitting it later causes silent deploy failures.\n\nThree behaviours separate a senior Amplify engineer from a generalist:\n\nSenior-engineer behaviours (buildspec as source of truth; rendering mode;\nDNS validation before cert issue): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Philosophy\n\nProvisioning philosophy (Gen 2 over Gen 1; branch environments; Secrets\nManager env vars; committed headers): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| §\"Prerequisites\" | Always — verify before provisioning |\n| §\"Step 1 — Git provider\" | CodeCommit \u002F GitHub \u002F GitLab \u002F Bitbucket |\n| §\"Step 2 — Framework + rendering mode\" | SSR vs SSG vs SPA |\n| §\"Step 3 — Build settings (amplify.yml)\" | buildspec, phases, cache |\n| §\"Step 4 — Environment variables\" | plaintext + Secrets Manager |\n| §\"Step 5 — Custom headers + redirects\" | SPA rewrite, security headers |\n| §\"Step 6 — Custom domain\" | Route 53 \u002F CloudFront \u002F ACM cert |\n| §\"Step 7 — Amplify Backend (Gen 2)\" | auth, API, storage, functions |\n| §\"Step 8 — CI\u002FCD pipeline\" | branch builds, preview URLs |\n| §\"Step 9 — Amplify Gen 2 latest features\" | TypeScript CDK backend |\n| §\"NEVER do these things\" | Review before signing off |\n| §\"Output format\" | The literal checklist template |\n| references\u002Fbuild-and-domain-reference.md | Deep buildspec + domain |\n| references\u002Fbackend-gen2-reference.md | Gen 2 backend patterns |\n\n## Reasoning framework (why provisioning order matters)\n\nAmplify configurations have **dependency and Git-binding semantics**\nthat make the provisioning order non-trivial:\n\n1. **Git provider BEFORE the app** — Amplify needs a repo connected to\n   trigger builds. The connection (OAuth for GitHub, service role for\n   CodeCommit) must exist before `create-app`.\n2. **Framework BEFORE build settings** — Next.js SSR needs\n   `amplify.yml`'s SSR-aware build phase; a static SPA needs a plain\n   `npm run build` and rewrite rule.\n3. **Build settings BEFORE the first push** — `amplify.yml` committed\n   to the repo is read on the first build. A missing buildspec defaults\n   to Amplify's framework auto-detection, which often misses custom\n   phases.\n4. **Backend BEFORE frontend env vars** — the frontend needs to know\n   the API URL, Cognito user pool ID, etc. These come from the backend\n   stack (Gen 2 `defineBackend` outputs).\n5. **Custom domain AFTER the first successful build** — Amplify issues\n   the domain cert after the app is live on the default\n   `*.amplifyapp.com` URL. Adding the domain before the first build\n   produces a cert for a non-functional app.\n\n## Amplify configuration dependency graph (novel heuristic)\n\n| Configuration | Binding | Effect of wrong order |\n|---|---|\n| Git provider connection | OAuth \u002F service role | `create-app` fails without `--repository` and a valid token |\n| Framework detection | `amplify.yml` buildSpec | Wrong framework = wrong build command = silent 500 on the URL |\n| Rendering mode (SSR\u002FSSG\u002FSPA) | `next.config.js` + Amplify | SSR-as-SPA = 404 on dynamic routes; SSG-as-SSR = wasted compute |\n| Environment variables | Per-branch | A var on `main` does NOT appear on `staging`; secrets should be Secrets Manager refs |\n| Custom headers + redirects | `amplify.yml` (committed) | Console-config set is overwritten on next push |\n| Custom domain | ACM cert + DNS validation | Cert stuck in PENDING if DNS CNAME missing |\n| Backend (Gen 2) | `amplify\u002Fbackend.ts` (CDK) | Backend deploy must run in the build phase via `ampx pipeline-deploy` |\n| Branch environments | Per-branch URL | PR previews only if branch detection is on |\n\n**Cross-dependency gotchas:**\nFull catalog (SSR compute role, third-party DNS validation, ampx IAM\n+ CDK bootstrap): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: rendering mode cost and latency\n\nThe rendering mode decides cost, cold-start, and SEO behavior. Pick by\nthe actual workload, not by framework default.\n\n| Mode | When to use | Cost | Cold start | SEO |\n|---|---|---|---|---|\n| **SSG** (static export) | Marketing site, docs, blog — content known at build | Build-time only | None (CDN) | Excellent |\n| **SSR** (server-side render at request) | Personalized dashboards, auth-gated apps, A\u002FB tests | Per-request compute | 50-200ms (managed) | Good (rendered HTML) |\n| **SPA** (client-side render) | Internal tools, SaaS dashboards behind login | Build-time only | None (CDN) | Poor (JS-rendered) |\n| **ISR** (incremental static regen) | E-commerce catalog, news with periodic rebuild | Build + periodic | None for cached | Excellent |\n\n**Common mistake:** defaulting to SSR for a marketing site. SSR\ncompute is billed per-request; a static marketing site pays for compute\nit does not need. Use SSG (`output: 'export'` in Next.js) for content\nsites. Use SSR only when the HTML differs per user \u002F per request.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING** with a\nspecific gap citation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account with Amplify access | Can't provision without it | `aws sts get-caller-identity` |\n| Region selected | Amplify apps are region-scoped | `aws configure get region` |\n| Git repo (CodeCommit \u002F GitHub \u002F GitLab \u002F Bitbucket) with `amplify.yml` | Amplify builds from a connected repo | `git remote -v`; check `amplify.yml` exists at repo root |\n| Git provider connection (OAuth token or CodeConnections service role) | Amplify needs read access to the repo | For GitHub: PAT with `repo` scope; for CodeCommit: `aws codeconnections list-connections` |\n| ACM certificate in us-east-1 (for custom domain) | Amplify custom domains use ACM | `aws acm list-certificates --region us-east-1` |\n| Route 53 hosted zone (for Route 53-managed domain) | Custom domain DNS | `aws route53 list-hosted-zones` |\n| Backend stack artifacts (for Gen 2: `amplify\u002Fbackend.ts`; CDK bootstrap) | Backend deploy runs in the build phase | Check `amplify\u002Fbackend.ts` exists; `aws cloudformation describe-stacks --stack-name CDKToolkit` |\n| Framework directive decided (SSR \u002F SSG \u002F SPA) | Drives buildspec + redirect rules | Captured in the prompt or follow-up |\n| Service role for Amplify (auto-created or existing) | Amplify assumes a role to access CodeCommit \u002F Secrets Manager | `aws iam get-role --role-name AWSAmplifyServiceRole` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## 10-step provisioning procedure\n\n### Step 1 — Git provider (binding decision — BEFORE create-app)\n\nAmplify supports CodeCommit, GitHub, GitLab, and Bitbucket. The\nprovider determines the connection method.\n\n**Decision tree:**\n\n```text\nIs the repo in AWS CodeCommit?\n├── YES → CodeCommit  (service role via CodeConnections)\n└── NO → Which provider?\n    ├── GitHub → GitHub  (OAuth PAT or GitHub App; CodeConnections)\n    ├── GitLab → GitLab  (access token; CodeConnections)\n    └── Bitbucket → Bitbucket  (app password; CodeConnections)\n```\n\n**Connection setup (GitHub example):**\n\n```bash\n# Create a CodeConnections connection (formerly CodeStar connection)\naws codeconnections create-connection \\\n  --provider-type GitHub \\\n  --connection-name github-amplify \\\n  --output json\n# Then complete the OAuth handshake in the Console to set the connection\n# status to AVAILABLE.\n```\n\n**Common mistake:** trying to use a personal access token (PAT) without\nthe `repo` scope. The Amplify build fails on `git clone` with a 401.\nUse a CodeConnections connection for GitHub \u002F GitLab \u002F Bitbucket; the\nconnection re-auths automatically.\n\n### Step 2 — Framework + rendering mode (drives buildspec)\n\nThe framework directive determines the build phase, the output directory,\nand the redirect rules.\n\n| Framework | SSR support | Build command | Output dir |\n|---|---|---|---|\n| Next.js (SSR) | YES (Amplify SSR compute) | `npm run build` | `.next` (Amplify auto-detects SSR) |\n| Next.js (SSG) | `output: 'export'` in next.config | `npm run build` | `out` |\n| React (Vite) | SPA | `npm run build` | `dist` |\n| React (CRA) | SPA | `npm run build` | `build` |\n| Vue \u002F Nuxt | SSR (Nuxt) or SPA (Vue) | `npm run build` | `.output` (Nuxt) or `dist` (Vue) |\n| Angular | SPA | `npm run build` | `dist\u002F\u003Cproject>` |\n| Svelte \u002F SvelteKit | SSR \u002F SPA | `npm run build` | `build` |\n\n**Common mistake:** declaring SSR in `next.config.js` but deploying as\nSPA. The framework directive must match the Amplify framework setting.\nFor Next.js SSR, Amplify auto-provisions the SSR compute role on first\ndeploy — do not delete it.\n\n### Step 3 — Build settings (amplify.yml buildspec)\n\nThe `amplify.yml` file at repo root is the buildspec. It defines\nfrontend and backend phases, cache, env vars, and output artifacts.\n\n**Canonical `amplify.yml` (Next.js + Gen 2 backend):**\n\n```yaml\nversion: 1\nfrontend:\n  phases:\n    preBuild:\n      commands:\n        - npm ci\n    build:\n      commands:\n        - npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID\n        - npm run build\n  artifacts:\n    baseDirectory: .next\n    files:\n      - '**\u002F*'\n  cache:\n    paths:\n      - node_modules\u002F**\u002F*\n  customHeaders:\n    - pattern: '**\u002F*'\n      headers:\n        - key: Strict-Transport-Security\n          value: 'max-age=31536000; includeSubDomains'\n        - key: X-Content-Type-Options\n          value: 'nosniff'\n        - key: X-Frame-Options\n          value: 'DENY'\n  redirects:\n    - source: '\u002F\u003C*>'\n      target: '\u002Findex.html'\n      status: 200\n      condition: null\n```\n\n**SPA rewrite rule:** the `redirects` section with `status: 200` rewrites\nall paths to `\u002Findex.html` for client-side routing (React Router, Vue\nRouter). Without this, refreshing `\u002Fusers\u002F123` returns 404.\n\n**Cache:** `node_modules` caching speeds up builds. Pin the lockfile\n(`npm ci` not `npm install`) for reproducible builds.\n\n### Step 4 — Environment variables\n\nEnv vars are branch-scoped. Set them via the Console, CLI, or\n`amplify.yml` `env:`.\n\n```bash\n# Plaintext env var on a specific branch\naws amplify update-app \\\n  --app-id dXXXX \\\n  --environment-variables platform=web,apiUrl=https:\u002F\u002Fapi.example.com \\\n  --output json\n\n# Secrets Manager reference (for API keys, DB credentials)\naws amplify update-app \\\n  --app-id dXXXX \\\n  --custom-rules source=SECRET_API_KEY,target=arn:aws:secretsmanager:us-east-1:111:secret:api-key-XXX \\\n  --output json\n```\n\n**Common mistake:** setting a secret as a plaintext env var. Plaintext\nenv vars are visible in the Console and in `amplify.yml` if committed.\nUse Secrets Manager references for anything sensitive — Amplify reads\nthe secret value at build time, never logs it.\n\n### Step 5 — Custom headers + redirects\n\nCustom headers (security headers, CORS) and redirects (SPA rewrite,\nlegacy URL redirects) live in `amplify.yml`.\n\nFull customHeaders + redirects YAML (HSTS, CSP, 301s, SPA rewrite):\n[references\u002Fbuild-and-domain-reference.md](references\u002Fbuild-and-domain-reference.md).\n\n**Common mistake:** Console-configuring headers and redirects. They are\noverwritten on the next push that includes `amplify.yml`. Always commit.\n\n### Step 6 — Custom domain (Route 53 \u002F CloudFront)\n\nA custom domain uses an ACM certificate with DNS validation.\n\nACM cert request + domain-association commands:\n[references\u002Fbuild-and-domain-reference.md](references\u002Fbuild-and-domain-reference.md).\n\n**Route 53 automatic validation:** if the hosted zone for\n`example.com` is in the same account, ACM auto-writes the validation\nCNAME. For third-party DNS (GoDaddy, Namecheap), copy the CNAME\nmanually.\n\n**Common mistake:** requesting the cert in a region other than\n`us-east-1`. Amplify custom domains require the cert in us-east-1\nregardless of where the app is deployed.\n\n### Step 7 — Amplify Backend (Gen 2 TypeScript CDK)\n\nAmplify Gen 2 uses `amplify\u002Fbackend.ts` with `defineBackend` — fully\nCDK-based, no `amplify init` \u002F `amplify push`.\n\n```typescript\n\u002F\u002F amplify\u002Fbackend.ts\nimport { defineBackend } from '@aws-amplify\u002Fbackend';\nimport { auth } from '.\u002Fauth\u002Fresource';\nimport { data } from '.\u002Fdata\u002Fresource';\nimport { storage } from '.\u002Fstorage\u002Fresource';\n\nexport const backend = defineBackend({\n  auth,\n  data,\n  storage,\n});\n```\n\nGen 2 backend resource catalog (auth\u002Fdata\u002Fstorage\u002Ffunctions) + build-phase\npipeline-deploy contract: [references\u002Fbackend-gen2-reference.md](references\u002Fbackend-gen2-reference.md).\n\n**Common mistake:** running `ampx push` (sandbox mode) in CI instead of\n`ampx pipeline-deploy`. Sandbox mode is for local dev; CI uses\n`pipeline-deploy` which reads the branch and app ID from Amplify env\nvars.\n\n### Step 8 — CI\u002FCD pipeline (branch builds, preview URLs)\n\nAmplify builds on every git push. Each branch gets its own URL.\n\n```bash\n# Enable PR previews (builds every PR branch)\naws amplify update-branch \\\n  --app-id dXXXX \\\n  --branch-name main \\\n  --pull-request-environment-name main \\\n  --output json\n\n# Set up a staging branch environment\naws amplify create-branch \\\n  --app-id dXXXX \\\n  --branch-name staging \\\n  --stage PRODUCTION \\\n  --output json\n```\n\n**Branch environments:**\n- `main` → production URL (`app.example.com`)\n- `staging` → staging URL (`staging.example.com` or\n  `staging.dXXXX.amplifyapp.com`)\n- PR branches → preview URL (`pr123.dXXXX.amplifyapp.com`)\n\n### Step 9 — Amplify Gen 2 latest features (2024-2026)\n\nGen 2 feature detail (CDK backend, branch backends, build image, SSR\nroles, Secrets Manager, Studio): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n### Step 10 — Transit \u002F networking edge cases\n\nTransit\u002Fnetworking edge cases (no VPC attachment, NAT for private\nbackends, second CloudFront): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things (top 5)\n\n1. **NEVER configure custom headers, redirects, or env vars only in\n   the Console.** Console-configured values are overwritten on the\n   next push that includes `amplify.yml`. Always commit `amplify.yml`\n   with customHeaders, redirects, and env-var references.\n\n2. **NEVER request the ACM certificate for a custom domain in a region\n   other than us-east-1.** Amplify custom domains require the cert in\n   us-east-1 regardless of where the app is deployed. A cert in\n   us-east-2 cannot be attached.\n\n3. **NEVER use `ampx push` (sandbox) in the CI build phase.** Sandbox\n   mode is for local dev with hot reload. CI uses\n   `npx ampx pipeline-deploy --branch $AWS_BRANCH` which deploys the\n   branch-specific backend stack.\n\n4. **NEVER deploy a Next.js SSR app as a SPA without the rewrite rule.**\n   SSR-as-SPA produces 404 on dynamic routes (`\u002Fusers\u002F[id]`). Either\n   use SSR (Amplify auto-detects) or SSG (`output: 'export'`) with a\n   `\u002F\u003C*> -> \u002Findex.html status 200` rewrite.\n\n5. **NEVER store secrets as plaintext environment variables.** Plaintext\n   env vars are visible in the Console and in `amplify.yml` if\n   committed. Use Secrets Manager references — Amplify reads the secret\n   at build time via the service role.\n\n**Additional critical mistakes:** never run one big `main` branch (use\nbranch previews); never assume env vars propagate across branches (they\nare branch-scoped); never delete the auto-created SSR compute role for\nNext.js SSR apps; never skip CDK bootstrap before the first Gen 2\nbackend deploy; never forget to validate the domain DNS CNAME before\nthe cert issues; never use `npm install` in CI (use `npm ci` for\nreproducibility); never configure a second CloudFront in front of\nAmplify without a documented reason (Amplify already fronts the app).\n\n## Output format\n\n```text\nAPP: \u003Capp-name>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Git provider: \u003CCodeCommit | GitHub | GitLab | Bitbucket> (connection: \u003COAuth | service role>)\n  [✓|✗] Repository: \u003Crepo-url> (amplify.yml committed: YES | NO)\n  [✓|✗] Framework: \u003CNext.js | React | Vue | Angular | Svelte> (version)\n  [✓|✗] Rendering mode: \u003CSSR | SSG | SPA | ISR>\n  [✓|✗] Build settings: \u003Camplify.yml phases: preBuild, build, postBuild>\n  [✓|✗] Environment variables: \u003CN plaintext, M Secrets Manager refs>\n  [✓|✗] Custom headers: \u003CHSTS, CSP, X-Frame-Options, ...>\n  [✓|✗] Redirects: \u003CSPA rewrite \u002F\u003C*> -> \u002Findex.html status 200; legacy 301s>\n  [✓|✗] Custom domain: \u003Cdomain> (ACM cert \u003Carn> in us-east-1; DNS validated: YES | NO)\n  [✓|✗] Backend (Gen 2): \u003Cauth Cognito, data AppSync, storage S3, functions Lambda>\n  [✓|✗] CI\u002FCD: \u003Cbranch builds on every push; preview URLs on PRs>\n  [✓|✗] Branch environments: \u003Cmain=prod, staging=staging, PR=preview>\nVERIFICATION_COMMANDS:\n  aws amplify get-app --app-id \u003Cid>\n  aws amplify list-branches --app-id \u003Cid>\n  aws amplify get-domain-association --app-id \u003Cid> --domain-name \u003Cdomain>\n  aws acm describe-certificate --certificate-arn \u003Carn> --region us-east-1\n```\n\n### Worked example — Next.js SSR with Gen 2 backend\n\n```text\nAPP: prod-web\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Git provider: GitHub (connection: CodeConnections github-amplify, AVAILABLE)\n  [✓] Repository: github.com\u002Fexample\u002Fprod-web (amplify.yml committed: YES)\n  [✓] Framework: Next.js 14\n  [✓] Rendering mode: SSR (Amplify auto-provisions SSR compute role)\n  [✓] Build settings: amplify.yml (preBuild: npm ci; build: ampx pipeline-deploy + npm run build)\n  [✓] Environment variables: 3 plaintext (API_URL, NODE_ENV, NEXT_PUBLIC_API_URL), 1 Secrets Manager ref (STRIPE_SECRET_KEY)\n  [✓] Custom headers: HSTS, X-Content-Type-Options nosniff, X-Frame-Options DENY, CSP default-src 'self'\n  [✓] Redirects: \u002F\u003C*> -> \u002Findex.html status 200 (SPA fallback for static routes)\n  [✓] Custom domain: app.example.com (ACM cert arn:aws:acm:us-east-1:111:certificate\u002Fabc in us-east-1; DNS validated: YES via Route 53)\n  [✓] Backend (Gen 2): auth Cognito (user pool + identity pool), data AppSync GraphQL, storage S3 (per-user prefixes)\n  [✓] CI\u002FCD: branch builds on every push; preview URLs on PRs\n  [✓] Branch environments: main=app.example.com, staging=staging.example.com, PR=pr\u003CN>.dXXXX.amplifyapp.com\nVERIFICATION_COMMANDS:\n  aws amplify get-app --app-id dXXXX\n  aws amplify list-branches --app-id dXXXX\n  aws amplify get-domain-association --app-id dXXXX --domain-name example.com\n  aws acm describe-certificate --certificate-arn arn:aws:acm:us-east-1:111:certificate\u002Fabc --region us-east-1\n```\n\nFurther worked examples (React SPA static site; PREREQUISITES_MISSING with\nno Git provider \u002F no amplify.yml): [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n\n## Error handling\n\nError-to-cause-to-fix table (repo access, ampx missing, SSR role, cert\ntimeout, CDK bootstrap, 404s): [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## Recent AWS features (2024-2026)\n\nRecent AWS features (2024-2026) — Gen 2, branch backends, Secrets\nManager, Node 20, Studio, CodeConnections: [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## References (load on demand)\n\n- [Worked examples](references\u002Fworked-examples.md) - further checklists: React SPA static site; PREREQUISITES_MISSING (no Git provider \u002F no amplify.yml)\n- [Error handling](references\u002Ferror-handling.md) - error-to-cause-to-fix table: repo access, ampx missing, SSR role, cert validation, CDK bootstrap, branch-scoped env vars, 404s\n- [Advanced patterns](references\u002Fadvanced-patterns.md) - senior-engineer behaviours, philosophy tenets, cross-dependency gotchas, Gen 2 features, networking edge cases, recent AWS features\n- [Build and domain reference](references\u002Fbuild-and-domain-reference.md) - deep buildspec + domain detail: custom headers\u002Fredirects YAML, ACM cert request + domain association commands\n- [Gen 2 backend reference](references\u002Fbackend-gen2-reference.md) - Gen 2 backend patterns: resource catalog, pipeline-deploy build-phase contract\n\n## Domain\n\nAWS CloudOps \u002F Amplify Application Provisioning, Git-Based CI\u002FCD,\nFrontend Hosting, and Serverless Backend Design.\n\n## AWS documentation\n\n- **AWS Amplify Hosting User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fwelcome.html\n- **Amplify Gen 2 Documentation** — https:\u002F\u002Fdocs.amplify.aws\u002Fgen2\u002F\n- **Amplify custom domains** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fcustom-domains.html\n- **Amplify buildspec (amplify.yml)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fbuild-settings.html\n- **Amplify redirects** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fredirects.html\n- **CodeConnections** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcodeconnections\u002Flatest\u002Fuserguide\u002Fwelcome.html\n- **AWS CLI Amplify reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Famplify\u002F\n- **Amplify SSR for Next.js** — https:\u002F\u002Fdocs.amplify.aws\u002Fgen2\u002Fdeploy-and-host\u002Ffullstack-branching-deployments\u002Fnextjs-app-router\u002F\n","# Amplify App Deployer\n\nAn AWS CloudOps agent skill that provisions Amplify applications with\ncorrect defaults across Git provider, rendering mode, build settings,\ncustom domain, backend, and CI\u002FCD. The skill walks a 10-step\nprovisioning procedure, captures the operator's framework, Git, and\nbackend decisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## What this skill does\n\nProvisions Amplify applications with production-grade defaults across\nGit-based deployments (CodeCommit \u002F GitHub \u002F GitLab \u002F Bitbucket),\nrendering mode (SSR \u002F SSG \u002F SPA), build settings (amplify.yml), custom\nheaders and redirects, environment variables, custom domain (Route 53 \u002F\nCloudFront), Amplify Backend (auth, API, storage, functions), and CI\u002FCD\npipeline on every git push. The output is a READY_TO_DEPLOY checklist\nwith verification commands.\n\n## STRICT output contract\n\nWhen this skill is invoked with an app-provisioning request (app name,\nframework, Git provider, region, or a partial configuration), the agent\nMUST respond with the READY_TO_DEPLOY checklist defined in §\"Output\nformat\" using the literal all-caps labels `APP:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and\ndownstream provisioning pipelines rely on; deviating from the literal\nlabels breaks automation silently.\n\n## Mindset\n\n**One-line takeaway:** Amplify is Git-driven infra — every push triggers\na build, every branch is an environment, and the buildspec is the source\nof truth for build, env vars, and redirects. Get the buildspec right at\ncreation; retrofitting it later causes silent deploy failures.\n\nThree behaviours separate a senior Amplify engineer from a generalist:\n\nSenior-engineer behaviours (buildspec as source of truth; rendering mode;\nDNS validation before cert issue): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Philosophy\n\nProvisioning philosophy (Gen 2 over Gen 1; branch environments; Secrets\nManager env vars; committed headers): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| §\"Prerequisites\" | Always — verify before provisioning |\n| §\"Step 1 — Git provider\" | CodeCommit \u002F GitHub \u002F GitLab \u002F Bitbucket |\n| §\"Step 2 — Framework + rendering mode\" | SSR vs SSG vs SPA |\n| §\"Step 3 — Build settings (amplify.yml)\" | buildspec, phases, cache |\n| §\"Step 4 — Environment variables\" | plaintext + Secrets Manager |\n| §\"Step 5 — Custom headers + redirects\" | SPA rewrite, security headers |\n| §\"Step 6 — Custom domain\" | Route 53 \u002F CloudFront \u002F ACM cert |\n| §\"Step 7 — Amplify Backend (Gen 2)\" | auth, API, storage, functions |\n| §\"Step 8 — CI\u002FCD pipeline\" | branch builds, preview URLs |\n| §\"Step 9 — Amplify Gen 2 latest features\" | TypeScript CDK backend |\n| §\"NEVER do these things\" | Review before signing off |\n| §\"Output format\" | The literal checklist template |\n| references\u002Fbuild-and-domain-reference.md | Deep buildspec + domain |\n| references\u002Fbackend-gen2-reference.md | Gen 2 backend patterns |\n\n## Reasoning framework (why provisioning order matters)\n\nAmplify configurations have **dependency and Git-binding semantics**\nthat make the provisioning order non-trivial:\n\n1. **Git provider BEFORE the app** — Amplify needs a repo connected to\n   trigger builds. The connection (OAuth for GitHub, service role for\n   CodeCommit) must exist before `create-app`.\n2. **Framework BEFORE build settings** — Next.js SSR needs\n   `amplify.yml`'s SSR-aware build phase; a static SPA needs a plain\n   `npm run build` and rewrite rule.\n3. **Build settings BEFORE the first push** — `amplify.yml` committed\n   to the repo is read on the first build. A missing buildspec defaults\n   to Amplify's framework auto-detection, which often misses custom\n   phases.\n4. **Backend BEFORE frontend env vars** — the frontend needs to know\n   the API URL, Cognito user pool ID, etc. These come from the backend\n   stack (Gen 2 `defineBackend` outputs).\n5. **Custom domain AFTER the first successful build** — Amplify issues\n   the domain cert after the app is live on the default\n   `*.amplifyapp.com` URL. Adding the domain before the first build\n   produces a cert for a non-functional app.\n\n## Amplify configuration dependency graph (novel heuristic)\n\n| Configuration | Binding | Effect of wrong order |\n|---|---|\n| Git provider connection | OAuth \u002F service role | `create-app` fails without `--repository` and a valid token |\n| Framework detection | `amplify.yml` buildSpec | Wrong framework = wrong build command = silent 500 on the URL |\n| Rendering mode (SSR\u002FSSG\u002FSPA) | `next.config.js` + Amplify | SSR-as-SPA = 404 on dynamic routes; SSG-as-SSR = wasted compute |\n| Environment variables | Per-branch | A var on `main` does NOT appear on `staging`; secrets should be Secrets Manager refs |\n| Custom headers + redirects | `amplify.yml` (committed) | Console-config set is overwritten on next push |\n| Custom domain | ACM cert + DNS validation | Cert stuck in PENDING if DNS CNAME missing |\n| Backend (Gen 2) | `amplify\u002Fbackend.ts` (CDK) | Backend deploy must run in the build phase via `ampx pipeline-deploy` |\n| Branch environments | Per-branch URL | PR previews only if branch detection is on |\n\n**Cross-dependency gotchas:**\nFull catalog (SSR compute role, third-party DNS validation, ampx IAM\n+ CDK bootstrap): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: rendering mode cost and latency\n\nThe rendering mode decides cost, cold-start, and SEO behavior. Pick by\nthe actual workload, not by framework default.\n\n| Mode | When to use | Cost | Cold start | SEO |\n|---|---|---|---|---|\n| **SSG** (static export) | Marketing site, docs, blog — content known at build | Build-time only | None (CDN) | Excellent |\n| **SSR** (server-side render at request) | Personalized dashboards, auth-gated apps, A\u002FB tests | Per-request compute | 50-200ms (managed) | Good (rendered HTML) |\n| **SPA** (client-side render) | Internal tools, SaaS dashboards behind login | Build-time only | None (CDN) | Poor (JS-rendered) |\n| **ISR** (incremental static regen) | E-commerce catalog, news with periodic rebuild | Build + periodic | None for cached | Excellent |\n\n**Common mistake:** defaulting to SSR for a marketing site. SSR\ncompute is billed per-request; a static marketing site pays for compute\nit does not need. Use SSG (`output: 'export'` in Next.js) for content\nsites. Use SSR only when the HTML differs per user \u002F per request.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING** with a\nspecific gap citation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account with Amplify access | Can't provision without it | `aws sts get-caller-identity` |\n| Region selected | Amplify apps are region-scoped | `aws configure get region` |\n| Git repo (CodeCommit \u002F GitHub \u002F GitLab \u002F Bitbucket) with `amplify.yml` | Amplify builds from a connected repo | `git remote -v`; check `amplify.yml` exists at repo root |\n| Git provider connection (OAuth token or CodeConnections service role) | Amplify needs read access to the repo | For GitHub: PAT with `repo` scope; for CodeCommit: `aws codeconnections list-connections` |\n| ACM certificate in us-east-1 (for custom domain) | Amplify custom domains use ACM | `aws acm list-certificates --region us-east-1` |\n| Route 53 hosted zone (for Route 53-managed domain) | Custom domain DNS | `aws route53 list-hosted-zones` |\n| Backend stack artifacts (for Gen 2: `amplify\u002Fbackend.ts`; CDK bootstrap) | Backend deploy runs in the build phase | Check `amplify\u002Fbackend.ts` exists; `aws cloudformation describe-stacks --stack-name CDKToolkit` |\n| Framework directive decided (SSR \u002F SSG \u002F SPA) | Drives buildspec + redirect rules | Captured in the prompt or follow-up |\n| Service role for Amplify (auto-created or existing) | Amplify assumes a role to access CodeCommit \u002F Secrets Manager | `aws iam get-role --role-name AWSAmplifyServiceRole` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## 10-step provisioning procedure\n\n### Step 1 — Git provider (binding decision — BEFORE create-app)\n\nAmplify supports CodeCommit, GitHub, GitLab, and Bitbucket. The\nprovider determines the connection method.\n\n**Decision tree:**\n\n```text\nIs the repo in AWS CodeCommit?\n├── YES → CodeCommit  (service role via CodeConnections)\n└── NO → Which provider?\n    ├── GitHub → GitHub  (OAuth PAT or GitHub App; CodeConnections)\n    ├── GitLab → GitLab  (access token; CodeConnections)\n    └── Bitbucket → Bitbucket  (app password; CodeConnections)\n```\n\n**Connection setup (GitHub example):**\n\n```bash\n# Create a CodeConnections connection (formerly CodeStar connection)\naws codeconnections create-connection \\\n  --provider-type GitHub \\\n  --connection-name github-amplify \\\n  --output json\n# Then complete the OAuth handshake in the Console to set the connection\n# status to AVAILABLE.\n```\n\n**Common mistake:** trying to use a personal access token (PAT) without\nthe `repo` scope. The Amplify build fails on `git clone` with a 401.\nUse a CodeConnections connection for GitHub \u002F GitLab \u002F Bitbucket; the\nconnection re-auths automatically.\n\n### Step 2 — Framework + rendering mode (drives buildspec)\n\nThe framework directive determines the build phase, the output directory,\nand the redirect rules.\n\n| Framework | SSR support | Build command | Output dir |\n|---|---|---|---|\n| Next.js (SSR) | YES (Amplify SSR compute) | `npm run build` | `.next` (Amplify auto-detects SSR) |\n| Next.js (SSG) | `output: 'export'` in next.config | `npm run build` | `out` |\n| React (Vite) | SPA | `npm run build` | `dist` |\n| React (CRA) | SPA | `npm run build` | `build` |\n| Vue \u002F Nuxt | SSR (Nuxt) or SPA (Vue) | `npm run build` | `.output` (Nuxt) or `dist` (Vue) |\n| Angular | SPA | `npm run build` | `dist\u002F\u003Cproject>` |\n| Svelte \u002F SvelteKit | SSR \u002F SPA | `npm run build` | `build` |\n\n**Common mistake:** declaring SSR in `next.config.js` but deploying as\nSPA. The framework directive must match the Amplify framework setting.\nFor Next.js SSR, Amplify auto-provisions the SSR compute role on first\ndeploy — do not delete it.\n\n### Step 3 — Build settings (amplify.yml buildspec)\n\nThe `amplify.yml` file at repo root is the buildspec. It defines\nfrontend and backend phases, cache, env vars, and output artifacts.\n\n**Canonical `amplify.yml` (Next.js + Gen 2 backend):**\n\n```yaml\nversion: 1\nfrontend:\n  phases:\n    preBuild:\n      commands:\n        - npm ci\n    build:\n      commands:\n        - npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID\n        - npm run build\n  artifacts:\n    baseDirectory: .next\n    files:\n      - '**\u002F*'\n  cache:\n    paths:\n      - node_modules\u002F**\u002F*\n  customHeaders:\n    - pattern: '**\u002F*'\n      headers:\n        - key: Strict-Transport-Security\n          value: 'max-age=31536000; includeSubDomains'\n        - key: X-Content-Type-Options\n          value: 'nosniff'\n        - key: X-Frame-Options\n          value: 'DENY'\n  redirects:\n    - source: '\u002F\u003C*>'\n      target: '\u002Findex.html'\n      status: 200\n      condition: null\n```\n\n**SPA rewrite rule:** the `redirects` section with `status: 200` rewrites\nall paths to `\u002Findex.html` for client-side routing (React Router, Vue\nRouter). Without this, refreshing `\u002Fusers\u002F123` returns 404.\n\n**Cache:** `node_modules` caching speeds up builds. Pin the lockfile\n(`npm ci` not `npm install`) for reproducible builds.\n\n### Step 4 — Environment variables\n\nEnv vars are branch-scoped. Set them via the Console, CLI, or\n`amplify.yml` `env:`.\n\n```bash\n# Plaintext env var on a specific branch\naws amplify update-app \\\n  --app-id dXXXX \\\n  --environment-variables platform=web,apiUrl=https:\u002F\u002Fapi.example.com \\\n  --output json\n\n# Secrets Manager reference (for API keys, DB credentials)\naws amplify update-app \\\n  --app-id dXXXX \\\n  --custom-rules source=SECRET_API_KEY,target=arn:aws:secretsmanager:us-east-1:111:secret:api-key-XXX \\\n  --output json\n```\n\n**Common mistake:** setting a secret as a plaintext env var. Plaintext\nenv vars are visible in the Console and in `amplify.yml` if committed.\nUse Secrets Manager references for anything sensitive — Amplify reads\nthe secret value at build time, never logs it.\n\n### Step 5 — Custom headers + redirects\n\nCustom headers (security headers, CORS) and redirects (SPA rewrite,\nlegacy URL redirects) live in `amplify.yml`.\n\nFull customHeaders + redirects YAML (HSTS, CSP, 301s, SPA rewrite):\n[references\u002Fbuild-and-domain-reference.md](references\u002Fbuild-and-domain-reference.md).\n\n**Common mistake:** Console-configuring headers and redirects. They are\noverwritten on the next push that includes `amplify.yml`. Always commit.\n\n### Step 6 — Custom domain (Route 53 \u002F CloudFront)\n\nA custom domain uses an ACM certificate with DNS validation.\n\nACM cert request + domain-association commands:\n[references\u002Fbuild-and-domain-reference.md](references\u002Fbuild-and-domain-reference.md).\n\n**Route 53 automatic validation:** if the hosted zone for\n`example.com` is in the same account, ACM auto-writes the validation\nCNAME. For third-party DNS (GoDaddy, Namecheap), copy the CNAME\nmanually.\n\n**Common mistake:** requesting the cert in a region other than\n`us-east-1`. Amplify custom domains require the cert in us-east-1\nregardless of where the app is deployed.\n\n### Step 7 — Amplify Backend (Gen 2 TypeScript CDK)\n\nAmplify Gen 2 uses `amplify\u002Fbackend.ts` with `defineBackend` — fully\nCDK-based, no `amplify init` \u002F `amplify push`.\n\n```typescript\n\u002F\u002F amplify\u002Fbackend.ts\nimport { defineBackend } from '@aws-amplify\u002Fbackend';\nimport { auth } from '.\u002Fauth\u002Fresource';\nimport { data } from '.\u002Fdata\u002Fresource';\nimport { storage } from '.\u002Fstorage\u002Fresource';\n\nexport const backend = defineBackend({\n  auth,\n  data,\n  storage,\n});\n```\n\nGen 2 backend resource catalog (auth\u002Fdata\u002Fstorage\u002Ffunctions) + build-phase\npipeline-deploy contract: [references\u002Fbackend-gen2-reference.md](references\u002Fbackend-gen2-reference.md).\n\n**Common mistake:** running `ampx push` (sandbox mode) in CI instead of\n`ampx pipeline-deploy`. Sandbox mode is for local dev; CI uses\n`pipeline-deploy` which reads the branch and app ID from Amplify env\nvars.\n\n### Step 8 — CI\u002FCD pipeline (branch builds, preview URLs)\n\nAmplify builds on every git push. Each branch gets its own URL.\n\n```bash\n# Enable PR previews (builds every PR branch)\naws amplify update-branch \\\n  --app-id dXXXX \\\n  --branch-name main \\\n  --pull-request-environment-name main \\\n  --output json\n\n# Set up a staging branch environment\naws amplify create-branch \\\n  --app-id dXXXX \\\n  --branch-name staging \\\n  --stage PRODUCTION \\\n  --output json\n```\n\n**Branch environments:**\n- `main` → production URL (`app.example.com`)\n- `staging` → staging URL (`staging.example.com` or\n  `staging.dXXXX.amplifyapp.com`)\n- PR branches → preview URL (`pr123.dXXXX.amplifyapp.com`)\n\n### Step 9 — Amplify Gen 2 latest features (2024-2026)\n\nGen 2 feature detail (CDK backend, branch backends, build image, SSR\nroles, Secrets Manager, Studio): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n### Step 10 — Transit \u002F networking edge cases\n\nTransit\u002Fnetworking edge cases (no VPC attachment, NAT for private\nbackends, second CloudFront): [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things (top 5)\n\n1. **NEVER configure custom headers, redirects, or env vars only in\n   the Console.** Console-configured values are overwritten on the\n   next push that includes `amplify.yml`. Always commit `amplify.yml`\n   with customHeaders, redirects, and env-var references.\n\n2. **NEVER request the ACM certificate for a custom domain in a region\n   other than us-east-1.** Amplify custom domains require the cert in\n   us-east-1 regardless of where the app is deployed. A cert in\n   us-east-2 cannot be attached.\n\n3. **NEVER use `ampx push` (sandbox) in the CI build phase.** Sandbox\n   mode is for local dev with hot reload. CI uses\n   `npx ampx pipeline-deploy --branch $AWS_BRANCH` which deploys the\n   branch-specific backend stack.\n\n4. **NEVER deploy a Next.js SSR app as a SPA without the rewrite rule.**\n   SSR-as-SPA produces 404 on dynamic routes (`\u002Fusers\u002F[id]`). Either\n   use SSR (Amplify auto-detects) or SSG (`output: 'export'`) with a\n   `\u002F\u003C*> -> \u002Findex.html status 200` rewrite.\n\n5. **NEVER store secrets as plaintext environment variables.** Plaintext\n   env vars are visible in the Console and in `amplify.yml` if\n   committed. Use Secrets Manager references — Amplify reads the secret\n   at build time via the service role.\n\n**Additional critical mistakes:** never run one big `main` branch (use\nbranch previews); never assume env vars propagate across branches (they\nare branch-scoped); never delete the auto-created SSR compute role for\nNext.js SSR apps; never skip CDK bootstrap before the first Gen 2\nbackend deploy; never forget to validate the domain DNS CNAME before\nthe cert issues; never use `npm install` in CI (use `npm ci` for\nreproducibility); never configure a second CloudFront in front of\nAmplify without a documented reason (Amplify already fronts the app).\n\n## Output format\n\n```text\nAPP: \u003Capp-name>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Git provider: \u003CCodeCommit | GitHub | GitLab | Bitbucket> (connection: \u003COAuth | service role>)\n  [✓|✗] Repository: \u003Crepo-url> (amplify.yml committed: YES | NO)\n  [✓|✗] Framework: \u003CNext.js | React | Vue | Angular | Svelte> (version)\n  [✓|✗] Rendering mode: \u003CSSR | SSG | SPA | ISR>\n  [✓|✗] Build settings: \u003Camplify.yml phases: preBuild, build, postBuild>\n  [✓|✗] Environment variables: \u003CN plaintext, M Secrets Manager refs>\n  [✓|✗] Custom headers: \u003CHSTS, CSP, X-Frame-Options, ...>\n  [✓|✗] Redirects: \u003CSPA rewrite \u002F\u003C*> -> \u002Findex.html status 200; legacy 301s>\n  [✓|✗] Custom domain: \u003Cdomain> (ACM cert \u003Carn> in us-east-1; DNS validated: YES | NO)\n  [✓|✗] Backend (Gen 2): \u003Cauth Cognito, data AppSync, storage S3, functions Lambda>\n  [✓|✗] CI\u002FCD: \u003Cbranch builds on every push; preview URLs on PRs>\n  [✓|✗] Branch environments: \u003Cmain=prod, staging=staging, PR=preview>\nVERIFICATION_COMMANDS:\n  aws amplify get-app --app-id \u003Cid>\n  aws amplify list-branches --app-id \u003Cid>\n  aws amplify get-domain-association --app-id \u003Cid> --domain-name \u003Cdomain>\n  aws acm describe-certificate --certificate-arn \u003Carn> --region us-east-1\n```\n\n### Worked example — Next.js SSR with Gen 2 backend\n\n```text\nAPP: prod-web\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Git provider: GitHub (connection: CodeConnections github-amplify, AVAILABLE)\n  [✓] Repository: github.com\u002Fexample\u002Fprod-web (amplify.yml committed: YES)\n  [✓] Framework: Next.js 14\n  [✓] Rendering mode: SSR (Amplify auto-provisions SSR compute role)\n  [✓] Build settings: amplify.yml (preBuild: npm ci; build: ampx pipeline-deploy + npm run build)\n  [✓] Environment variables: 3 plaintext (API_URL, NODE_ENV, NEXT_PUBLIC_API_URL), 1 Secrets Manager ref (STRIPE_SECRET_KEY)\n  [✓] Custom headers: HSTS, X-Content-Type-Options nosniff, X-Frame-Options DENY, CSP default-src 'self'\n  [✓] Redirects: \u002F\u003C*> -> \u002Findex.html status 200 (SPA fallback for static routes)\n  [✓] Custom domain: app.example.com (ACM cert arn:aws:acm:us-east-1:111:certificate\u002Fabc in us-east-1; DNS validated: YES via Route 53)\n  [✓] Backend (Gen 2): auth Cognito (user pool + identity pool), data AppSync GraphQL, storage S3 (per-user prefixes)\n  [✓] CI\u002FCD: branch builds on every push; preview URLs on PRs\n  [✓] Branch environments: main=app.example.com, staging=staging.example.com, PR=pr\u003CN>.dXXXX.amplifyapp.com\nVERIFICATION_COMMANDS:\n  aws amplify get-app --app-id dXXXX\n  aws amplify list-branches --app-id dXXXX\n  aws amplify get-domain-association --app-id dXXXX --domain-name example.com\n  aws acm describe-certificate --certificate-arn arn:aws:acm:us-east-1:111:certificate\u002Fabc --region us-east-1\n```\n\nFurther worked examples (React SPA static site; PREREQUISITES_MISSING with\nno Git provider \u002F no amplify.yml): [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n\n## Error handling\n\nError-to-cause-to-fix table (repo access, ampx missing, SSR role, cert\ntimeout, CDK bootstrap, 404s): [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## Recent AWS features (2024-2026)\n\nRecent AWS features (2024-2026) — Gen 2, branch backends, Secrets\nManager, Node 20, Studio, CodeConnections: [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## References (load on demand)\n\n- [Worked examples](references\u002Fworked-examples.md) - further checklists: React SPA static site; PREREQUISITES_MISSING (no Git provider \u002F no amplify.yml)\n- [Error handling](references\u002Ferror-handling.md) - error-to-cause-to-fix table: repo access, ampx missing, SSR role, cert validation, CDK bootstrap, branch-scoped env vars, 404s\n- [Advanced patterns](references\u002Fadvanced-patterns.md) - senior-engineer behaviours, philosophy tenets, cross-dependency gotchas, Gen 2 features, networking edge cases, recent AWS features\n- [Build and domain reference](references\u002Fbuild-and-domain-reference.md) - deep buildspec + domain detail: custom headers\u002Fredirects YAML, ACM cert request + domain association commands\n- [Gen 2 backend reference](references\u002Fbackend-gen2-reference.md) - Gen 2 backend patterns: resource catalog, pipeline-deploy build-phase contract\n\n## Domain\n\nAWS CloudOps \u002F Amplify Application Provisioning, Git-Based CI\u002FCD,\nFrontend Hosting, and Serverless Backend Design.\n\n## AWS documentation\n\n- **AWS Amplify Hosting User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fwelcome.html\n- **Amplify Gen 2 Documentation** — https:\u002F\u002Fdocs.amplify.aws\u002Fgen2\u002F\n- **Amplify custom domains** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fcustom-domains.html\n- **Amplify buildspec (amplify.yml)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fbuild-settings.html\n- **Amplify redirects** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famplify\u002Flatest\u002Fuserguide\u002Fredirects.html\n- **CodeConnections** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcodeconnections\u002Flatest\u002Fuserguide\u002Fwelcome.html\n- **AWS CLI Amplify reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Famplify\u002F\n- **Amplify SSR for Next.js** — https:\u002F\u002Fdocs.amplify.aws\u002Fgen2\u002Fdeploy-and-host\u002Ffullstack-branching-deployments\u002Fnextjs-app-router\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, amplify, devtools, deploy, cicd, git, codecommit, github, frontend, serverless","1","Jacky Chan — AWS Community Builder","aws-cloudops","DevTools","0.1.0","aws, amplify, amplify gen 2, git-based deploy, codecommit, github, gitlab, bitbucket, buildspec, amplify.yml, custom headers, redirects, SPA rewrite, environment variables, custom domain, route 53, cloudfront, SSR, SSG, SPA, amplify backend, cognito auth, appsync api, lambda functions, s3 storage, cicd pipeline, branch environments, cloudops, deploy, devtools","deploy","high","false","capability","Invoke when the user wants to create a new Amplify application, wire a Git provider (CodeCommit, GitHub, GitLab, Bitbucket) for CI\u002FCD, configure a custom domain via Route 53 \u002F CloudFront, design SSR vs SSG vs SPA rendering, deploy an Amplify Gen 2 (TypeScript CDK-based) backend, wire Cognito auth \u002F AppSync API \u002F S3 storage \u002F Lambda functions, configure buildspec.yml (amplify.yml), set custom headers \u002F redirects (SPA rewrite), manage environment variables, or generate provisioning CLI commands \u002F IaC templates. Do NOT invoke for self-managed Next.js on EC2 \u002F ECS \u002F Fargate, CloudFront static site without Amplify, or AppSync-only deployments without the Amplify build pipeline.","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with amplify, cloudfront, route53, iam, secretsmanager, cognito-idp, appsync, lambda, s3, and codeconnections access. Works with Terraform aws_amplify_app \u002F aws_amplify_branch \u002F aws_amplify_domain_association resources, CloudFormation AWS::Amplify::App templates, and the Amplify Gen 2 TypeScript CDK backend (amplify defineBackend).","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Famplify-app-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill amplify-app-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill amplify-app-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill amplify-app-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",7414,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcustom-domain-third-party-dns.md",623,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fbaselines\u002Fcustom-domain-third-party-dns.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fgen2-backend-ampx-pipeline-deploy.md",526,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fbaselines\u002Fgen2-backend-ampx-pipeline-deploy.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-git-provider-and-amplify-yml.md",512,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fbaselines\u002Fmissing-git-provider-and-amplify-yml.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fnextjs-ssr-gen2-backend.md",774,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fbaselines\u002Fnextjs-ssr-gen2-backend.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Freact-spa-static-no-backend.md",562,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fbaselines\u002Freact-spa-static-no-backend.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1857,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",13267,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcustom-domain-third-party-dns.md",846,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fprompts\u002Fcustom-domain-third-party-dns.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fgen2-backend-ampx-pipeline-deploy.md",1057,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fprompts\u002Fgen2-backend-ampx-pipeline-deploy.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-git-provider-and-amplify-yml.md",352,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fprompts\u002Fmissing-git-provider-and-amplify-yml.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fnextjs-ssr-gen2-backend.md",1112,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fprompts\u002Fnextjs-ssr-gen2-backend.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Freact-spa-static-no-backend.md",899,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fevals\u002Fprompts\u002Freact-spa-static-no-backend.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6228,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",6111,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fbackend-gen2-reference.md",6770,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Freferences\u002Fbackend-gen2-reference.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fbuild-and-domain-reference.md",6504,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Freferences\u002Fbuild-and-domain-reference.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ferror-handling.md",1050,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Freferences\u002Ferror-handling.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",2026,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4641,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Famplify-app-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]