aws-amplify

Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 TypeScript backends.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/dennisvink/yolomancer --skill aws-amplify-dennisvink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-amplify
Source: https://github.com/dennisvink/yolomancer/tree/main/skills/aws/specialized-skills/web-and-mobile-development/aws-amplify
Command: npx skills add https://github.com/dennisvink/yolomancer --skill aws-amplify-dennisvink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @aws-amplify/backend, aws-amplify, @aws-amplify/ui-react, @aws-amplify/ui-react-ai, @aws-amplify/adapter-nextjs, and includes references (resource) components.

What problem does it solve? Building full-stack applications with AWS Amplify Gen2 requires coordinating TypeScript backend definitions (auth, data, storage, functions) with framework-specific frontend integration across React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. This Skill provides validated, version-specific patterns that prevent common mistakes like misconfigured entry points, circular dependencies, and silent auth failures. ## Core Features & Use Cases - Backend Resource Definition: Configure Cognito auth (MFA, social login, passwordless, SAML via CDK), AppSync/DynamoDB data models with authorization rules, S3 storage, Lambda functions, REST/HTTP APIs, and AI conversation/generation routes via Bedrock. - Cross-Platform Frontend Integration: Framework-specific setup for 8 platforms, including Next.js App Router client components, React Native import ordering, and native mobile Authenticator components. - Deployment Workflows: Sandbox environments, CI/CD pipeline setup with IAM roles, branch-based multi-environment deployments, secrets management, and custom domains. - Use Case: A developer asks to add Google social login with owner-based data authorization to a Next.js app. The Skill routes to auth-backend.md for the defineAuth configuration with secret() handling, then to auth-web.md for the Authenticator component and Next.js SSR setup. ## Quick Start Ask the assistant to scaffold a new Amplify Gen2 project with authentication and a data model for your chosen framework.

Frequently Asked Questions about aws-amplify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up authentication in AWS Amplify Gen2?

Define auth in amplify/auth/resource.ts using defineAuth with loginWith options like email, social providers, or passwordless methods, then import it into amplify/backend.ts via defineBackend. Frontend integration uses the Authenticator component from @aws-amplify/ui-react or platform equivalents.

How do I configure Amplify in a Next.js App Router project?

Create a ConfigureAmplifyClientSide client component that calls Amplify.configure(outputs, { ssr: true }) and import it in app/layout.tsx. The layout is a server component, so configuration must run in a dedicated client component to avoid 'Auth UserPool not configured' errors.

Does Amplify Gen2 support SAML enterprise identity providers?

SAML is not supported directly in defineAuth; the high-level API only covers OIDC via externalProviders. You must use CDK escape hatches through backend.auth.resources.cfnResources to configure a CfnUserPoolIdentityProvider for SAML.

Why does my Amplify app fail with module-not-found for amplify_outputs.json?

amplify_outputs.json is generated, not committed to source control. Run npx ampx sandbox (or npx ampx sandbox --once) before building to generate it locally; in CI/CD, npx ampx pipeline-deploy generates it during the build phase.

What is the difference between Amplify Gen2 and Gen1?

Gen2 uses a TypeScript code-first approach with defineBackend, defineAuth, and defineData in an amplify/ directory, while Gen1 uses the Amplify CLI with amplify/.config. This Skill covers Gen2 only; Gen1 projects require a separate migration path.

Why do my Amplify data subscriptions fail silently?

Subscriptions require a WebSocket-compatible auth mode such as userPool or iam; API key auth fails silently on subscriptions. Also ensure useEffect returns a cleanup function calling sub.unsubscribe() to prevent connection leaks.