env-dogma

Centralize environment variables into wrangler.toml and vite.config.ts.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill env-dogma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-dogma
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/env-dogma
Command: npx skills add https://github.com/arthrod/conejo-skills --skill env-dogma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates environment variable sprawl and insecure secret handling in Vite, Cloudflare Workers, and Tauri projects by enforcing a centralized, canonical configuration architecture.

Core Features & Use Cases

  • Centralized Configuration: Migrates all environment variables to wrangler.toml and vite.config.ts, eliminating fragmented .env files.
  • Security Hardening: Enforces a strict separation between non-sensitive variables and secrets, ensuring sensitive values are never committed to version control.
  • Audit & Compliance: Provides a comprehensive suite of shell-based audit tools to detect and remove forbidden access patterns like process.env in worker code.

Quick Start

Run the env-dogma audit and refactor process to identify all forbidden environment variable patterns and migrate them to the canonical configuration.

Frequently Asked Questions about env-dogma

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

FAQPage Schema
How do I centralize environment variables in Vite, Cloudflare Workers, and Tauri applications?

Centralize environment variables by migrating all configuration to wrangler.toml for worker-side variables and vite.config.ts for client-side build-time injection, eliminating fragmented .env files. This enforces a canonical configuration architecture across all three runtimes.

What is the best way to secure secrets and remove .env file sprawl in a Vite and Cloudflare project?

Securing secrets requires enforcing a strict separation between non-sensitive variables and sensitive values, ensuring secrets are never committed to version control. Centralizing configuration in wrangler.toml and vite.config.ts eliminates the insecure .env sprawl pattern entirely.

How do I audit my codebase for insecure process.env access patterns in Cloudflare Workers?

Auditing for insecure process.env access patterns is done using a comprehensive suite of shell-based audit tools. These tools detect and flag forbidden environment variable access patterns in worker code, enabling you to remove them and migrate to canonical configuration.

Can I use wrangler.toml and vite.config.ts for all environment configuration instead of .env files?

Yes, you can use wrangler.toml and vite.config.ts for all configuration. This approach requires strict adherence to wrangler.toml for worker-side variables and vite.config.ts for client-side build-time injection, completely replacing file-based .env loading.

Why does my Cloudflare Workers code still have inconsistent environment variable access patterns after refactoring?

Inconsistent access patterns persist when forbidden process.env references remain in worker code. Running the shell-based audit tools detects these residual patterns so you can eliminate them and enforce consistent access across runtime environments.

Does env-dogma support removing file-based environment loading for Tauri applications?

Yes, env-dogma targets Tauri applications by refactoring environment variable and secret management to eliminate file-based loading. It centralizes configuration, ensuring consistent access patterns across Vite, Cloudflare Workers, and Tauri runtime environments.