
Aws Amplify
If you're building full-stack apps on AWS and want everything wired together without stitching CloudFormation by hand, this is the Gen2 TypeScript-first approach. It covers auth via Cognito, GraphQL data with AppSync, S3 storage, Lambda functions, and Bedrock AI integration, all configured in code under an amplify/ directory. Works across React, Next.js, Vue, Angular, plus mobile with Flutter, Swift, Android, and React Native. The skill is explicit about defaults (React for web, but it asks before assuming mobile platforms) and routing (separate references for backend config versus frontend integration). Useful if you want guardrails against Gen1 patterns or need validated snippets for defineAuth, defineData, and the sandbox workflow.
- skills.sh installs
- 7K
- GitHub stars
- 3.4K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add aws/agent-toolkit-for-aws --skill aws-amplify --agent claude-codeInstalls 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-identitysucceeds) - For sandbox:
npx ampx --versionreturns a valid version - For mobile: Platform-specific tooling (Xcode, Android Studio, Flutter SDK)
Defaults & Assumptions
When the user does not specify a framework:
- Web: Default to React (Vite) and explain the choice.
- Mobile: Ask which platform (Flutter, Swift, Android, or React Native) — there is no universal mobile default, so guessing leads to wasted effort.
- Neither specified: If the user says "build an app" without clarifying web vs. mobile, ask before proceeding — the framework choice affects every subsequent step.
- 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:
Sponsors
Details
- Repository
- github.com/aws/agent-toolkit-for-aws
- Categories
- Frontend Development, Backend & APIs, DevOps & CI/CD, AI & Agent Building, Release Management, Cloud & Infrastructure, Mobile Development, CLI & Terminal, Databases
- First seen
- May 16, 2026
More from aws/agent-toolkit-for-aws
All 56- Creating Data Lake Table7K
- Finding Data Lake Assets7K
- Connecting Lambda To Dynamodb6.9K
- Troubleshooting Application Failures6.9K
- Configuring Vpc Endpoints For Private Aws Service Access6.8K
- Debugging Lambda Timeouts6.8K
- Setting Up Cloudwatch Alarm Notifications6.8K
- Launching Ec2 Instance With Best Practices6.8K
- Troubleshooting S3 Files6.7K
- Creating Api Gateway Stage6.7K
- Setting Up Ec2 Instance Profiles6.6K
- Creating Production Vpc Multi Az6.6K
- Signing In To Aws6.6K
- Aws Transform6.5K
- Connecting Vpcs With Peering6.5K
- Enabling Lambda Vpc Internet Access6.5K
- Exporting Rds To S36.5K
- Setting Up Cloudtrail Multi Region6.5K
- Routing Traffic With Route53 And Cloudfront6.5K
- Creating Amazon Aurora Db Cluster With Instances6.4K
- Troubleshooting Efs6.3K
- Aws Lambda Durable Functions6.2K
- Aws Lambda Managed Instances6.2K
- Aws Cleanrooms6.1K