amplify-workflow
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/ di
Profile →npx skills add awslabs/agent-plugins --skill amplify-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 yar
- Prerequisites
- Defaults & Assumptions
- Quick Start — Route to the Right Reference
- Step 0: Read Core Reference (ALWAYS)
- Step 1: Identify the Task Type
- Step 2: Backend Features
- Step 3: Frontend Integration
- Core Concepts
- Amplify Gen2 Architecture
- Directory Structure
- Key APIs
- Documentation & Resource Verification
- Security Considerations
- Links
What does the amplify-workflow skill do?
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/ di
How do I install it?
Run `npx skills add awslabs/agent-plugins --skill amplify-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From awslabs/agent-plugins, a repository with 850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.