What problem does it solve? Repositories often have fragmented configuration spread across environment variables, dotenv files, JSON, appsettings, and secret providers, making it unsafe for agents and developers to inspect or change settings. This Skill discovers those mechanisms, classifies every signal, and produces a deterministic operational facade without creating a shadow configuration store. ## Core Features & Use Cases - Discovery and classification: Inventories configuration sources, consumers, loaders, and secret providers, assigning each signal a disposition such as MANAGED, CANDIDATE, or OBSOLETE. - Static contract and deterministic generation: Validates a state-free contract and generates a standardized configuration CLI plus seven agent/developer documents, with drift checking and byte-identical regeneration. - Safe candidate lifecycle: Approves ambiguous fields only with explicit authority and fingerprint verification, regenerating the facade and docs before marking candidates implemented. - Use Case: Point it at a Python or .NET repository whose settings are scattered across .env files and appsettings; it produces a contract, a config CLI with plan/apply semantics, and a complete agent handbook while leaving native runtime resolution untouched. ## Quick Start Ask the agent to run coferlandia-config-toolsmith against your repository to analyze its configuration and generate the standardized config CLI and documentation.
