2026
claude-skills
An open-source library of distilled, reusable engineering practice for AWS Amplify, Next.js and Expo.
Problem
The same architectural decisions kept recurring across projects — auth wiring, soft deletes, async job fan-out, table naming — and getting re-derived from scratch each time.
My role
Author and maintainer.
Outcome
Forty-plus documented setup flows covering an entire production stack, each one written from work that actually shipped rather than from theory.
Every skill in the repo comes out of a real implementation: the Cognito post-confirmation trigger that creates a profile row without a client-side race, the SSM pattern that stops Lambda table-name lookups from creating circular stack dependencies, the two-Lambda fan-out for work that exceeds the API Gateway timeout.
The value isn't the code snippets. It's that each one records the trap that made the naive approach fail.