From ff35428b63711a0705f4b6ee7f67521b35ee3f96 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Tue, 10 Feb 2026 13:14:34 +0100
Subject: [PATCH 01/15] add aws-amplify plugin

---
 .claude-plugin/marketplace.json               |  22 ++
 .../aws-amplify/.claude-plugin/plugin.json    |  18 ++
 plugins/aws-amplify/.mcp.json                 |  15 +
 plugins/aws-amplify/README.md                 | 137 +++++++++
 plugins/aws-amplify/commands/build.md         |  34 +++
 .../skills/amplify-workflow/SKILL.md          | 259 ++++++++++++++++++
 6 files changed, 485 insertions(+)
 create mode 100644 plugins/aws-amplify/.claude-plugin/plugin.json
 create mode 100644 plugins/aws-amplify/.mcp.json
 create mode 100644 plugins/aws-amplify/README.md
 create mode 100644 plugins/aws-amplify/commands/build.md
 create mode 100644 plugins/aws-amplify/skills/amplify-workflow/SKILL.md

diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index d62dc06..68ee934 100644
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -31,6 +31,28 @@
         "cdk"
       ],
       "version": "1.0.0"
+    },
+    {
+      "category": "fullstack",
+      "description": "Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs",
+      "keywords": [
+        "aws",
+        "aws agent skills",
+        "amazon",
+        "amplify",
+        "fullstack",
+        "gen2",
+        "workflows"
+      ],
+      "name": "aws-amplify",
+      "source": "./plugins/aws-amplify",
+      "tags": [
+        "aws",
+        "amplify",
+        "fullstack",
+        "workflows"
+      ],
+      "version": "1.0.0"
     }
   ]
 }
diff --git a/plugins/aws-amplify/.claude-plugin/plugin.json b/plugins/aws-amplify/.claude-plugin/plugin.json
new file mode 100644
index 0000000..a576738
--- /dev/null
+++ b/plugins/aws-amplify/.claude-plugin/plugin.json
@@ -0,0 +1,18 @@
+{
+  "author": {
+    "name": "Amazon Web Services"
+  },
+  "description": "Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs",
+  "homepage": "https://github.com/awslabs/agent-plugins",
+  "keywords": [
+    "aws",
+    "amplify",
+    "fullstack",
+    "gen2",
+    "workflows"
+  ],
+  "license": "Apache-2.0",
+  "name": "aws-amplify",
+  "repository": "https://github.com/awslabs/agent-plugins",
+  "version": "1.0.0"
+}
diff --git a/plugins/aws-amplify/.mcp.json b/plugins/aws-amplify/.mcp.json
new file mode 100644
index 0000000..7a749d9
--- /dev/null
+++ b/plugins/aws-amplify/.mcp.json
@@ -0,0 +1,15 @@
+{
+  "mcpServers": {
+    "aws-mcp": {
+      "command": "uvx",
+      "timeout": 100000,
+      "transport": "stdio",
+      "args": [
+        "mcp-proxy-for-aws@latest",
+        "--log-level",
+        "ERROR",
+        "https://aws-mcp.us-east-1.api.aws/mcp"
+      ]
+    }
+  }
+}
diff --git a/plugins/aws-amplify/README.md b/plugins/aws-amplify/README.md
new file mode 100644
index 0000000..c0ae572
--- /dev/null
+++ b/plugins/aws-amplify/README.md
@@ -0,0 +1,137 @@
+# AWS Amplify Claude Plugin
+
+Build full-stack applications with AWS Amplify Gen 2 using TypeScript code-first development.
+
+## Overview
+
+This plugin provides a workflow orchestrator for AWS Amplify Gen 2 development. It validates prerequisites, analyzes project state, retrieves official AWS SOPs via MCP, and guides you through backend creation, deployment, and frontend integration.
+
+## Features
+
+- **SOP-Driven**: Uses official AWS Amplify Standard Operating Procedures via MCP
+- **Phased Workflow**: Backend → Sandbox → Frontend → Testing → Production
+- **Framework Support**: React, Next.js, Vue, Angular, React Native, Flutter, Swift, Android
+- **Gen 2 Only**: TypeScript code-first (`defineAuth`, `defineData`, `defineStorage`, `defineFunction`)
+
+## Prerequisites
+
+- Node.js 18.x or later
+- AWS credentials configured (`aws configure` or `aws sso login`)
+- Claude Code 1.0.33 or later
+- `uv` package manager for MCP server: https://docs.astral.sh/uv/getting-started/installation/
+
+## Installation
+
+### Option 1: Load locally (recommended for testing)
+
+```bash
+git clone https://github.com/hfurkanbozkurt/aws-amplify-claude-plugin
+claude --plugin-dir ./aws-amplify-claude-plugin
+```
+
+### Option 2: Copy to your project
+
+Copy the plugin directory into your project and load it:
+
+```bash
+claude --plugin-dir ./aws-amplify-claude-plugin
+```
+
+### Option 3: Multiple plugins
+
+You can load multiple plugins at once:
+
+```bash
+claude --plugin-dir ./aws-amplify-claude-plugin --plugin-dir ./another-plugin
+```
+
+## Usage
+
+### Slash Command
+
+```
+/aws-amplify:build I want to create a todo app with authentication
+```
+
+### Auto-Invoked Skill
+
+The `amplify-workflow` skill is automatically invoked when you mention Amplify-related topics:
+- "Amplify", "backend", "sandbox", "deploy"
+- Adding auth, data, storage, functions
+- Building full-stack apps
+
+Just describe what you want naturally.
+
+## Workflow Phases
+
+| Phase | Description | SOP |
+|-------|-------------|-----|
+| Backend | Create/modify Amplify resources | `amplify-backend-implementation` |
+| Sandbox | Deploy to sandbox for testing | `amplify-deployment-guide` |
+| Frontend | Connect frontend to backend | `amplify-frontend-integration` |
+| Testing | Local verification | Manual |
+| Production | Deploy to production | `amplify-deployment-guide` |
+
+**Common Patterns:**
+- New app: Backend → Sandbox → Frontend → Testing → Production
+- Add feature: Backend → Sandbox
+- Redeploy: Sandbox only
+- Connect UI: Frontend → Testing
+- Go live: Production only
+
+## Plugin Structure
+
+```
+aws-amplify-claude-plugin/
+├── .claude-plugin/
+│   └── plugin.json          # Plugin manifest
+├── commands/
+│   └── build.md             # /aws-amplify:build command
+├── skills/
+│   └── amplify-workflow/
+│       └── SKILL.md         # Auto-invoked orchestrator
+├── .mcp.json                # AWS MCP server config
+├── .gitignore
+├── package.json
+├── LICENSE
+└── README.md
+```
+
+## AWS Credentials
+
+Must be configured before use:
+
+```bash
+# Option 1: Access keys
+aws configure
+
+# Option 2: SSO
+aws sso login
+
+# Verify
+aws sts get-caller-identity
+```
+
+## MCP Server
+
+This plugin requires the AWS MCP server for SOP retrieval. It's automatically configured via `.mcp.json`.
+
+Verify it's working:
+```
+/mcp
+```
+
+Should show `aws-mcp` as active.
+
+**If MCP is unavailable**, the plugin will STOP and ask you to configure it. It will not proceed without MCP.
+
+## License
+
+Apache-2.0
+
+## Resources
+
+- [AWS Amplify Docs](https://docs.amplify.aws/)
+- [Amplify Gen 2 Guide](https://docs.amplify.aws/react/start/)
+- [Claude Code Plugins](https://code.claude.com/docs/en/plugins)
+- [Model Context Protocol](https://modelcontextprotocol.io/)
diff --git a/plugins/aws-amplify/commands/build.md b/plugins/aws-amplify/commands/build.md
new file mode 100644
index 0000000..26ee2bd
--- /dev/null
+++ b/plugins/aws-amplify/commands/build.md
@@ -0,0 +1,34 @@
+---
+description: Build full-stack apps with AWS Amplify Gen 2 - describe what you want to build
+argument-hint: "[description of what to build]"
+---
+
+# Build with AWS Amplify Gen 2
+
+**Request:** $ARGUMENTS
+
+## Input Validation
+
+If `$ARGUMENTS` is empty or unclear, ask:
+```
+What would you like to build? For example:
+- "A todo app with user authentication"
+- "Add a GraphQL API to my existing Next.js app"
+- "Deploy my app to production"
+```
+
+## Execution
+
+This command delegates to the `amplify-workflow` skill which handles:
+
+1. **Step 1: Validate Prerequisites** - Node.js, npm, AWS credentials
+2. **Step 2: Handle Missing Credentials** - STOP if AWS credentials not configured
+3. **Step 3: Execute Workflow** - Determine phases, present plan, execute
+
+Follow the complete workflow defined in the skill.
+
+**Key rules:**
+- Gen 2 ONLY (`defineAuth`, `defineData`, `defineStorage`, `defineFunction`)
+- NO Gen 1 patterns (`amplify init`, `amplify push`)
+- Always follow SOPs completely
+- STOP if MCP tools fail (do not improvise)
diff --git a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
new file mode 100644
index 0000000..74467f0
--- /dev/null
+++ b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
@@ -0,0 +1,259 @@
+---
+name: amplify-workflow
+description: Orchestrates AWS Amplify Gen 2 workflows for building full-stack apps with React, Next.js, Vue, Angular, Flutter, or Swift. Use when user wants to BUILD, CREATE, or DEPLOY Amplify projects, add authentication, data models, storage, GraphQL APIs, Lambda functions, or deploy to sandbox/production. Do NOT invoke for conceptual questions, comparisons, or troubleshooting unrelated to active development.
+---
+
+# Amplify Workflow
+
+Orchestrated workflow for AWS Amplify Gen 2 development.
+
+## When to Use This Workflow
+
+Use for any Amplify Gen 2 work:
+- Building a new full-stack application
+- Adding features to an existing backend
+- Connecting frontend to backend
+- Deploying to sandbox or production
+
+The workflow determines which phases apply based on your request.
+
+**DO NOT invoke when:**
+- User asks conceptual questions ("What is Amplify?", "How does defineData work?")
+- User asks for comparisons ("Gen 1 vs Gen 2")
+- User is troubleshooting existing issues unrelated to building
+- User just wants information, not action
+
+---
+
+## Step 1: Validate Prerequisites
+
+Run these checks before proceeding:
+
+1. **Node.js 18.x or later**
+   ```bash
+   node --version
+   ```
+
+2. **npm available**
+   ```bash
+   npm --version
+   ```
+
+3. **AWS credentials configured** (CRITICAL)
+   ```bash
+   AWS_PAGER="" aws sts get-caller-identity
+   ```
+
+## Step 2: Handle Missing AWS Credentials
+
+If the AWS credentials check fails, **STOP** and present this message to the user:
+
+```
+## ⚠️ AWS Credentials Required
+
+I can't proceed without AWS credentials configured. Please set up your credentials first:
+
+**📚 Setup Guide:** https://docs.amplify.aws/react/start/account-setup/
+
+**Quick options:**
+- Run `aws configure` to set up access keys
+- Run `aws sso login` if using AWS IAM Identity Center
+
+Once your credentials are configured, **come back and start a new conversation** to continue building with Amplify.
+```
+
+**Do NOT proceed with Amplify work until credentials are configured.** The user must restart the conversation after setting up credentials.
+
+## Step 3: Execute Workflow
+
+Once all prerequisites pass, follow the workflow below.
+
+---
+
+## Critical Rules
+
+1. **Always follow SOPs completely** - Do not improvise or skip steps
+2. **Never use Gen 1 patterns** - This is for Amplify Gen 2 only (TypeScript code-first, `defineAuth`/`defineData`/`defineStorage`/`defineFunction`)
+3. **Understand before planning** - Read all necessary project files (e.g., `amplify/`, `package.json`, existing code) to understand the current state BEFORE proposing a plan
+4. **Research before planning** - If unsure about Amplify capabilities or best practices, use documentation tools to search and read AWS Amplify docs BEFORE presenting the plan
+5. **Wait for confirmation after each phase** - After completing each phase, STOP and ask the user to confirm before proceeding to the next phase
+6. **If you encounter an error or get sidetracked:**
+   - Fix the immediate issue
+   - Return to the SOP and continue from where you left off
+   - Do NOT abandon the SOP or start improvising
+7. **If you lose track of where you were in the SOP:**
+   - Use the SOP retrieval tool to get the SOP again
+   - Identify which step you completed last
+   - Continue from the next step
+
+---
+
+## Determine Applicable Phases
+
+Based on the user's request and project state, determine which phases apply:
+
+| Phase | Applies when |
+|-------|--------------|
+| 1: Backend | User needs to create or modify Amplify backend resources |
+| 2: Sandbox | Backend code needs deployment for testing |
+| 3: Frontend | Frontend needs to connect to Amplify backend |
+| 4: Testing | App ready for local verification |
+| 5: Production | User wants to deploy to production |
+
+Common patterns:
+- **New full-stack app:** 1 → 2 → 3 → 4 → 5
+- **Add feature to existing backend:** 1 → 2
+- **Redeploy after changes:** 2 only
+- **Connect existing frontend:** 3 → 4
+- **Deploy to production:** 5 only
+
+---
+
+## Present Plan and Confirm
+
+Present to the user:
+
+```
+## 📋 Plan
+
+### What I understood
+- [Brief summary of what the user wants]
+
+### 🛠️ Features
+[list features if applicable]
+
+### ⚛️ Framework
+[framework if known]
+
+### 📦 Phases I'll execute
+1. [Phase name] - [one-line description] → SOP: [sop-name]
+2. [Phase name] - [one-line description] → SOP: [sop-name]
+...
+(Include SOP name for phases 1, 2, 3, and 5. Phase 4 has no SOP.)
+
+Ready to get started? ✨
+```
+
+**WAIT for user confirmation before proceeding.**
+
+⚠️ **Once the user approves the plan, you MUST stick to it. Do not deviate from the planned phases or SOPs unless the user explicitly asks for changes.**
+
+---
+
+## Execute Phases
+
+Execute each applicable phase IN SEQUENCE.
+
+**When starting a phase, announce it as a header:**
+```
+## ⚙️ Phase 1: Backend (SOP: amplify-backend-implementation)
+[Next: Phase 2: Sandbox Deployment]
+
+## 🚀 Phase 2: Sandbox Deployment (SOP: amplify-deployment-guide)
+[Next: Phase 3: Frontend Integration]
+
+## 🎨 Phase 3: Frontend Integration (SOP: amplify-frontend-integration)
+[Next: Phase 4: Local Testing]
+
+## 🧪 Phase 4: Local Testing
+[Next: Phase 5: Production Deployment]
+
+## 🌐 Phase 5: Production Deployment (SOP: amplify-deployment-guide)
+```
+Omit "[Next: ...]" if it's the last phase in your plan.
+
+---
+
+### Phase 1: Backend
+
+⚠️ **Do NOT write any code until you have retrieved and read the SOP.**
+
+Use the SOP retrieval tool to get **"amplify-backend-implementation"** and follow it completely.
+
+**After completion:**
+- Summarize what was created
+- **STOP and ask:** "Phase 1 complete. Ready to proceed to Phase 2: Sandbox Deployment? 🚀"
+- **WAIT for user confirmation before proceeding.**
+
+---
+
+### Phase 2: Sandbox Deployment
+
+⚠️ **Do NOT run any commands until you have retrieved and read the SOP.**
+
+Use the SOP retrieval tool to get **"amplify-deployment-guide"** and follow it for SANDBOX deployment.
+
+**After completion:**
+- Confirm deployment succeeded and `amplify_outputs.json` exists
+- **STOP and ask:** "Phase 2 complete. Ready to proceed to Phase 3: Frontend Integration? 🎨"
+- **WAIT for user confirmation before proceeding.**
+
+---
+
+### Phase 3: Frontend Integration
+
+**Prerequisite:** `amplify_outputs.json` must exist. If not, run Phase 2 first.
+
+⚠️ **Do NOT write any code until you have retrieved and read the SOP.**
+
+Use the SOP retrieval tool to get **"amplify-frontend-integration"** and follow it completely.
+
+**After completion:**
+- Summarize integration work
+- **STOP and ask:** "Phase 3 complete. Ready to proceed to Phase 4: Local Testing? 🧪"
+- **WAIT for user confirmation before proceeding.**
+
+---
+
+### Phase 4: Local Testing
+
+Present to the user:
+
+```
+## 🧪 Time to test!
+
+### Start your dev server
+[framework-specific command]
+
+### Try out these features
+[list features implemented]
+
+Let me know how it goes! 🤞
+```
+
+**After user confirms testing is successful:**
+- **STOP and ask:** "Phase 4 complete. Ready to proceed to Phase 5: Production Deployment? 🌐"
+- **WAIT for user confirmation before proceeding.**
+
+---
+
+### Phase 5: Production Deployment
+
+⚠️ **Do NOT run any commands until you have retrieved and read the SOP.**
+
+Use the SOP retrieval tool to get **"amplify-deployment-guide"** and follow it for PRODUCTION deployment.
+
+**After completion:**
+
+```
+## 🎉 You're live!
+
+### 🌐 Production URL
+[url]
+
+### 🔧 Amplify Console
+https://console.aws.amazon.com/amplify/home
+
+Your app is now deployed! Future updates: just push to your repo → auto-deploys ✨
+```
+
+---
+
+## Troubleshooting
+
+If issues occur during any phase:
+1. Check the SOP's troubleshooting section first
+2. Use documentation tools to search AWS Amplify docs for the error message
+3. Read the relevant documentation page
+
+**After resolving the issue, immediately return to the SOP and continue from where you left off. Do not abandon the workflow.**

From 93a50a7b5525440ea667ec9cc7cc98f961376680 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Tue, 10 Feb 2026 13:48:40 +0100
Subject: [PATCH 02/15] apply Copilot AI comments

---
 plugins/aws-amplify/.mcp.json |  2 +-
 plugins/aws-amplify/README.md | 28 ++++++++--------------------
 2 files changed, 9 insertions(+), 21 deletions(-)

diff --git a/plugins/aws-amplify/.mcp.json b/plugins/aws-amplify/.mcp.json
index 7a749d9..b0d658b 100644
--- a/plugins/aws-amplify/.mcp.json
+++ b/plugins/aws-amplify/.mcp.json
@@ -3,7 +3,7 @@
     "aws-mcp": {
       "command": "uvx",
       "timeout": 100000,
-      "transport": "stdio",
+      "type": "stdio",
       "args": [
         "mcp-proxy-for-aws@latest",
         "--log-level",
diff --git a/plugins/aws-amplify/README.md b/plugins/aws-amplify/README.md
index c0ae572..8f7ec5f 100644
--- a/plugins/aws-amplify/README.md
+++ b/plugins/aws-amplify/README.md
@@ -17,32 +17,23 @@ This plugin provides a workflow orchestrator for AWS Amplify Gen 2 development.
 
 - Node.js 18.x or later
 - AWS credentials configured (`aws configure` or `aws sso login`)
-- Claude Code 1.0.33 or later
+- Claude Code 2.1.29 or later
 - `uv` package manager for MCP server: https://docs.astral.sh/uv/getting-started/installation/
 
 ## Installation
 
-### Option 1: Load locally (recommended for testing)
+### Option 1: Marketplace (recommended)
 
 ```bash
-git clone https://github.com/hfurkanbozkurt/aws-amplify-claude-plugin
-claude --plugin-dir ./aws-amplify-claude-plugin
+/plugin marketplace add awslabs/agent-plugins
+/plugin install aws-amplify@awslabs-agent-plugins
 ```
 
-### Option 2: Copy to your project
-
-Copy the plugin directory into your project and load it:
-
-```bash
-claude --plugin-dir ./aws-amplify-claude-plugin
-```
-
-### Option 3: Multiple plugins
-
-You can load multiple plugins at once:
+### Option 2: Load locally (for testing)
 
 ```bash
-claude --plugin-dir ./aws-amplify-claude-plugin --plugin-dir ./another-plugin
+git clone https://github.com/awslabs/agent-plugins
+claude --plugin-dir ./agent-plugins/plugins/aws-amplify
 ```
 
 ## Usage
@@ -82,7 +73,7 @@ Just describe what you want naturally.
 ## Plugin Structure
 
 ```
-aws-amplify-claude-plugin/
+aws-amplify/
 ├── .claude-plugin/
 │   └── plugin.json          # Plugin manifest
 ├── commands/
@@ -91,9 +82,6 @@ aws-amplify-claude-plugin/
 │   └── amplify-workflow/
 │       └── SKILL.md         # Auto-invoked orchestrator
 ├── .mcp.json                # AWS MCP server config
-├── .gitignore
-├── package.json
-├── LICENSE
 └── README.md
 ```
 

From 7ac5484a566a85e913a2354d69c72a1b8b9ba52f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Tue, 10 Feb 2026 17:05:12 +0100
Subject: [PATCH 03/15] fix formatting issues + add code owners

---
 .github/CODEOWNERS                            |  1 +
 plugins/aws-amplify/README.md                 | 17 +++++++-----
 plugins/aws-amplify/commands/build.md         |  2 ++
 .../skills/amplify-workflow/SKILL.md          | 27 ++++++++++++++-----
 4 files changed, 33 insertions(+), 14 deletions(-)

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index ea6d605..d7465de 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -24,6 +24,7 @@ LICENSE                   @awslabs/agent-plugins-admins
 mise.toml                 @awslabs/agent-plugins-admins
 NOTICE                    @awslabs/agent-plugins-admins
 plugins/                  @awslabs/agent-plugins-admins
+plugins/aws-amplify/      @awslabs/amplify-ai @awslabs/agent-plugins-admins
 README.md                 @awslabs/agent-plugins-admins
 schemas/                  @awslabs/agent-plugins-admins
 tools/                    @awslabs/agent-plugins-admins
diff --git a/plugins/aws-amplify/README.md b/plugins/aws-amplify/README.md
index 8f7ec5f..7190c86 100644
--- a/plugins/aws-amplify/README.md
+++ b/plugins/aws-amplify/README.md
@@ -47,6 +47,7 @@ claude --plugin-dir ./agent-plugins/plugins/aws-amplify
 ### Auto-Invoked Skill
 
 The `amplify-workflow` skill is automatically invoked when you mention Amplify-related topics:
+
 - "Amplify", "backend", "sandbox", "deploy"
 - Adding auth, data, storage, functions
 - Building full-stack apps
@@ -55,15 +56,16 @@ Just describe what you want naturally.
 
 ## Workflow Phases
 
-| Phase | Description | SOP |
-|-------|-------------|-----|
-| Backend | Create/modify Amplify resources | `amplify-backend-implementation` |
-| Sandbox | Deploy to sandbox for testing | `amplify-deployment-guide` |
-| Frontend | Connect frontend to backend | `amplify-frontend-integration` |
-| Testing | Local verification | Manual |
-| Production | Deploy to production | `amplify-deployment-guide` |
+| Phase      | Description                     | SOP                              |
+| ---------- | ------------------------------- | -------------------------------- |
+| Backend    | Create/modify Amplify resources | `amplify-backend-implementation` |
+| Sandbox    | Deploy to sandbox for testing   | `amplify-deployment-guide`       |
+| Frontend   | Connect frontend to backend     | `amplify-frontend-integration`   |
+| Testing    | Local verification              | Manual                           |
+| Production | Deploy to production            | `amplify-deployment-guide`       |
 
 **Common Patterns:**
+
 - New app: Backend → Sandbox → Frontend → Testing → Production
 - Add feature: Backend → Sandbox
 - Redeploy: Sandbox only
@@ -105,6 +107,7 @@ aws sts get-caller-identity
 This plugin requires the AWS MCP server for SOP retrieval. It's automatically configured via `.mcp.json`.
 
 Verify it's working:
+
 ```
 /mcp
 ```
diff --git a/plugins/aws-amplify/commands/build.md b/plugins/aws-amplify/commands/build.md
index 26ee2bd..e84512d 100644
--- a/plugins/aws-amplify/commands/build.md
+++ b/plugins/aws-amplify/commands/build.md
@@ -10,6 +10,7 @@ argument-hint: "[description of what to build]"
 ## Input Validation
 
 If `$ARGUMENTS` is empty or unclear, ask:
+
 ```
 What would you like to build? For example:
 - "A todo app with user authentication"
@@ -28,6 +29,7 @@ This command delegates to the `amplify-workflow` skill which handles:
 Follow the complete workflow defined in the skill.
 
 **Key rules:**
+
 - Gen 2 ONLY (`defineAuth`, `defineData`, `defineStorage`, `defineFunction`)
 - NO Gen 1 patterns (`amplify init`, `amplify push`)
 - Always follow SOPs completely
diff --git a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
index 74467f0..afab692 100644
--- a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
+++ b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
@@ -10,6 +10,7 @@ Orchestrated workflow for AWS Amplify Gen 2 development.
 ## When to Use This Workflow
 
 Use for any Amplify Gen 2 work:
+
 - Building a new full-stack application
 - Adding features to an existing backend
 - Connecting frontend to backend
@@ -18,6 +19,7 @@ Use for any Amplify Gen 2 work:
 The workflow determines which phases apply based on your request.
 
 **DO NOT invoke when:**
+
 - User asks conceptual questions ("What is Amplify?", "How does defineData work?")
 - User asks for comparisons ("Gen 1 vs Gen 2")
 - User is troubleshooting existing issues unrelated to building
@@ -30,16 +32,19 @@ The workflow determines which phases apply based on your request.
 Run these checks before proceeding:
 
 1. **Node.js 18.x or later**
+
    ```bash
    node --version
    ```
 
 2. **npm available**
+
    ```bash
    npm --version
    ```
 
 3. **AWS credentials configured** (CRITICAL)
+
    ```bash
    AWS_PAGER="" aws sts get-caller-identity
    ```
@@ -92,15 +97,16 @@ Once all prerequisites pass, follow the workflow below.
 
 Based on the user's request and project state, determine which phases apply:
 
-| Phase | Applies when |
-|-------|--------------|
-| 1: Backend | User needs to create or modify Amplify backend resources |
-| 2: Sandbox | Backend code needs deployment for testing |
-| 3: Frontend | Frontend needs to connect to Amplify backend |
-| 4: Testing | App ready for local verification |
-| 5: Production | User wants to deploy to production |
+| Phase         | Applies when                                             |
+| ------------- | -------------------------------------------------------- |
+| 1: Backend    | User needs to create or modify Amplify backend resources |
+| 2: Sandbox    | Backend code needs deployment for testing                |
+| 3: Frontend   | Frontend needs to connect to Amplify backend             |
+| 4: Testing    | App ready for local verification                         |
+| 5: Production | User wants to deploy to production                       |
 
 Common patterns:
+
 - **New full-stack app:** 1 → 2 → 3 → 4 → 5
 - **Add feature to existing backend:** 1 → 2
 - **Redeploy after changes:** 2 only
@@ -145,6 +151,7 @@ Ready to get started? ✨
 Execute each applicable phase IN SEQUENCE.
 
 **When starting a phase, announce it as a header:**
+
 ```
 ## ⚙️ Phase 1: Backend (SOP: amplify-backend-implementation)
 [Next: Phase 2: Sandbox Deployment]
@@ -160,6 +167,7 @@ Execute each applicable phase IN SEQUENCE.
 
 ## 🌐 Phase 5: Production Deployment (SOP: amplify-deployment-guide)
 ```
+
 Omit "[Next: ...]" if it's the last phase in your plan.
 
 ---
@@ -171,6 +179,7 @@ Omit "[Next: ...]" if it's the last phase in your plan.
 Use the SOP retrieval tool to get **"amplify-backend-implementation"** and follow it completely.
 
 **After completion:**
+
 - Summarize what was created
 - **STOP and ask:** "Phase 1 complete. Ready to proceed to Phase 2: Sandbox Deployment? 🚀"
 - **WAIT for user confirmation before proceeding.**
@@ -184,6 +193,7 @@ Use the SOP retrieval tool to get **"amplify-backend-implementation"** and follo
 Use the SOP retrieval tool to get **"amplify-deployment-guide"** and follow it for SANDBOX deployment.
 
 **After completion:**
+
 - Confirm deployment succeeded and `amplify_outputs.json` exists
 - **STOP and ask:** "Phase 2 complete. Ready to proceed to Phase 3: Frontend Integration? 🎨"
 - **WAIT for user confirmation before proceeding.**
@@ -199,6 +209,7 @@ Use the SOP retrieval tool to get **"amplify-deployment-guide"** and follow it f
 Use the SOP retrieval tool to get **"amplify-frontend-integration"** and follow it completely.
 
 **After completion:**
+
 - Summarize integration work
 - **STOP and ask:** "Phase 3 complete. Ready to proceed to Phase 4: Local Testing? 🧪"
 - **WAIT for user confirmation before proceeding.**
@@ -222,6 +233,7 @@ Let me know how it goes! 🤞
 ```
 
 **After user confirms testing is successful:**
+
 - **STOP and ask:** "Phase 4 complete. Ready to proceed to Phase 5: Production Deployment? 🌐"
 - **WAIT for user confirmation before proceeding.**
 
@@ -252,6 +264,7 @@ Your app is now deployed! Future updates: just push to your repo → auto-deploy
 ## Troubleshooting
 
 If issues occur during any phase:
+
 1. Check the SOP's troubleshooting section first
 2. Use documentation tools to search AWS Amplify docs for the error message
 3. Read the relevant documentation page

From 5a3b869ef3808c138f1a5dcf9fcbcb84e56da1bc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 10:26:04 +0100
Subject: [PATCH 04/15] fix: adjust codeowners to new format

---
 .github/CODEOWNERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 1255538..b8bc0ce 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -24,13 +24,13 @@ LICENSE                   @awslabs/agent-plugins-admins
 mise.toml                 @awslabs/agent-plugins-admins
 NOTICE                    @awslabs/agent-plugins-admins
 plugins/                  @awslabs/agent-plugins-admins
-plugins/aws-amplify/      @awslabs/amplify-ai @awslabs/agent-plugins-admins
 README.md                 @awslabs/agent-plugins-admins
 schemas/                  @awslabs/agent-plugins-admins
 tools/                    @awslabs/agent-plugins-admins
 
 ## Plugins (alphabetically listed)
 
+plugins/aws-amplify/      @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-amplify
 plugins/deploy-on-aws     @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-deploy-on-aws
 
 ## File must end with CODEOWNERS file

From caa6b02d4c99ed3733b496ffd8963045a4fe5cc7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 10:31:00 +0100
Subject: [PATCH 05/15] fix: small formatting issue

---
 .github/CODEOWNERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index b8bc0ce..3d688ce 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -30,7 +30,7 @@ tools/                    @awslabs/agent-plugins-admins
 
 ## Plugins (alphabetically listed)
 
-plugins/aws-amplify/      @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-amplify
+plugins/aws-amplify      @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-amplify
 plugins/deploy-on-aws     @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-deploy-on-aws
 
 ## File must end with CODEOWNERS file

From cdbc181bdf2d4d9562c0eaa189922f9159273e13 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 10:36:24 +0100
Subject: [PATCH 06/15] fix: formatting in CODEOWNERS

---
 .github/CODEOWNERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 3d688ce..0a459f8 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -30,9 +30,9 @@ tools/                    @awslabs/agent-plugins-admins
 
 ## Plugins (alphabetically listed)
 
-plugins/aws-amplify      @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-amplify
+plugins/aws-amplify       @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-amplify
 plugins/deploy-on-aws     @awslabs/agent-plugins-admins @awslabs/agent-plugins-maintainers  @awslabs/agent-plugins-deploy-on-aws
 
 ## File must end with CODEOWNERS file
 
-.github/CODEOWNERS         @awslabs/agent-plugins-admins
+.github/CODEOWNERS        @awslabs/agent-plugins-admins

From e8aacc850ec71bf2f25dfb267c62dc237b8cc487 Mon Sep 17 00:00:00 2001
From: must1d <95445223+must1d@users.noreply.github.com>
Date: Wed, 11 Feb 2026 10:53:46 +0100
Subject: [PATCH 07/15] Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: must1d <95445223+must1d@users.noreply.github.com>
---
 plugins/aws-amplify/README.md                        | 10 +++++-----
 plugins/aws-amplify/skills/amplify-workflow/SKILL.md |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/plugins/aws-amplify/README.md b/plugins/aws-amplify/README.md
index 7190c86..fdae990 100644
--- a/plugins/aws-amplify/README.md
+++ b/plugins/aws-amplify/README.md
@@ -46,13 +46,13 @@ claude --plugin-dir ./agent-plugins/plugins/aws-amplify
 
 ### Auto-Invoked Skill
 
-The `amplify-workflow` skill is automatically invoked when you mention Amplify-related topics:
+The `amplify-workflow` skill is automatically invoked when you ask Claude to build, modify, or deploy an Amplify Gen 2 backend or full-stack app, for example:
 
-- "Amplify", "backend", "sandbox", "deploy"
-- Adding auth, data, storage, functions
-- Building full-stack apps
+- "Create a new Amplify backend with auth and a todo data model"
+- "Add S3 storage and a Lambda function to my existing Amplify project"
+- "Deploy my Amplify sandbox environment" / "Promote my sandbox to production"
 
-Just describe what you want naturally.
+It is **not** used for conceptual questions about Amplify, comparisons with other frameworks, or troubleshooting existing projects—ask those as normal questions without expecting the workflow to start. For build/create/deploy tasks, just describe what you want to change or deploy in natural language.
 
 ## Workflow Phases
 
diff --git a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
index afab692..eab0591 100644
--- a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
+++ b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: amplify-workflow
-description: Orchestrates AWS Amplify Gen 2 workflows for building full-stack apps with React, Next.js, Vue, Angular, Flutter, or Swift. Use when user wants to BUILD, CREATE, or DEPLOY Amplify projects, add authentication, data models, storage, GraphQL APIs, Lambda functions, or deploy to sandbox/production. Do NOT invoke for conceptual questions, comparisons, or troubleshooting unrelated to active development.
+description: Orchestrates AWS Amplify Gen 2 workflows for building full-stack apps with React, Next.js, Vue, Angular, React Native, Flutter, Swift, or Android. Use when user wants to BUILD, CREATE, or DEPLOY Amplify projects, add authentication, data models, storage, GraphQL APIs, Lambda functions, or deploy to sandbox/production. Do NOT invoke for conceptual questions, comparisons, or troubleshooting unrelated to active development.
 ---
 
 # Amplify Workflow

From 05b1190f563f0b8d5d40805ec162750cdba2db96 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 11:30:19 +0100
Subject: [PATCH 08/15] feat: add deployment skill

---
 plugins/aws-amplify/README.md                 | 27 ++++++++-----
 .../skills/amplify-deploy/SKILL.md            | 40 +++++++++++++++++++
 .../skills/amplify-workflow/SKILL.md          | 32 ++++++++-------
 plugins/deploy-on-aws/skills/deploy/SKILL.md  |  9 +++++
 .../skills/deploy/references/defaults.md      |  5 +++
 5 files changed, 90 insertions(+), 23 deletions(-)
 create mode 100644 plugins/aws-amplify/skills/amplify-deploy/SKILL.md

diff --git a/plugins/aws-amplify/README.md b/plugins/aws-amplify/README.md
index fdae990..6e5edef 100644
--- a/plugins/aws-amplify/README.md
+++ b/plugins/aws-amplify/README.md
@@ -50,19 +50,26 @@ The `amplify-workflow` skill is automatically invoked when you ask Claude to bui
 
 - "Create a new Amplify backend with auth and a todo data model"
 - "Add S3 storage and a Lambda function to my existing Amplify project"
-- "Deploy my Amplify sandbox environment" / "Promote my sandbox to production"
 
-It is **not** used for conceptual questions about Amplify, comparisons with other frameworks, or troubleshooting existing projects—ask those as normal questions without expecting the workflow to start. For build/create/deploy tasks, just describe what you want to change or deploy in natural language.
+The `amplify-deploy` skill is the mandatory entry point for all Amplify deployments (sandbox and production). It is automatically invoked for deployment requests, for example:
+
+- "Deploy my Amplify sandbox environment"
+- "Promote my sandbox to production"
+- "Release my Amplify app"
+
+When `amplify-workflow` reaches its deployment phases (Phase 2: Sandbox, Phase 5: Production), it delegates to `amplify-deploy` automatically.
+
+These skills are **not** used for conceptual questions about Amplify, comparisons with other frameworks, or troubleshooting existing projects—ask those as normal questions without expecting the workflow to start. For build/create/deploy tasks, just describe what you want in natural language.
 
 ## Workflow Phases
 
-| Phase      | Description                     | SOP                              |
-| ---------- | ------------------------------- | -------------------------------- |
-| Backend    | Create/modify Amplify resources | `amplify-backend-implementation` |
-| Sandbox    | Deploy to sandbox for testing   | `amplify-deployment-guide`       |
-| Frontend   | Connect frontend to backend     | `amplify-frontend-integration`   |
-| Testing    | Local verification              | Manual                           |
-| Production | Deploy to production            | `amplify-deployment-guide`       |
+| Phase      | Description                     | Handled By                            |
+| ---------- | ------------------------------- | ------------------------------------- |
+| Backend    | Create/modify Amplify resources | SOP: `amplify-backend-implementation` |
+| Sandbox    | Deploy to sandbox for testing   | `amplify-deploy` skill                |
+| Frontend   | Connect frontend to backend     | SOP: `amplify-frontend-integration`   |
+| Testing    | Local verification              | Manual                                |
+| Production | Deploy to production            | `amplify-deploy` skill                |
 
 **Common Patterns:**
 
@@ -81,6 +88,8 @@ aws-amplify/
 ├── commands/
 │   └── build.md             # /aws-amplify:build command
 ├── skills/
+│   ├── amplify-deploy/
+│   │   └── SKILL.md         # Deployment skill (sandbox & production)
 │   └── amplify-workflow/
 │       └── SKILL.md         # Auto-invoked orchestrator
 ├── .mcp.json                # AWS MCP server config
diff --git a/plugins/aws-amplify/skills/amplify-deploy/SKILL.md b/plugins/aws-amplify/skills/amplify-deploy/SKILL.md
new file mode 100644
index 0000000..0e02dcc
--- /dev/null
+++ b/plugins/aws-amplify/skills/amplify-deploy/SKILL.md
@@ -0,0 +1,40 @@
+---
+name: amplify-deploy
+description: Deploy AWS Amplify Gen 2 applications to sandbox (development) or production environments. MUST be used when user wants to DEPLOY, RELEASE, PROMOTE, or PUBLISH an Amplify app. Handles both sandbox deployment for testing and production deployment for going live. This is the mandatory entry point for all Amplify deployment operations.
+---
+
+# Amplify Deploy
+
+Deploy an AWS Amplify Gen 2 application to sandbox or production.
+
+## When to Use This Skill
+
+Use for any Amplify deployment:
+
+- Deploy to sandbox for development/testing
+- Deploy/promote to production
+- Redeploy after code changes
+- Any request involving "deploy my Amplify app"
+
+---
+
+## Retrieve and Follow the SOP
+
+The **"amplify-deployment-guide"** SOP must be retrieved **at least once**
+during the conversation using the SOP retrieval tool from `aws-mcp`.
+
+**All steps in the SOP must be followed** for any type of deployment
+(sandbox or production). The SOP contains the latest and most accurate
+deployment procedures. Do not improvise or skip steps.
+
+### Critical Rules
+
+1. **Follow the SOP completely** - Do not improvise or skip steps
+2. **If you encounter an error:**
+   - Fix the immediate issue
+   - Return to the SOP and continue from where you left off
+   - Do NOT abandon the SOP
+3. **If you lose track of where you were:**
+   - Retrieve the SOP again
+   - Identify which step you completed last
+   - Continue from the next step
diff --git a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
index eab0591..96845b9 100644
--- a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
+++ b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
@@ -97,13 +97,13 @@ Once all prerequisites pass, follow the workflow below.
 
 Based on the user's request and project state, determine which phases apply:
 
-| Phase         | Applies when                                             |
-| ------------- | -------------------------------------------------------- |
-| 1: Backend    | User needs to create or modify Amplify backend resources |
-| 2: Sandbox    | Backend code needs deployment for testing                |
-| 3: Frontend   | Frontend needs to connect to Amplify backend             |
-| 4: Testing    | App ready for local verification                         |
-| 5: Production | User wants to deploy to production                       |
+| Phase         | Applies when                                               |
+| ------------- | ---------------------------------------------------------- |
+| 1: Backend    | User needs to create or modify Amplify backend resources   |
+| 2: Sandbox    | Deploy to sandbox for testing (via `amplify-deploy` skill) |
+| 3: Frontend   | Frontend needs to connect to Amplify backend               |
+| 4: Testing    | App ready for local verification                           |
+| 5: Production | Deploy to production (via `amplify-deploy` skill)          |
 
 Common patterns:
 
@@ -135,7 +135,7 @@ Present to the user:
 1. [Phase name] - [one-line description] → SOP: [sop-name]
 2. [Phase name] - [one-line description] → SOP: [sop-name]
 ...
-(Include SOP name for phases 1, 2, 3, and 5. Phase 4 has no SOP.)
+(Include SOP name for phases 1 and 3. Phases 2 and 5 use the `amplify-deploy` skill. Phase 4 has no SOP.)
 
 Ready to get started? ✨
 ```
@@ -156,7 +156,7 @@ Execute each applicable phase IN SEQUENCE.
 ## ⚙️ Phase 1: Backend (SOP: amplify-backend-implementation)
 [Next: Phase 2: Sandbox Deployment]
 
-## 🚀 Phase 2: Sandbox Deployment (SOP: amplify-deployment-guide)
+## 🚀 Phase 2: Sandbox Deployment (via amplify-deploy skill)
 [Next: Phase 3: Frontend Integration]
 
 ## 🎨 Phase 3: Frontend Integration (SOP: amplify-frontend-integration)
@@ -165,7 +165,7 @@ Execute each applicable phase IN SEQUENCE.
 ## 🧪 Phase 4: Local Testing
 [Next: Phase 5: Production Deployment]
 
-## 🌐 Phase 5: Production Deployment (SOP: amplify-deployment-guide)
+## 🌐 Phase 5: Production Deployment (via amplify-deploy skill)
 ```
 
 Omit "[Next: ...]" if it's the last phase in your plan.
@@ -188,9 +188,11 @@ Use the SOP retrieval tool to get **"amplify-backend-implementation"** and follo
 
 ### Phase 2: Sandbox Deployment
 
-⚠️ **Do NOT run any commands until you have retrieved and read the SOP.**
+**Delegate to the `amplify-deploy` skill** for sandbox deployment.
 
-Use the SOP retrieval tool to get **"amplify-deployment-guide"** and follow it for SANDBOX deployment.
+When invoking, indicate that the deployment target is **sandbox (development)**.
+The `amplify-deploy` skill will handle SOP retrieval, prerequisite checks, and
+the complete deployment process.
 
 **After completion:**
 
@@ -241,9 +243,11 @@ Let me know how it goes! 🤞
 
 ### Phase 5: Production Deployment
 
-⚠️ **Do NOT run any commands until you have retrieved and read the SOP.**
+**Delegate to the `amplify-deploy` skill** for production deployment.
 
-Use the SOP retrieval tool to get **"amplify-deployment-guide"** and follow it for PRODUCTION deployment.
+When invoking, indicate that the deployment target is **production**.
+The `amplify-deploy` skill will handle SOP retrieval, prerequisite checks, and
+the complete deployment process.
 
 **After completion:**
 
diff --git a/plugins/deploy-on-aws/skills/deploy/SKILL.md b/plugins/deploy-on-aws/skills/deploy/SKILL.md
index dfc8d77..f1de722 100644
--- a/plugins/deploy-on-aws/skills/deploy/SKILL.md
+++ b/plugins/deploy-on-aws/skills/deploy/SKILL.md
@@ -20,6 +20,15 @@ straightforward services. Don't ask questions with obvious answers.
 4. **Generate** - Write IaC code with [security defaults](references/security.md) applied
 5. **Deploy** - Run security checks, then execute with user confirmation
 
+### Amplify Hosting Delegation
+
+When the recommended deployment target is **Amplify Hosting** (static sites,
+SPAs, or full-stack Amplify Gen 2 apps), delegate the deployment step to the
+`amplify-deploy` skill from the `aws-amplify` plugin. That skill handles
+SOP-driven sandbox and production deployment for Amplify. Continue with
+steps 1-4 of this workflow for analysis, recommendation, and cost estimation,
+then hand off to `amplify-deploy` for the actual deployment.
+
 ## Defaults
 
 See [defaults.md](references/defaults.md) for the complete service selection matrix.
diff --git a/plugins/deploy-on-aws/skills/deploy/references/defaults.md b/plugins/deploy-on-aws/skills/deploy/references/defaults.md
index 6779d27..4ede578 100644
--- a/plugins/deploy-on-aws/skills/deploy/references/defaults.md
+++ b/plugins/deploy-on-aws/skills/deploy/references/defaults.md
@@ -25,6 +25,11 @@ Less configuration than S3 + CloudFront. Git-based deployments work out of the b
 Use S3 + CloudFront when user needs fine-grained control over caching, edge functions,
 or has existing CloudFront infrastructure.
 
+**Deployment:** When deploying to Amplify Hosting, delegate to the
+`amplify-deploy` skill (from the `aws-amplify` plugin). It provides
+SOP-driven deployment for both sandbox (development) and production
+environments, including prerequisite validation and guided workflows.
+
 Use `amplify_docs` topic in awsknowledge MCP for framework-specific guidance
 (React, Next.js, Vue, Angular, etc.).
 

From 88a57afc5519f82f41947cb9c9b0be4be4c6facd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 12:09:05 +0100
Subject: [PATCH 09/15] feat: improve plugin

---
 plugins/aws-amplify/README.md                 |   5 +-
 plugins/aws-amplify/commands/build.md         |  17 +--
 .../skills/amplify-deploy/SKILL.md            |  20 ++++
 .../skills/amplify-workflow/SKILL.md          | 100 ++++++++++--------
 4 files changed, 81 insertions(+), 61 deletions(-)

diff --git a/plugins/aws-amplify/README.md b/plugins/aws-amplify/README.md
index 6e5edef..c020e56 100644
--- a/plugins/aws-amplify/README.md
+++ b/plugins/aws-amplify/README.md
@@ -17,7 +17,6 @@ This plugin provides a workflow orchestrator for AWS Amplify Gen 2 development.
 
 - Node.js 18.x or later
 - AWS credentials configured (`aws configure` or `aws sso login`)
-- Claude Code 2.1.29 or later
 - `uv` package manager for MCP server: https://docs.astral.sh/uv/getting-started/installation/
 
 ## Installation
@@ -125,6 +124,10 @@ Should show `aws-mcp` as active.
 
 **If MCP is unavailable**, the plugin will STOP and ask you to configure it. It will not proceed without MCP.
 
+**Note:** The MCP endpoint (`us-east-1.api.aws`) is the API location for SOP
+retrieval only. It does not affect which region your Amplify resources deploy
+to — deployment region is controlled by your AWS credentials and CLI configuration.
+
 ## License
 
 Apache-2.0
diff --git a/plugins/aws-amplify/commands/build.md b/plugins/aws-amplify/commands/build.md
index e84512d..fe50494 100644
--- a/plugins/aws-amplify/commands/build.md
+++ b/plugins/aws-amplify/commands/build.md
@@ -20,17 +20,8 @@ What would you like to build? For example:
 
 ## Execution
 
-This command delegates to the `amplify-workflow` skill which handles:
+Delegate to the `amplify-workflow` skill and follow its complete workflow.
+The skill handles prerequisite validation, phase planning, SOP retrieval,
+and user confirmation gates.
 
-1. **Step 1: Validate Prerequisites** - Node.js, npm, AWS credentials
-2. **Step 2: Handle Missing Credentials** - STOP if AWS credentials not configured
-3. **Step 3: Execute Workflow** - Determine phases, present plan, execute
-
-Follow the complete workflow defined in the skill.
-
-**Key rules:**
-
-- Gen 2 ONLY (`defineAuth`, `defineData`, `defineStorage`, `defineFunction`)
-- NO Gen 1 patterns (`amplify init`, `amplify push`)
-- Always follow SOPs completely
-- STOP if MCP tools fail (do not improvise)
+Gen 2 ONLY — no Gen 1 patterns (`amplify init`, `amplify push`).
diff --git a/plugins/aws-amplify/skills/amplify-deploy/SKILL.md b/plugins/aws-amplify/skills/amplify-deploy/SKILL.md
index 0e02dcc..1247fa3 100644
--- a/plugins/aws-amplify/skills/amplify-deploy/SKILL.md
+++ b/plugins/aws-amplify/skills/amplify-deploy/SKILL.md
@@ -18,6 +18,26 @@ Use for any Amplify deployment:
 
 ---
 
+## Invocation Context
+
+This skill may be invoked standalone or from the `amplify-workflow` orchestrator.
+
+- **From orchestrator:** The deployment type (sandbox or production) is specified
+  by the caller. Do not re-ask the user. Prerequisites (Node.js, npm, AWS
+  credentials) were already validated — skip the SOP's dependency verification step.
+- **Standalone:** Determine deployment type from the user's request. Validate
+  prerequisites per the SOP.
+
+## Mapping Deployment Targets to SOP Parameters
+
+The SOP uses the parameter name `deployment_type` with values `sandbox` or `cicd`.
+Map user/caller intent as follows:
+
+- "sandbox", "development", "testing" → SOP deployment_type: **sandbox**
+- "production", "prod", "live", "release", "cicd" → SOP deployment_type: **cicd**
+
+---
+
 ## Retrieve and Follow the SOP
 
 The **"amplify-deployment-guide"** SOP must be retrieved **at least once**
diff --git a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
index 96845b9..dd34b24 100644
--- a/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
+++ b/plugins/aws-amplify/skills/amplify-workflow/SKILL.md
@@ -1,29 +1,16 @@
 ---
 name: amplify-workflow
-description: Orchestrates AWS Amplify Gen 2 workflows for building full-stack apps with React, Next.js, Vue, Angular, React Native, Flutter, Swift, or Android. Use when user wants to BUILD, CREATE, or DEPLOY Amplify projects, add authentication, data models, storage, GraphQL APIs, Lambda functions, or deploy to sandbox/production. Do NOT invoke for conceptual questions, comparisons, or troubleshooting unrelated to active development.
+description: Orchestrates AWS Amplify Gen 2 workflows for building full-stack apps with React, Next.js, Vue, Angular, React Native, Flutter, Swift, or Android. Use when user wants to BUILD or CREATE Amplify projects, add authentication, data models, storage, GraphQL APIs, or Lambda functions. Not for conceptual questions, comparisons, or troubleshooting unrelated to active development.
 ---
 
 # Amplify Workflow
 
 Orchestrated workflow for AWS Amplify Gen 2 development.
 
-## When to Use This Workflow
+## Scope
 
-Use for any Amplify Gen 2 work:
-
-- Building a new full-stack application
-- Adding features to an existing backend
-- Connecting frontend to backend
-- Deploying to sandbox or production
-
-The workflow determines which phases apply based on your request.
-
-**DO NOT invoke when:**
-
-- User asks conceptual questions ("What is Amplify?", "How does defineData work?")
-- User asks for comparisons ("Gen 1 vs Gen 2")
-- User is troubleshooting existing issues unrelated to building
-- User just wants information, not action
+This workflow covers building and creating Amplify Gen 2 projects through a phased
+approach. Deployment phases delegate to the `amplify-deploy` skill automatically.
 
 ---
 
@@ -54,11 +41,11 @@ Run these checks before proceeding:
 If the AWS credentials check fails, **STOP** and present this message to the user:
 
 ```
-## ⚠️ AWS Credentials Required
+## AWS Credentials Required
 
 I can't proceed without AWS credentials configured. Please set up your credentials first:
 
-**📚 Setup Guide:** https://docs.amplify.aws/react/start/account-setup/
+**Setup Guide:** https://docs.amplify.aws/react/start/account-setup/
 
 **Quick options:**
 - Run `aws configure` to set up access keys
@@ -108,11 +95,14 @@ Based on the user's request and project state, determine which phases apply:
 Common patterns:
 
 - **New full-stack app:** 1 → 2 → 3 → 4 → 5
+- **Backend only (no frontend):** 1 → 2
 - **Add feature to existing backend:** 1 → 2
 - **Redeploy after changes:** 2 only
 - **Connect existing frontend:** 3 → 4
 - **Deploy to production:** 5 only
 
+**IMPORTANT: Only include phases that the user actually needs.** If the user asks for backend work only (e.g., "add auth", "create a data model", "add storage"), do NOT include Phase 3 (Frontend Integration) or Phase 4 (Local Testing). Frontend phases should only be included when the user explicitly asks for frontend work, a full-stack app, or to connect a frontend to Amplify.
+
 ---
 
 ## Present Plan and Confirm
@@ -120,29 +110,29 @@ Common patterns:
 Present to the user:
 
 ```
-## 📋 Plan
+## Plan
 
 ### What I understood
 - [Brief summary of what the user wants]
 
-### 🛠️ Features
+### Features
 [list features if applicable]
 
-### ⚛️ Framework
+### Framework
 [framework if known]
 
-### 📦 Phases I'll execute
+### Phases I'll execute
 1. [Phase name] - [one-line description] → SOP: [sop-name]
 2. [Phase name] - [one-line description] → SOP: [sop-name]
 ...
 (Include SOP name for phases 1 and 3. Phases 2 and 5 use the `amplify-deploy` skill. Phase 4 has no SOP.)
 
-Ready to get started? ✨
+Ready to get started?
 ```
 
 **WAIT for user confirmation before proceeding.**
 
-⚠️ **Once the user approves the plan, you MUST stick to it. Do not deviate from the planned phases or SOPs unless the user explicitly asks for changes.**
+**Once the user approves the plan, you MUST stick to it. Do not deviate from the planned phases or SOPs unless the user explicitly asks for changes.**
 
 ---
 
@@ -153,19 +143,19 @@ Execute each applicable phase IN SEQUENCE.
 **When starting a phase, announce it as a header:**
 
 ```
-## ⚙️ Phase 1: Backend (SOP: amplify-backend-implementation)
+## Phase 1: Backend (SOP: amplify-backend-implementation)
 [Next: Phase 2: Sandbox Deployment]
 
-## 🚀 Phase 2: Sandbox Deployment (via amplify-deploy skill)
+## Phase 2: Sandbox Deployment (via amplify-deploy skill)
 [Next: Phase 3: Frontend Integration]
 
-## 🎨 Phase 3: Frontend Integration (SOP: amplify-frontend-integration)
+## Phase 3: Frontend Integration (SOP: amplify-frontend-integration)
 [Next: Phase 4: Local Testing]
 
-## 🧪 Phase 4: Local Testing
+## Phase 4: Local Testing
 [Next: Phase 5: Production Deployment]
 
-## 🌐 Phase 5: Production Deployment (via amplify-deploy skill)
+## Phase 5: Production Deployment (via amplify-deploy skill)
 ```
 
 Omit "[Next: ...]" if it's the last phase in your plan.
@@ -174,14 +164,25 @@ Omit "[Next: ...]" if it's the last phase in your plan.
 
 ### Phase 1: Backend
 
-⚠️ **Do NOT write any code until you have retrieved and read the SOP.**
+**CRITICAL: Do NOT create frontend scaffolding or templates during this phase.** Do not run `create-next-app`, `create-react-app`, `create-vite`, `npm create`, or any frontend project generators. Phase 1 is strictly for Amplify backend resources (the `amplify/` directory). If a frontend project already exists, leave it untouched. If no frontend project exists and the user only asked for backend work, do NOT create one.
+
+Before creating any files, ensure `.gitignore` exists in the project root and includes:
+`node_modules/`, `.env*`, `amplify_outputs.json`, `.amplify/`, `dist/`, `build/`.
+Create or update it if these entries are missing.
+
+**Do NOT write any code until you have retrieved and read the SOP.**
 
 Use the SOP retrieval tool to get **"amplify-backend-implementation"** and follow it completely.
 
+**SOP overrides for orchestrator context:**
+
+- **Skip the SOP's Step 12** ("Determine Next SOP Requirements") — phase sequencing is controlled by this workflow, not the SOP.
+- **Prerequisites were already validated** in Step 1 of this workflow. The SOP's dependency verification (Step 1) can be skipped.
+
 **After completion:**
 
 - Summarize what was created
-- **STOP and ask:** "Phase 1 complete. Ready to proceed to Phase 2: Sandbox Deployment? 🚀"
+- **STOP and ask:** "Phase 1 complete. Ready to proceed to Phase 2: Sandbox Deployment?"
 - **WAIT for user confirmation before proceeding.**
 
 ---
@@ -191,13 +192,13 @@ Use the SOP retrieval tool to get **"amplify-backend-implementation"** and follo
 **Delegate to the `amplify-deploy` skill** for sandbox deployment.
 
 When invoking, indicate that the deployment target is **sandbox (development)**.
-The `amplify-deploy` skill will handle SOP retrieval, prerequisite checks, and
-the complete deployment process.
+Also indicate that prerequisites (Node.js, npm, AWS credentials) were already
+validated in Step 1 of this workflow so the deploy skill can skip re-verification.
 
 **After completion:**
 
 - Confirm deployment succeeded and `amplify_outputs.json` exists
-- **STOP and ask:** "Phase 2 complete. Ready to proceed to Phase 3: Frontend Integration? 🎨"
+- **STOP and ask:** "Phase 2 complete. Ready to proceed to Phase 3: Frontend Integration?"
 - **WAIT for user confirmation before proceeding.**
 
 ---
@@ -206,14 +207,19 @@ the complete deployment process.
 
 **Prerequisite:** `amplify_outputs.json` must exist. If not, run Phase 2 first.
 
-⚠️ **Do NOT write any code until you have retrieved and read the SOP.**
+**Do NOT write any code until you have retrieved and read the SOP.**
 
 Use the SOP retrieval tool to get **"amplify-frontend-integration"** and follow it completely.
 
+**SOP overrides for orchestrator context:**
+
+- **Skip the SOP's Step 12** ("Determine Next SOP Requirements") — phase sequencing is controlled by this workflow, not the SOP.
+- **Prerequisites were already validated** in Step 1 of this workflow.
+
 **After completion:**
 
 - Summarize integration work
-- **STOP and ask:** "Phase 3 complete. Ready to proceed to Phase 4: Local Testing? 🧪"
+- **STOP and ask:** "Phase 3 complete. Ready to proceed to Phase 4: Local Testing?"
 - **WAIT for user confirmation before proceeding.**
 
 ---
@@ -223,7 +229,7 @@ Use the SOP retrieval tool to get **"amplify-frontend-integration"** and follow
 Present to the user:
 
 ```
-## 🧪 Time to test!
+## Time to test
 
 ### Start your dev server
 [framework-specific command]
@@ -231,12 +237,12 @@ Present to the user:
 ### Try out these features
 [list features implemented]
 
-Let me know how it goes! 🤞
+Let me know how it goes!
 ```
 
 **After user confirms testing is successful:**
 
-- **STOP and ask:** "Phase 4 complete. Ready to proceed to Phase 5: Production Deployment? 🌐"
+- **STOP and ask:** "Phase 4 complete. Ready to proceed to Phase 5: Production Deployment?"
 - **WAIT for user confirmation before proceeding.**
 
 ---
@@ -245,22 +251,22 @@ Let me know how it goes! 🤞
 
 **Delegate to the `amplify-deploy` skill** for production deployment.
 
-When invoking, indicate that the deployment target is **production**.
-The `amplify-deploy` skill will handle SOP retrieval, prerequisite checks, and
-the complete deployment process.
+When invoking, indicate that the deployment target is **production** (maps to
+`cicd` deployment type in the SOP). Also indicate that prerequisites were
+already validated in Step 1 of this workflow.
 
 **After completion:**
 
 ```
-## 🎉 You're live!
+## You're live!
 
-### 🌐 Production URL
+### Production URL
 [url]
 
-### 🔧 Amplify Console
+### Amplify Console
 https://console.aws.amazon.com/amplify/home
 
-Your app is now deployed! Future updates: just push to your repo → auto-deploys ✨
+Your app is now deployed! Future updates: just push to your repo for auto-deploys.
 ```
 
 ---

From ab98be0e86c2ac84d3bbadd34736e5b3c6a594b1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 12:12:41 +0100
Subject: [PATCH 10/15] fix: revert changes in deploy to aws plugin

---
 plugins/deploy-on-aws/.claude-plugin/plugin.json         | 2 +-
 plugins/deploy-on-aws/skills/deploy/SKILL.md             | 9 ---------
 .../deploy-on-aws/skills/deploy/references/defaults.md   | 5 -----
 3 files changed, 1 insertion(+), 15 deletions(-)

diff --git a/plugins/deploy-on-aws/.claude-plugin/plugin.json b/plugins/deploy-on-aws/.claude-plugin/plugin.json
index 5df6a70..8b37862 100644
--- a/plugins/deploy-on-aws/.claude-plugin/plugin.json
+++ b/plugins/deploy-on-aws/.claude-plugin/plugin.json
@@ -2,7 +2,7 @@
   "author": {
     "name": "Amazon Web Services"
   },
-  "description": "Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment.",
+  "description": "Deploy any application to AWS. Get architecture recommendations, cost estimates, and one-command deployment.",
   "homepage": "https://github.com/awslabs/agent-plugins",
   "keywords": [
     "aws",
diff --git a/plugins/deploy-on-aws/skills/deploy/SKILL.md b/plugins/deploy-on-aws/skills/deploy/SKILL.md
index f1de722..dfc8d77 100644
--- a/plugins/deploy-on-aws/skills/deploy/SKILL.md
+++ b/plugins/deploy-on-aws/skills/deploy/SKILL.md
@@ -20,15 +20,6 @@ straightforward services. Don't ask questions with obvious answers.
 4. **Generate** - Write IaC code with [security defaults](references/security.md) applied
 5. **Deploy** - Run security checks, then execute with user confirmation
 
-### Amplify Hosting Delegation
-
-When the recommended deployment target is **Amplify Hosting** (static sites,
-SPAs, or full-stack Amplify Gen 2 apps), delegate the deployment step to the
-`amplify-deploy` skill from the `aws-amplify` plugin. That skill handles
-SOP-driven sandbox and production deployment for Amplify. Continue with
-steps 1-4 of this workflow for analysis, recommendation, and cost estimation,
-then hand off to `amplify-deploy` for the actual deployment.
-
 ## Defaults
 
 See [defaults.md](references/defaults.md) for the complete service selection matrix.
diff --git a/plugins/deploy-on-aws/skills/deploy/references/defaults.md b/plugins/deploy-on-aws/skills/deploy/references/defaults.md
index 4ede578..6779d27 100644
--- a/plugins/deploy-on-aws/skills/deploy/references/defaults.md
+++ b/plugins/deploy-on-aws/skills/deploy/references/defaults.md
@@ -25,11 +25,6 @@ Less configuration than S3 + CloudFront. Git-based deployments work out of the b
 Use S3 + CloudFront when user needs fine-grained control over caching, edge functions,
 or has existing CloudFront infrastructure.
 
-**Deployment:** When deploying to Amplify Hosting, delegate to the
-`amplify-deploy` skill (from the `aws-amplify` plugin). It provides
-SOP-driven deployment for both sandbox (development) and production
-environments, including prerequisite validation and guided workflows.
-
 Use `amplify_docs` topic in awsknowledge MCP for framework-specific guidance
 (React, Next.js, Vue, Angular, etc.).
 

From cf07a23208f1b79323269c3f8d0a9fd661aa2f81 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 12:15:47 +0100
Subject: [PATCH 11/15] revert: change of deploy to aws description

---
 plugins/deploy-on-aws/.claude-plugin/plugin.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugins/deploy-on-aws/.claude-plugin/plugin.json b/plugins/deploy-on-aws/.claude-plugin/plugin.json
index 8b37862..5df6a70 100644
--- a/plugins/deploy-on-aws/.claude-plugin/plugin.json
+++ b/plugins/deploy-on-aws/.claude-plugin/plugin.json
@@ -2,7 +2,7 @@
   "author": {
     "name": "Amazon Web Services"
   },
-  "description": "Deploy any application to AWS. Get architecture recommendations, cost estimates, and one-command deployment.",
+  "description": "Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment.",
   "homepage": "https://github.com/awslabs/agent-plugins",
   "keywords": [
     "aws",

From 2e1b50460c76afd56f66fce0f07098c37855b78c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 12:23:46 +0100
Subject: [PATCH 12/15] chore(docs): add new plugin to README

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 02c9f61..2b95333 100644
--- a/README.md
+++ b/README.md
@@ -9,6 +9,7 @@ Agent Plugins for AWS equip AI coding agents with the skills to help you archite
 
 | Plugin            | Description                                                                                      | Status    |
 | ----------------- | ------------------------------------------------------------------------------------------------ | --------- |
+| [**aws-amplify**](./plugins/aws-amplify/README.md) | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs               | Available |
 | **deploy-on-aws** | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
 
 ## Installation (Claude Code)

From 53a352b999e968b1fa6f5e887e898bf8654693bc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 12:26:21 +0100
Subject: [PATCH 13/15] fix: build error

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 2b95333..4b4edce 100644
--- a/README.md
+++ b/README.md
@@ -7,10 +7,10 @@ Agent Plugins for AWS equip AI coding agents with the skills to help you archite
 
 ## Plugins
 
-| Plugin            | Description                                                                                      | Status    |
-| ----------------- | ------------------------------------------------------------------------------------------------ | --------- |
-| [**aws-amplify**](./plugins/aws-amplify/README.md) | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs               | Available |
-| **deploy-on-aws** | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
+| Plugin                                             | Description                                                                                      | Status    |
+| -------------------------------------------------- | ------------------------------------------------------------------------------------------------ | --------- |
+| [**aws-amplify**](./plugins/aws-amplify/README.md) | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs                     | Available |
+| **deploy-on-aws**                                  | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
 
 ## Installation (Claude Code)
 

From 574d7c4c8c08022e9cc4d4964d1c4f5fdfb484e8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 13:59:00 +0100
Subject: [PATCH 14/15] improve fix

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 4b4edce..21e1ae7 100644
--- a/README.md
+++ b/README.md
@@ -7,10 +7,10 @@ Agent Plugins for AWS equip AI coding agents with the skills to help you archite
 
 ## Plugins
 
-| Plugin                                             | Description                                                                                      | Status    |
-| -------------------------------------------------- | ------------------------------------------------------------------------------------------------ | --------- |
-| [**aws-amplify**](./plugins/aws-amplify/README.md) | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs                     | Available |
-| **deploy-on-aws**                                  | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
+| Plugin                                 | Description                                                                                      | Status    |
+| -------------------------------------- | ------------------------------------------------------------------------------------------------ | --------- |
+| [**aws-amplify**](plugins/aws-amplify) | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs                     | Available |
+| **deploy-on-aws**                      | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
 
 ## Installation (Claude Code)
 

From 0d590cd2e67578cb5a522fd40c63a38dc5b970e8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mustaf=C3=AB=20Dobra?= <mdobra@amazon.com>
Date: Wed, 11 Feb 2026 14:02:12 +0100
Subject: [PATCH 15/15] align link in README for deploy on aws plugin

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 21e1ae7..e3b3f1a 100644
--- a/README.md
+++ b/README.md
@@ -7,10 +7,10 @@ Agent Plugins for AWS equip AI coding agents with the skills to help you archite
 
 ## Plugins
 
-| Plugin                                 | Description                                                                                      | Status    |
-| -------------------------------------- | ------------------------------------------------------------------------------------------------ | --------- |
-| [**aws-amplify**](plugins/aws-amplify) | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs                     | Available |
-| **deploy-on-aws**                      | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
+| Plugin                                     | Description                                                                                      | Status    |
+| ------------------------------------------ | ------------------------------------------------------------------------------------------------ | --------- |
+| [**aws-amplify**](plugins/aws-amplify)     | Build full-stack apps with AWS Amplify Gen 2 using guided workflows and SOPs                     | Available |
+| [**deploy-on-aws**](plugins/deploy-on-aws) | Deploy applications to AWS with architecture recommendations, cost estimates, and IaC deployment | Available |
 
 ## Installation (Claude Code)