← ClaudeAtlas

add-config-optionlisted

Use when a ticket adds or changes a configuration option — an environment variable, a settings key, a CLI flag, a YAML field — that operators set, and it must have one source of truth, a validated default, precedence rules, and documentation that cannot drift. Invoke for "make X configurable", "add an env var for Y", "expose a setting", or "the default should be Z".
tmj-90/gaffer · ★ 1 · AI & Automation · score 70
Install: claude install-skill tmj-90/gaffer
# Add a configuration option Configuration is the operator's API: everything that varies between deploys while the code stays the same. A new option must be declared once, parsed and validated at startup, defaulted to today's behaviour, and documented from the same place it is defined. Half the incidents that start with "we set the env var" end with "in the wrong process" or "in seconds, not milliseconds". ## Steps 1. **Confirm it should be an option at all.** Twelve-factor's test: config is what varies per deploy (hosts, credentials, limits, feature switches). A value that never differs between environments is a constant — keep it in code (the `minimalism` skill). A credential is not an ordinary option: follow the `security-secret-handling` skill. 2. **Find the config spine.** Where options are declared (a schema, a settings module, a `config.sh`, a typed `Config` object), how precedence works (commonly: CLI flag, then env var, then config file, then default), and whether docs are generated from it. Call `search_lore` for the convention, and search for existing env reads with the Grep tool (a Bash command mentioning `process.env` is hook-blocked). Add the option THERE; never read `process.env.X` or `os.environ` from a random module. 3. **Name it by the repo's rules.** Prefix, casing, scope and unit (`APP_UPLOAD_TIMEOUT_MS`, not `timeout`). The unit in the name prevents the classic seconds-vs-milliseconds outage. Never reuse a retired option's