Build serverless backends on AWS with Aurora DSQL, better-auth, Lambda (API Gateway REST + WAF), and S3. Use when building a backend, deploying to AWS, setting up auth, creating APIs, or adding storage. Covers the same capabilities as Supabase but fully serverless on AWS.
Build serverless backends on AWS with Aurora DSQL, better-auth, Lambda (API Gateway REST + WAF), and S3. Use when building a backend, deploying to AWS, setting up auth, creating APIs, or adding storage. Covers the same capabilities as Supabase but fully serverless on AWS.
Deploy and configure BOA Studio — the admin UI for BOA backends. Handles local dev setup, cloud deployment to AWS Amplify, auth configuration (token or Cognito), and first-run setup. Use when a developer wants to run, deploy, or configure BOA Studio.
Diagnose and fix BOA backend issues — deploy failures, 403 errors, CORS problems, auth not working, database connection timeouts, migration failures. Use this skill whenever a developer reports an error, sees unexpected behavior, or something broke after a deploy. Triggers on error messages, HTTP status codes, stack traces, and phrases like "not working", "broken", "failing", "can't sign in", "getting 403".
Inspect, manage, and operate a running BOA backend — view tables and schema, check stack status, tail Lambda logs, seed data, open the dashboard, run API smoke tests, and monitor costs. Use this skill when a developer wants to see what's in their backend, check on their deployment, view logs, manage data, or understand their AWS usage. Triggers on phrases like "show me my tables", "what's deployed", "open dashboard", "view logs", "seed data", "smoke test", "status", "how much is this costing".
Estimate AWS costs for a BOA backend and compare with Supabase pricing. Use this skill when a developer asks about costs, pricing, "how much will this cost", "is BOA cheaper than Supabase", "estimate my AWS bill", "pricing comparison", budget planning, or wants to understand what they'll pay at different user scales. Also use when someone is evaluating whether to use BOA vs Supabase/Firebase from a cost perspective.
Audit and improve an existing design document. Use after a design doc has been drafted to verify technical accuracy, find gaps, and fix issues.
Create a new design document from abstract requirements. Use when the user describes a feature or change and needs a formal design doc written to docs/design/.