golang-configuration
Load and validate application configuration from environment variables and config files. Use when managing Go application config with environment variables or viper.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 3
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 e1f63f36e0cd624f… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Golang Configuration
Priority: P1 (HIGH)
Principles
- 12-Factor App: Store config in environment variables.
- Typed Config: Load config into struct, validate immediately.
- Secrets: Never commit secrets. Use env vars or secret managers.
- No Globals: Return Config struct and inject it.
Implementation Workflow
- Define Config struct — Create typed struct with all required fields.
- Load defaults — Set sensible defaults for non-secret values.
- Override from file — Optionally load from YAML/JSON config file.
- Override from env — Environment variables take highest priority.
- Validate at startup — Crash immediately on missing required config.
- Inject via constructor — Pass Config to services; never use global config vars.
See config struct and usage examples
Libraries
- Standard Lib:
os.Getenvfor simple apps. - Viper: Industry standard for complex configs (env, files, remote).
- Koanf: Lighter, cleaner alternative to Viper.
- Caarlos0/env: Strict struct tagging approach.
Anti-Patterns
- No hardcoded secrets: load all secrets from env vars or secret manager.
- No global config vars: return typed Config struct and inject via constructors.
- No silent startup: crash immediately on missing required env vars.
References
Files
3- SKILL.md
ffa1abc2f91.8 KB - evals/evals.json
85972897ae1.8 KB - references/config-patterns.md
be645fa8751.3 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.