python-settingslisted
Install: claude install-skill wntic/pyhouse
# Python — Settings
A program's configuration arrives from its environment, and one kind of class reads it: the settings
class. This skill owns what that class declares, which of its fields may default, how a secret travels
through it, and where the object is built. It holds in any Python program — a service of either
architecture family, a CLI tool, a library — because every one of them either reads configuration or is
handed it.
## When to use vs. neighbours
- What a settings class or its environment prefix is called, the nested-prefix collision, and the stem a
shared library reads → `naming` (its rule 7 and **One environment prefix per settings class**).
- A settings object, client or engine built at module level → `python-packaging` rule 8, which owns
building nothing at import time; this skill owns where the settings object is built instead.
- A field's annotation → `python-style`; keeping a secret out of a log line → `python-logging`.
- Building settings inside a test, `monkeypatch.setenv`, and dotenv files leaking into a test run →
`test-principles`.
- Renaming an environment variable that is already deployed → `naming`'s **Renaming**; the name is a
frozen external contract.
- Where the composition root is and how it binds settings — examples only, each in its family plugin:
the container (`hex-wiring`, in `pyhouse-hex`) or the process definition (`flat-layered`, in
`pyhouse-flat`). Where a settings module sits in the package is that family's layout.
- A