config-env-parameters — Claude Code skill for Symfony config
The config-env-parameters skill guides changes to Symfony environment variables, parameters, and secrets across environments. Use it when configuration needs a clear home and safe injection into the app.
MIT ★ 234 updated 2026-10-05
npx skills add dev-toolings/superpowers-symfony --skill config-env-parameters -a claude-codeWhat config-env-parameters does
The skill helps choose where a value belongs: .env, .env.local, the server environment, or Symfony’s secrets vault. It covers injecting values with %env(...)% and a suitable processor, or through a parameter or #[Autowire].
For environment-specific settings, it points to config/packages/<env>/ and when@<env> blocks. It also calls out env-file loading order and checking required values in a service. In production, set variables in the server or container environment. Committing .env.local, .env.*.local, or the vault decryption key risks exposing local configuration or secrets. Env values stay strings until processed, so a boolean comparison needs proper casting.
What it helps with
- separate Symfony configuration by environment
- inject an env value with the right processor
- store credentials in the Symfony secrets vault
- check which
.envfile takes precedence - keep the vault decryption key out of Git
Example prompts for the agent
- Add a Symfony environment variable for this service and inject it with the appropriate processor.
- Move these credentials into the Symfony secrets vault without printing their values.
- Set a separate production value and show where Symfony should read it from.
How to install config-env-parameters
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill config-env-parameters -a claude-code2Manually: put the files in place
~/.claude/skills/config-env-parameters/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/config-env-parameters/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill config-env-parameters -a codex2Manually: put the files in place
.agents/skills/config-env-parameters/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill config-env-parameters -a cursor2Manually: put the files in place
.cursor/skills/config-env-parameters/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dev-toolings/superpowers-symfony content/skills/config-env-parameters2Manually: put the files in place
.github/skills/config-env-parameters/SKILL.md1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill config-env-parameters -a gemini-cli2Platform CLI
gemini skills install https://github.com/dev-toolings/superpowers-symfony --path content/skills/config-env-parametersManually: put the files in place
.devin/skills/config-env-parameters/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about config-env-parameters
How do I install config-env-parameters in Claude Code?
Run npx skills add dev-toolings/superpowers-symfony --skill config-env-parameters -a claude-code. The skill file is at ~/.claude/skills/config-env-parameters/SKILL.md.
What does config-env-parameters do?
It guides Symfony configuration changes involving environment variables, parameters, and secrets. It covers environment-specific values and ways to inject processed values into the app.
Where should production environment variables go?
Set them in the server or container environment rather than in files. The skill also warns against committing local env files or the secrets vault decryption key.
Source text
SKILL.md · MIT
--- name: config-env-parameters description: Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings capabilities: [read, search, edit, shell] tags: [architecture, config] # projected by `bun run build` — do not edit by hand allowed-tools: - Read - Glob - Grep - Write - Edit - Bash --- # Config Env Parameters (Symfony) ## Use when - Adding or changing an environment variable, a parameter, or a secret. - A value differs between environments (dev, test, prod). - Casting or parsing env values (`int:`, `bool:`, `json:`, `csv:`, `file:`). - Storing credentials in the Symfony secrets vault. ## Default workflow 1. Decide where the value lives: `.env` default, `.env.local`, real environment, or the vault for secrets. 2. Declare it with a safe committed default, never a real credential. 3. Inject it with `%env(...)%` and the right processor, through a parameter or `#[Autowire]`. 4. Put environment-specific settings in `config/packages/<env>/` or `when@<env>` blocks. 5. Fail fast in the service when a required value is empty. ## Guardrails - Never commit `.env.local`, `.env.*.local` or the vault decryption key. - In production, set variables in the server or container environment, not in files. - Env values are strings until processed: cast them, do not compare `"false"` to `false`. - Remember the loading order: `.env`, `.env.local` (skipped in test), `.env.<env>`, `.env.<env>.local`. ## Progressive disclosure - Use this file for execution posture and risk controls. - Open references when deep implementation details are needed. ## Output contract - Where each new value is defined, per environment. - The injection point and the processor used. - Secrets added to the vault, named but never printed. ## References - `reference.md`
© dev-toolings · MIT · dev-toolings/superpowers-symfony