Amplify Workflow

If you're building on AWS Amplify Gen2, this is the skill to load. It covers the full TypeScript code-first stack: auth with Cognito, GraphQL data modeling with AppSync and DynamoDB (relationships, enums, authorization rules), S3 storage, Lambda functions, and the Amplify AI Kit for Bedrock. Works across React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. The references are split cleanly between backend resource definitions and frontend integration patterns, so you can jump straight to what you need. Worth using even for questions you think you know, since Gen2 has specific patterns that differ from Gen1 and the skill prevents common version mismatches.

skills.sh installs: 101
GitHub stars: 938
last updated: Jun 11, 2026

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

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:

SKILL.md on GitHub