Goal
Plan configuration so environments are reproducible and secrets stay safe.
When to Use
- A new system is being set up.
- Existing env vars and config are ad hoc.
- The project spans several runtimes or deployment targets.
Instructions
- List required configuration by environment and by runtime.
- Separate secrets from non-secret configuration.
- Decide how configuration is validated and loaded.
- Note defaults, overrides, and environment-specific restrictions.
Constraints
- Do not assume one
.envfile is enough for all contexts. - Keep required config discoverable.
- Avoid silent fallback behavior for critical values.
Output Format
- config inventory
- environment mapping
- validation and loading strategy
- risks
Examples
- "Plan env configuration for local, CI, staging, and prod."
- "How should serverless and worker configs differ?"