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 patt
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 19 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill86%
Checks it passed that the model alone missed
Identifies core-web.md as the required initial reference document
Identifies core-mobile.md as the primary required reference guide
Explains the choice of React with Vite as the web framework default
and 8 more in the full report
9 fixed10 passed either way3 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+89%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/16/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Which reference guide must be read first when connecting a native iOS Swift or Android application to an Amplify Gen2 backend?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies core-mobile.md as the primary required reference guide
Missed
Passed
case-14 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md211 lines17 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.
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