Official agent skill

Amplify Workflow

by awslabs in awslabs/agent-plugins

Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).

OfficialApache-2.0Auto-check passedMobile

Install Amplify Workflow

skills CLI
$ npx skills add awslabs/agent-plugins --skill amplify-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install awslabs/agent-plugins amplify-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/awslabs/agent-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/aws-amplify/skills/amplify-workflow .claude/skills/amplify-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
amplify-workflow
GitHub stars
915
Token cost
~3.2k tokens
SKILL.md length
1,009 words
Files
17 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).

  • Works in 4 steps: Read Core Reference (ALWAYS) → Identify the Task Type → Backend Features → …
  • Amplify Gen2 topics — even for questions you think you know — it contains validated
  • SKILL.md covers Prerequisites, Defaults & Assumptions, Quick Start — Route to the… and Core Concepts, plus 3 more sections
  • Calls npx and aws

What it does

Amplify Workflow is an agent skill from awslabs/agent-plugins, published by the product's own GitHub organization. Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent…

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `references/advanced-features.md`, `references/ai.md` and `references/auth-backend.md`).

It sits in Mobile, covering Cross-platform mobile apps, iOS development and File uploads and storage. It works with Amazon Web Services, Amazon DynamoDB, React Native and TypeScript. The repository describes itself as: Agent Plugins for AWS equip AI coding agents with the skills to help you architect, deploy, and operate on AWS. The licence is Apache-2.0.

When your agent uses it

  • Amplify Gen2 topics — even for questions you think you know — it contains validated
  • Version-specific patterns that prevent common mistakes
  • : user mentions Amplify Gen2
  • Project has amplify/ directory

Example prompts

  • “/amplify-workflow”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Read Core Reference (ALWAYS)
  2. Identify the Task Type
  3. Backend Features
  4. Frontend Integration

What it can do on your machine

Read from SKILL.md and the folder at commit da51970. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • aws

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.amplify.aws
    • ui.docs.amplify.aws

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Amplify Workflow loads about 3.2k tokens when it runs, and up to ~33k if it reads all its reference files. Until then it costs about 228 tokens; SKILL.md has 1,009 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~228
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~33k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from awslabs/agent-plugins at commit da51970, republished under its Apache-2.0 licence (© awslabs). 1,009 words, ~3,220 tokens.

Download SKILL.mdSave it as .claude/skills/amplify-workflow/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.
name
amplify-workflow
description
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).

AWS Amplify Gen2

Build and deploy full-stack applications using AWS Amplify Gen2's TypeScript code-first approach. This skill covers backend resource creation, frontend integration across 8 frameworks, and deployment workflows.

Prerequisites

  • Node.js ^18.19.0 || ^20.6.0 || >=22 and npm
  • AWS credentials configured (aws sts get-caller-identity succeeds)
  • For sandbox: npx ampx --version returns a valid version
  • For mobile: Platform-specific tooling (Xcode, Android Studio, Flutter SDK)

Defaults & Assumptions

When the user does not specify a framework:

  • Web: You SHOULD default to React (Vite) and explain the choice.
  • Mobile: You MUST ask which platform the user wants (Flutter, Swift, Android, or React Native). There is no universal mobile default.
  • Neither specified: If the user says "build an app" without clarifying web vs. mobile, you MUST ask before proceeding.
  • Backend only: If only backend changes are requested and no frontend framework is mentioned, skip the frontend integration step entirely.

When the user does not specify tooling or strategy:

  • Package manager: You SHOULD default to npm unless the user specifies yarn or pnpm.
  • Language: You SHOULD default to TypeScript. Gen2 backends are TypeScript-only; frontends SHOULD follow the project's existing language.
  • Next.js: You SHOULD default to App Router unless the user specifies Pages Router.
  • React Native: Ask the user whether they use Expo or bare React Native CLI.
  • Auth: You MUST ask which login method the user wants (email/password, social login, SAML, passwordless, etc.). Do not assume a default.
  • Data authorization: default to publicApiKey (allow.publicApiKey()) — this is the starter template default. When auth is added, switch to owner-based (allow.owner()) with defaultAuthorizationMode: 'userPool'.

Quick Start — Route to the Right Reference

Step 0: Read Core Reference (ALWAYS)

You MUST read the core reference for your target platform before reading any other reference file. These contain Gen2 detection, Amplify.configure() placement per framework, sandbox commands, required packages, and directory structure rules — patterns needed for all tasks, not just new projects.

  • Web (React, Next.js, Vue, Angular, React Native): You MUST read core-web.md
  • Mobile (Flutter, Swift, Android): You MUST read core-mobile.md
  • Backend only (no frontend work): Skip to Step 1.
Step 1: Identify the Task Type
TaskGo To
Create a new project→ scaffolding.md, then Step 2 and/or Step 3
Add or modify a backend feature→ Step 2 (Backend Features)
Connect frontend to existing backend→ Step 3 (Frontend Integration)
Deploy the application→ deployment.md
Step 2: Backend Features

You MUST read the corresponding reference for each backend feature:

FeatureReferenceWhen to Use
Authenticationauth-backend.mdEmail/password, social login, MFA, SAML/OIDC
Data Modelsdata-backend.mdGraphQL schema, DynamoDB, relationships, auth rules
File Storagestorage-backend.mdS3 uploads/downloads, access rules
Functions & APIfunctions-and-api.mdLambda, custom resolvers, REST/HTTP APIs, calling from client
AI Featuresai.mdConversation, generation, AI tools via Bedrock (backend config + React/Next.js frontend)
Geo, PubSub, CDKadvanced-features.mdBackend-only: custom CDK stacks, overrides, custom outputs. Backend + frontend: Geo, PubSub, Face Liveness

Each backend feature file is self-contained. Load only what you need.

Routing note: These files apply for both adding and modifying features. Route to the same file whether the user says "add auth" or "change auth config" — each reference covers the full define surface.

Step 3: Frontend Integration

After configuring backend resources, connect the frontend. Choose by platform and feature:

Web (React, Next.js, Vue, Angular, React Native):

FeatureReference
Auth UI & flowsauth-web.md
Data CRUD & subscriptionsdata-web.md
Storage upload/downloadstorage-web.md

Mobile (Flutter, Swift, Android):

FeatureReference
Auth UI & flowsauth-mobile.md
Data CRUD & subscriptionsdata-mobile.md
Storage upload/downloadstorage-mobile.md

Note: AI and Functions frontend patterns are included in ai.md and functions-and-api.md respectively — they are not split into separate web/mobile files.

Core Concepts

Show full SKILL.md (428 more words)Show less
Amplify Gen2 Architecture
  • Code-first: All backend resources defined in TypeScript under amplify/
  • Main config: amplify/backend.ts imports and combines all resources via defineBackend()
  • Resource files: amplify/auth/resource.ts, amplify/data/resource.ts, amplify/storage/resource.ts, amplify/functions/<name>/resource.ts
  • Generated output: amplify_outputs.json — consumed by frontend Amplify.configure(). Gitignored — generated by npx ampx sandbox (local dev) or npx ampx pipeline-deploy (CI/CD), never committed.
Directory Structure
project-root/
├── amplify/
│   ├── backend.ts            # defineBackend({ auth, data, ... })
│   ├── auth/resource.ts      # defineAuth({ ... })
│   ├── data/resource.ts      # defineData({ schema })
│   ├── storage/resource.ts   # defineStorage({ ... })
│   └── functions/
│       └── my-func/
│           ├── resource.ts   # defineFunction({ ... })
│           └── handler.ts    # export const handler = ...
├── src/                      # Frontend code
├── amplify_outputs.json      # Generated — DO NOT edit or commit (gitignored)
└── package.json
Key APIs
PackagePurpose
@aws-amplify/backenddefineAuth, defineData, defineStorage, defineFunction, defineBackend
aws-amplifyFrontend: Amplify.configure(), generateClient(), auth/data/storage APIs
@aws-amplify/ui-reactPre-built UI: <Authenticator>, <StorageBrowser>
@aws-amplify/ui-react-aiAI UI: <AIConversation>, useAIConversation

Documentation & Resource Verification

When you need AWS documentation (advanced CDK constructs, service limits, provider-specific auth config):

  1. If AWS documentation tools are available (e.g., via AWS MCP), you SHOULD use them to search and retrieve relevant documentation pages.
  2. If AWS documentation tools are unavailable, you MUST fall back to web search or the aws CLI for resource verification.

Why conditional: Amplify Gen2 is code-first — the primary workflow is editing TypeScript files and running npx ampx commands. AWS MCP tools are useful for post-deployment verification but are not required.

Security Considerations

  • Use secret() for all credentials and API keys — never hardcode or use plain environment variables for sensitive values
  • Review allow.guest() exposure carefully — guest access is enabled by default and grants unauthenticated users access to IAM-authorized resources
  • Scope IAM policies to specific resource ARNs — avoid resources: ['*'] in production
  • Never log secrets or include them in error messages
  • Enable CloudTrail and CloudWatch alarms for monitoring Amplify-deployed resources; enable access logging on S3, AppSync, and API Gateway
  • Configure security headers for web apps — set CSP, HSTS, X-Frame-Options, and X-Content-Type-Options via customHeaders in amplify.yml
  • Attach AWS WAF to public-facing AppSync APIs and API Gateway endpoints for defense in depth
  • Enable throttling and rate limiting on API Gateway and AppSync APIs to prevent abuse
  • Use IAM roles with ephemeral credentials for CI/CD pipelines and Lambda execution roles — never long-lived access keys
  • Encrypt CloudWatch Logs groups with KMS (aws:kms) when they may contain PII, tokens, or secrets; enable log retention policies
  • Enable AppSync schema validation and API Gateway request validators to reject malformed input at the edge
  • Use ACM-managed TLS certificates for custom domains on Amplify Hosting — configure via customDomain in deployment config

All documentation links use react as the default platform slug. Replace /react/ in any URL with your target framework:

FrameworkSlug
Reactreact
Next.jsnextjs
Vuevue
Angularangular
React Nativereact-native
Flutterflutter
Swiftswift
Androidandroid

© awslabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 16 other files (references) in plugins/aws-amplify/skills/amplify-workflow of awslabs/agent-plugins.

  • SKILL.md
  • references/advanced-features.md
  • references/ai.md
  • references/auth-backend.md
  • references/auth-mobile.md
  • references/auth-web.md
  • references/core-mobile.md
  • references/core-web.md
  • references/data-backend.md
  • references/data-mobile.md
  • references/data-web.md
  • references/deployment.md
  • references/functions-and-api.md
  • references/scaffolding.md
  • references/storage-backend.md
  • references/storage-mobile.md
  • references/storage-web.md

Open the folder on GitHubat commit da51970

Compare with similar skills

Amplify Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Amplify Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Amplify Workflow this skillawslabs/agent-plugins915—~3.2kAutomated safety check: PassApache-2.0
AWS Amplifyaws/agent-toolkit-for-aws2.8k—~3.9kAutomated safety check: PassApache-2.0
Frontend Designavibebuilder/claude-prime120—~2.1kAutomated safety check: PassMIT
Design SystemWrongStack/WrongStack370—~3.9kAutomated safety check: PassMIT
Msk Operationsaws/tools-for-devops-agent100—~6.6kAutomated safety check: PassApache-2.0
AWS Advisordiegosouzapw/awesome-omni-skills159—~4.3kAutomated safety check: PassMIT

Similar skills

  • AWS Amplify

    aws/agent-toolkit-for-aws

    Official

    Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).

    2.8k GitHub stars~3.9k tokensUpdated today
    MobileAuto-check passed
  • Frontend Design

    avibebuilder/claude-prime

    Builds distinctive, production-grade UIs that avoid generic AI aesthetics.

    120 GitHub stars~2.1k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check passed
  • Design System

    WrongStack/WrongStack

    Use this skill BEFORE writing or restyling ANY user-facing interface.

    370 GitHub stars~3.9k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Msk Operations

    aws/tools-for-devops-agent

    Official

    Amazon MSK Provisioned operations, troubleshooting, and health assessment for Standard and Express brokers.

    100 GitHub stars~6.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • AWS Advisor

    diegosouzapw/awesome-omni-skills

    AWS Advisor workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.

    159 GitHub stars~4.3k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed
  • UI UX Pro Max

    saoudi-h/solar-icons

    UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.

    184 GitHub starsUsed in 18 repos~11k tokens
    Frontend & DesignAuto-check: notes

More from awslabs/agent-plugins

All 33 skills in this repo
  • Dataset Evaluation

    awslabs/agent-plugins

    Official

    Validates dataset formatting and quality for SageMaker model fine-tuning (SFT, DPO, or RLVR).

    915 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Dataset Transformation

    awslabs/agent-plugins

    Official

    Generates code that transforms datasets between ML schemas for model training or evaluation.

    915 GitHub starsUsed in 2 repos~3.5k tokens
    Auto-check passed
  • Finetuning Technique

    awslabs/agent-plugins

    Official

    Selects a fine-tuning technique (SFT, DPO, RLVR, or RLAIF) for the user's use case and validates it against the selected model's available recipes.

    915 GitHub starsUsed in 1 repo~604 tokens
    Auto-check passed
  • Hyperpod Issue Report

    awslabs/agent-plugins

    Official

    Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases.

    915 GitHub starsUsed in 1 repo~890 tokens
    Auto-check passed
  • Hyperpod Performance Debugger

    awslabs/agent-plugins

    Official

    Diagnose performance issues on Amazon SageMaker HyperPod clusters — uneven NCCL bandwidth across nodes and poor filesystem throughput.

    915 GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check passed
  • Hyperpod Ssm

    awslabs/agent-plugins

    Official

    Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM).

    915 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check: notes

Categories

Questions about Amplify Workflow

What does Amplify Workflow do?

Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Amplify Workflow is an agent skill from awslabs/agent-plugins, published by the product's own GitHub organization. Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).

When should I use Amplify Workflow?

Amplify Workflow fits situations like: amplify Gen2 topics — even for questions you think you know — it contains validated; version-specific patterns that prevent common mistakes; : user mentions Amplify Gen2; project has amplify/ directory.

How do I install Amplify Workflow in Claude Code?

Run `npx skills add awslabs/agent-plugins --skill amplify-workflow -a claude-code`. Or copy the skill folder (plugins/aws-amplify/skills/amplify-workflow in awslabs/agent-plugins) into .claude/skills/amplify-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Amplify Workflow in Codex?

Run `npx skills add awslabs/agent-plugins --skill amplify-workflow -a codex`. Or copy the skill folder (plugins/aws-amplify/skills/amplify-workflow in awslabs/agent-plugins) into .agents/skills/amplify-workflow in your project. Codex loads it when a task matches its description.

Can I use Amplify Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add awslabs/agent-plugins --skill amplify-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amplify-workflow, .gemini/skills/amplify-workflow, .github/skills/amplify-workflow and .opencode/skills/amplify-workflow in your project.

What does Amplify Workflow need to run?

Going by SKILL.md and its folder, Amplify Workflow needs the command-line tools its instructions call (npx and aws). Our summary lists: Node.js.

Does Amplify Workflow access the network?

SKILL.md names 2 domains. As links in the text: docs.amplify.aws and ui.docs.amplify.aws. This is read from the text; nothing was executed.

Is Amplify Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Amplify Workflow use?

Amplify Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Amplify Workflow use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 30k tokens, read only when the agent opens those files.

What are the alternatives to Amplify Workflow?

Skills that share tags, products or a category with Amplify Workflow: AWS Amplify (aws/agent-toolkit-for-aws, 2.8k stars), Frontend Design (avibebuilder/claude-prime, 120 stars), Design System (WrongStack/WrongStack, 370 stars) and Msk Operations (aws/tools-for-devops-agent, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Amplify Workflow?

awslabs (a GitHub organization, an official publisher) maintains it in awslabs/agent-plugins, which has 915 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 5, 2026.

Source: awslabs/agent-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.