What problem does it solve? It prevents configuration drift, hardcoded secrets, and inconsistent environment variables by enforcing a single contract for how .env files, Spring configuration binding, and sensitive values are created, renamed, and deleted. ## Core Features & Use Cases - Configuration Contract Enforcement: Requires every new environment variable to be added to both .env and .env.example, with UPPER_SNAKE_CASE naming and grouped prefixes like AI_, MYSQL_, REDIS_, AGENT_, and MCP_. - Secrets Protection: Prohibits hardcoding API keys, passwords, and tokens in Java code, application.yml, docs, logs, or Git commits, and mandates .env be gitignored while .env.example is committed. - Spring Boot Binding Rules: Standardizes loading .env through the native spring.config.import mechanism with a custom PropertySourceLoader, and prefers @ConfigurationProperties over scattered @Value usage. - Use Case: When adding a new AI embedding endpoint, the Skill guides you to add AI_EMBEDDING_BASE_URL to both env files, bind it via configuration properties, verify no duplicate keys exist, and validate startup. ## Quick Start Ask the AI to add a new environment variable for a third-party service API key following the configuration skill rules.
