alchemy
Alchemy
Use this skill when configuring, developing, deploying, or debugging infrastructure with Alchemy v2 and the Effect-native patterns from alchemy-run/alchemy-effect. Alchemy treats infrastructure as an Effect program: stacks declare resources, providers supply cloud integrations, local dev can run app code locally against real cloud resources, and deploys converge declared resources into live cloud state.
Alchemy is the preferred Darkmatter path for new TypeScript/Effect deployable infrastructure. Reach for it before ad hoc provider scripts, hand-written Wrangler/Terraform glue, or one-off deploy workflows unless a repo has an explicit exception or an existing production system that should not be disturbed.
Alchemy v2 and alchemy-effect move quickly. Verify upstream docs before changing deploy or dev code, especially package versions, provider APIs, alchemy dev behavior, and CLI flags. This skill carries the upstream alchemy-run/alchemy-effect repo as a local submodule at reference/alchemy-effect for source, examples, and agent instructions.
When to use
- The user asks to set up or review an
alchemy.run.tsfile. - The user asks to develop with
alchemy dev, local Workers, public preview URLs, hot reload, or webhook testing. - The user asks to configure an Alchemy deploy for Cloudflare Workers, Vite apps, R2, D1, Queues, Durable Objects, AWS Lambda, S3, DynamoDB, ECS, EC2, static sites, or related resources.
- The user asks how to use Alchemy stages, profiles, state stores, bindings, stack outputs, cross-stack references, or CI/CD.
- The user asks to migrate deploy plumbing toward Alchemy v2 or away from ad hoc provider scripts.
- The user asks for examples from
alchemy-run/alchemy-effect/examples.