← ClaudeAtlas

python-settingslisted

Use when a program reads configuration from its environment — writing or extending a settings class, deciding whether a field gets a default, carrying a secret, or deciding where the settings object is built and how its values reach the code that uses them. Owns one settings class per configured component, the non-strict namespace, no default on a required field or a tunable, the secret type and where it is unwrapped, derived values, validation that only normalizes or rejects, construction at the composition root, and what a library reads (nothing, when published). The prefix's name is `naming`; nothing built at import time is `python-packaging`. - Also when asked for a config class, an env var, a `.env` file, a `BaseSettings` subclass, an API key or password field, a timeout or pool-size default, `os.getenv` in a module, or where to build the settings object.
wntic/pyhouse · ★ 3 · Code & Development · score 76
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