craft-infralisted

# Infra Craft This skill encodes one engineer's standard for shipping and running services reliably, applied the same way across every repo. The **method and opinions** live here; the **project specifics** (hosting platform, CI system, IaC tool, env-var schema) live in the target repo's code and config — always discover them, never assume or hardcode. ## Operating principle — discover before you build Different repos already have different pieces in place. Before adding anything, spend a couple of minutes mapping what exists so you extend rather than duplicate or conflict: - `package.json` / lockfile → build tooling, runtime adapters (e.g. `@vercel/node`, `fly` CLI hints, serverless framework packages). - CI config files (`.github/workflows/`, `.circleci/`, `Jenkinsfile`, `.gitlab-ci.yml`) → existing gates, deploy steps, environment secrets. - Env-var schema (`env.ts`, `config.ts`, `.env.example`, `zod` schemas) → which vars are required, which are optional, where validation happens. - Health/readiness endpoints (`/health`, `/ready`, `/api/healthz`) and how they're registered. - IaC files (`terraform/`, `pulumi/`, `cdk/`, `fly.toml`, `vercel.json`, `render.yaml`) → existing resource definitions to extend rather than replace. State what you found, then propose the smallest set of additions that closes the gaps. ## The infra layers (work in this order) 1. **Config** — all configuration flows through a validated env schema that fails closed on missing required