skills.rest
firtoz
firtozCOMMUNITY
Explore all skills by this author →
Website𝕏@firtozGitHub

cf-workers-env-local

Manage and validate environment variable files across dev, staging, and production for Cloudflare Alchemy apps.

10|Updated May 22, 2025
Search Tags:#devops#environment#alchemy#cloudflare#ci-cd#env
One-click install
npx skills add https://github.com/firtoz/cf-multiworker-starter-kit --skill cf-workers-env-local
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cf-workers-env-local
Source: https://github.com/firtoz/cf-multiworker-starter-kit/tree/main/agents/skills/cf-workers-env-local
Command: npx skills add https://github.com/firtoz/cf-multiworker-starter-kit --skill cf-workers-env-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alchemy env rules help teams manage repository-root .env.local (dev), .env.staging (staging / PR preview deploys), and .env.production (prod / CI), with optional per-package .env.local, avoiding plain .env files and ensuring correct bindings.

Core Features & Use Cases

  • Centralized guidance for using and documenting env files across dev, staging, and prod.
  • Per-package .env.local overrides to scope vars to specific apps without leaking secrets.
  • Clear alignment with Alchemy bindings and CI workflows to keep local dev and production consistent.

Quick Start

Use this skill to configure and document repository-wide environment variables across dev, staging, and prod with per-package overrides.

Frequently Asked Questions about cf-workers-env-local

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage environment variables across dev, staging, and production for Cloudflare Workers?▼

Manage Cloudflare Workers environment variables by using repository-root .env.local, .env.staging, and .env.production files to scope configurations for dev, staging, and prod respectively. This enforces conventions and ensures correct Alchemy bindings across different deployment stages.

What is the best way to handle environment variables in a Cloudflare Workers monorepo?▼

Handle environment variables in a Cloudflare Workers monorepo by applying repository-root .env files for global config and optional per-package .env.local overrides. This scopes specific variables to individual apps without leaking secrets or breaking Alchemy bindings.

Why should I avoid plain .env files when setting up Alchemy apps?▼

Avoid plain .env files in Alchemy apps to prevent ambiguous environment overrides and misaligned bindings. Using specific .env.local, .env.staging, and .env.production files enforces clear conventions for CI workflows and local development.

Can I scope environment variables to specific packages in a Cloudflare Workers monorepo?▼

Yes, you can scope environment variables to specific packages by using per-package .env.local files. This allows individual app overrides while maintaining a centralized repository-root configuration for broader development, staging, and production environments.

How do I align Cloudflare Alchemy bindings with CI workflows for staging and production?▼

Align Cloudflare Alchemy bindings with CI workflows by strictly mapping .env.staging to PR preview deploys and .env.production to prod CI. Maintaining this file convention keeps local development and production environments consistent.

Related Skills

Explore More Software Engineering Skills→
firtozfirtoz
10

cf-starter-workflow

Automate Cloudflare multi-worker workflow setup and task orchestration from the repository root.

Community
Advanced
joelhooksjoelhooks
22

cloudflare-deploy

Deploy Cloudflare Workers and Pages via wrangler with authentication and domain setup.

Community
Advanced
DicklesworthstoneDicklesworthstone
70

wrangler

Deploy and manage Cloudflare Workers, Pages, and storage via wrangler CLI.

Community
Intermediate
vincent119vincent119

go-configuration

Centralize Go application configuration and environment variables with Viper.

Community
Intermediate