alchemy-infralisted

Sets up Alchemy (alchemy-run/alchemy, Infrastructure-as-TypeScript) in any codebase — new project scaffold OR add to existing app. Wires Cloudflare/AWS providers, state backend, secrets, and binding types end-to-end with strict secret hygiene. USE THIS SKILL whenever the user mentions "alchemy", "alchemy.run", "Infrastructure as TypeScript", or asks to deploy a Worker/Lambda/D1/R2/KV/Queue/DO via TS, add a state backend, configure ALCHEMY_PASSWORD, generate alchemy.run.ts, replace SST/Pulumi/CDK/Terraform with Alchemy, or scaffold a Cloudflare/AWS app from TypeScript. Trigger even when the user does not say "alchemy" explicitly but describes the workflow (e.g., "deploy a Worker with KV in pure TS", "TypeScript IaC", "wire D1 + Drizzle to a Worker", "set up Cloudflare bindings without wrangler.toml").
Lepidochelyscleavage180/alchemy-infra · ★ 0 · DevOps & Infrastructure · score 78

Install: claude install-skill Lepidochelyscleavage180/alchemy-infra

# alchemy-infra You are configuring **Alchemy** — an ESM-only, TypeScript-native IaC library where resources are async functions you `await`. State lives in JSON files (default), Cloudflare DO, S3, or SQLite. Secrets are encrypted with `ALCHEMY_PASSWORD`. This skill is **interactive**. Do not guess the user's situation. Run the **Intake** below first, then branch. --- ## Step 0 — Intake (ALWAYS run before writing files) Ask the user these questions in a single batched prompt (use the AskUserQuestion tool if available; otherwise plain text with numbered options). Do not skip — the answers change every subsequent decision. 1. **Starting point** — (a) brand-new project, (b) add to existing repo, (c) replace existing IaC (SST/Pulumi/CDK/Terraform/Wrangler). 2. **Cloud target** — (a) Cloudflare, (b) AWS, (c) both, (d) other provider (Vercel/Neon/PlanetScale/Stripe/etc). 3. **Framework** (if applicable) — Worker only, Vite, Next.js, SvelteKit, Astro, Nuxt, TanStack Start, React Router, Redwood, Bun SPA, or none. 4. **Runtime preference** — Bun (recommended), Node, pnpm/npm/yarn. 5. **State backend** — filesystem (default, fine for solo dev), CloudflareStateStore (recommended for teams/CI), S3StateStore, SQLiteStateStore. 6. **Auth method** — Cloudflare OAuth (`alchemy login`), CF API token in env, AWS profile, or "I'll do it later". 7. **Stage/env strategy** — single stage, per-user (`$USER`), per-branch PR previews (`pr-<n>`), explicit prod/staging/dev. 8. **Resources up fro