/amplify-workflow

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](references/core-web.md)

• **Mobile** (Flutter, Swift, Android): You **MUST** read

[core-mobile.md](references/core-mobile.md)

• **Backend only** (no frontend work): Skip to Step 1.

Step 1: Identify the Task Type

| Task | Go To | | ---------------------------------------- | ------------------------------------------------------------------------ | | **Create a new project** | → [scaffolding.md](references/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](references/deployment.md) |

Step 2: Backend Features

You **MUST** read the corresponding reference for each backend feature:

| Feature | Reference | When to Use | | ---------------- | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | Authentication | [auth-backend.md](references/auth-backend.md) | Email/password, social login, MFA, SAML/OIDC | | Data Models | [data-backend.md](references/data-backend.md) | GraphQL schema, DynamoDB, relationships, auth rules | | File Storage | [storage-backend.md](references/storage-backend.md) | S3 uploads/downloads, access rules | | Functions & API | [functions-and-api.md](references/functions-and-api.md) | Lambda, custom resolvers, REST/HTTP APIs, calling from client | | AI Features | [ai.md](references/ai.md) | Conversation, generation, AI tools via Bedrock _(backend config + React/Next.js frontend)_ | | Geo, PubSub, CDK | [advanced-features.md](references/advanced-features.md) | Backend-only: custom CDK stacks, overrides, custom outputs. Backend + frontend: Geo, PubSub, Face Liveness |

Each backend feature file is self-containe