handbook

Enforce Amplify Gen 2 handbook patterns before coding features.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ChinchillaEnterprises/ChillSkills --skill handbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handbook
Source: https://github.com/ChinchillaEnterprises/ChillSkills/tree/main/handbook
Command: npx skills add https://github.com/ChinchillaEnterprises/ChillSkills --skill handbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of writing outdated or incorrect Amplify Gen 2 code by providing Claude with a single, authoritative source of best practices. It significantly reduces research time and debugging efforts, ensuring implementations are always aligned with proven patterns.

Core Features & Use Cases

  • Guided Implementation: Claude automatically reads the project's resources/handbook/ documentation before implementing any Amplify Gen 2 code, ensuring adherence to established patterns.
  • Best Practices Enforcement: Guarantees code follows production-tested guidelines for authentication, data modeling, Lambda functions, webhooks, and frontend patterns.
  • Prevents Hallucinations: Ensures all code is based on verified, up-to-date patterns rather than generic or potentially incorrect approaches.

Quick Start

Implement a new data model for user profiles, ensuring it follows Amplify Gen 2 best practices.

Frequently Asked Questions about handbook

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

FAQPage Schema
How do I ensure my Amplify Gen 2 code follows best practices?

Amplify Gen 2 best practices are enforced by reading your project's handbook documentation before coding, then applying pattern abstractions like defineAuth, defineData, defineFunction, and defineStorage. This prevents outdated implementations and ensures all code aligns with production-tested guidelines for authentication, data modeling, Lambda functions, webhooks, and frontend patterns.

What patterns should I use for authentication and data modeling in Amplify Gen 2?

Amplify Gen 2 provides canonical patterns for authentication and data modeling through defineAuth and defineData abstractions documented in your project's handbook. Following these patterns eliminates guesswork, ensures consistency across your application, and reduces debugging time by grounding implementations in verified best practices.

Can I use CDK imports or API Gateway directly in Amplify Gen 2 projects?

No. Amplify Gen 2 enforces a pattern-first approach that avoids CDK imports and direct API Gateway resources. Instead, use the handbook-defined abstractions like defineFunction and defineStorage to maintain compatibility and follow production-tested patterns for Lambda functions, webhooks, and deployment workflows.

How do I implement Lambda functions and webhooks in Amplify Gen 2?

Lambda functions and webhooks in Amplify Gen 2 are implemented using defineFunction and related pattern abstractions documented in your project's handbook. This approach ensures your serverless code follows established guidelines and integrates correctly with authentication, data modeling, and frontend patterns.

What's the fastest way to reduce research time when building Amplify Gen 2 features?

Use your project's handbook as an authoritative source before implementing any feature. This eliminates hallucinations and research overhead by providing verified patterns for authentication, data modeling, Lambda functions, webhooks, and frontend patterns—ensuring correct implementations on the first attempt.