frontendSPA frontend development — AlpineJS + Tailwind CSS v4 + Pinecone Router loaded from CDN at pinned versions with no build step, the index.html/app.js/views layout, adding a route, Terraform-rendered runtime config, S3 deployment, design-idiom rules and the settled accessibility patterns. Use when wri
infrastructureTerraform and AWS conventions — never running apply, per-environment tfvars and workspaces, recorded outputs, file organisation, default_tags, project_prefix resource naming, terraform-aws-modules preferences, Lambda timeouts, and references for S3/CloudFront frontend hosting, Route 53/SES, Cognito
lambdas-goGo AWS Lambda conventions — directory naming by trigger (api-<method>-, api-socket-, alb-<method>-, url-, sqs-, sns-, mq-, dynamo-, kinesis-, kafka-, docdb-, s3-, bus-, pipe-, schedule-, cognito-, logs-, alarm-, email-, iot-, aurora-, lambda-, secrets-, ninja-) for API Gateway, WebSocket, ALB, funct
lambdas-nodeNode.js AWS Lambda conventions — when Node is justified over Go, ESM/.mjs modules, the nodejs runtime and index.handler entry point, factory-function dependency injection, node --test with co-located .test.mjs files, the structured log line format, npm-install-on-package packaging, and the same trig
product-requirementsWriting user requirements — what counts as a user-level feature versus a system one, one requirement per file grouping related user stories, the required sections (Dependencies, Risk Assessment, User Stories with Gherkin stories and acceptance criteria, Test Coverage notes, Light Risk Assessment, Ca