Agent skill · operations · aj-geddes
configuration-management
Manage application configuration including environment variables, settings management, configuration hierarchies, secret management, feature flags, and 12-factor app principles. Use for config, environment setup, or settings management.
Why this skill is useful
Provides specific patterns and practices for managing application configuration that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
Configuration Management Table of Contents Overview When to Use Quick Start Reference Guides Best Practices Overview Comprehensive guide to managing application configuration across environments, including environment variables, configuration files, secrets, feature flags, and following 12-factor app methodology. When to Use Setting up configuration for different environments Managing secrets and credentials Implementing feature flags Creating configuration hierarchies Following 12-factor app principles Migrating configuration to cloud services Implementing dynamic configuration Managing multi-tenant configurations Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- Environment Variables Environment Variables Configuration Hierarchies Configuration Hierarchies Secret Management Secret Management Feature Flags Feature Flags 12-Factor App Configuration 12-Factor App Configuration Configuration Validation Configuration Validation Dynamic Configuration (Remote Config) Dynamic Configuration (Remote Config) Best Practices ✅ DO Store configuration in environment variables Use different config files per environment Validate configuration on startup Use secret managers for sensitive data Never commit secrets to version control Provide sensible defaults Document all configuration options Use type-safe configuration objects Implement configuration hierarchy (base + overrides) Use feature flags for gradual rollouts Follow 12-factor app principles Implement graceful degradation for missing config Cache secrets to reduce API calls ❌ DON'T Hardcode configuration in source code Commit .env files with real secrets Use different config formats across services Store secrets in plain text Expose configuration through APIs Use production credentials in development Ignore configuration validation errors Access process.env directly everywhere Store configuration in databases (circular dependency) Mix configura …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/configuration-management