Specx Settings
Add runtime configuration to specx Python services with `pydantic-settings`. Use when creating settings classes, environment variables, `.env.example`, injecting settings at delivery, infrastructure, or composition edges, documenting config, mapping configuration into typed core policy collaborators, or removing direct environment reads from core code.
Install
npx skills add maksimzayats/specx --skill specx-settingsgit clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p ~/.claude/skills
cp -r /tmp/specx/.agents/skills/specx-settings ~/.claude/skills/specx-settingsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# specx Settings
Use this skill whenever runtime configuration is needed. Read
`references/settings.md` before adding settings code.
## Rules
- Model runtime config with classes that inherit `BaseRuntimeSettings`.
- Give each settings class a docstring that explains the configuration scope
and includes a concrete `Example:`.
- Place settings near the class that consumes them unless the setting is truly
application-wide.
- Logging settings are application-wide and live beside
`infrastructure/logging/configurator.py` and its `LoggingConfigurator`.
- Use `BaseStrEnum` for finite configuration values such as logging levels.
- Inject settings objects only into delivery, infrastructure, and composition
classes. Do not inject `BaseRuntimeSettings` subclasses into core use cases,
services, capabilities, entities, repositories, or gateway ports.
- When configuration represents a genuine business policy, map it at the
composition root into a typed core value or capability that has no dependency
on Pydantic or `BaseRuntimeSettings`.
- Let `diwire` auto-register settings as root-scoped singletons. Register a
settings instance explicitly only for an intentional override.
- At operational entrypoints, load required runtime values with
`SettingsClass.from_environment()`. Build explicit test or composition
overrides with `SettingsClass.model_validate({...})` so strict type checking
does not mistake raw input strings for already-validated field types.Details
- Skill name
specx-settings- Repository
- maksimzayats/specx
- Path
.agents/skills/specx-settings/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Specx Settings skill do?
Add runtime configuration to specx Python services with `pydantic-settings`. Use when creating settings classes, environment variables, `.env.example`, injecting settings at delivery, infrastructure, or composition edges, documenting config, mapping configuration into typed core policy collaborators, or removing direct environment reads from core code.
How do I install the Specx Settings skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add maksimzayats/specx --skill specx-settings. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Specx Settings popular?
It lives in maksimzayats/specx, which has 198 GitHub stars and 33 forks.
Related skills
Specx Add Core Service
198maksimzayats/specx
Add or refactor a specx core scope service. Use when implementing focused reusable business/application behavior under a core scope services package, extracting logic from a use case, injecting deterministic collaborators, accepting an active unit of work, choosing between Service and Capability, or keeping business decisions away from delivery and infrastructure.
Specx Add Core Use Case
198maksimzayats/specx
Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope use_cases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into class-based application code.
Specx Add Delivery Controller
198maksimzayats/specx
Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.
Abi and Calling Conventions
293mohitmishra786/low-level-dev-skills
ABI and calling conventions skill for cross-language boundaries. Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Activates on queries about calling convention, ABI, System V AMD64, AAPCS, stack frame, variadic function, or FFI registers.
Specx Project Structure
198maksimzayats/specx
Create or reshape a Python FastAPI service repo into the specx clean core/delivery architecture using packaged scoped foundation bases. Use when starting an API backend, adding the first src package, or establishing `AGENTS.md`, `core/`, optional local `foundation/`, `delivery/`, infrastructure, `ioc/`, migrations, and tests.
Af Xdp
293mohitmishra786/low-level-dev-skills
AF_XDP skill for high-performance XDP sockets. Use when creating AF_XDP sockets, configuring UMEM and XSK rings, XDP_REDIRECT programs, copy vs zero-copy mode, or comparing with DPDK. Activates on queries about AF_XDP, xsk_umem, XDP_REDIRECT, libbpf xsk, or zero-copy XDP.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.