skills.rest
kaptinlin
kaptinlinCOMMUNITY
Explore all skills by this author →
GitHub

config-designing

Guides Go projects to select and implement optimal struct-based Config patterns with Options separation and migration paths.

23|2|Updated Jun 9, 2025
Search Tags:#migration#patterns#go#config#options#library-design#go-config
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill config-designing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: config-designing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/config-designing
Command: npx skills add https://github.com/kaptinlin/gozod --skill config-designing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Go projects often struggle to pick a configuration pattern that cleanly separates serializable config from runtime options. This guide helps you decide between Config struct + Options, Options Only, and go-config for applications, ensuring scalable, maintainable design.

Core Features & Use Cases

  • Decision patterns for library design and application wiring.
  • Guidance on migration from older constructors to Config + New(cfg, opts...).
  • Clear rules for zero-value defaults and separation of concerns.

Quick Start

Choose a pattern and implement it by creating a Config struct with a New(cfg, opts...) signature, or use an Options-Only constructor for runtime dependencies.

Frequently Asked Questions about config-designing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best Go config pattern for separating serializable config from runtime options?▼

The best Go config pattern uses a Config struct for serializable data and an Options struct for runtime dependencies, ensuring clear separation of concerns and maintainable application wiring.

How do I migrate an existing Go library constructor to a Config and Options pattern?▼

To migrate a Go library constructor, adopt the New(cfg, opts...) signature and follow backward-compatibility rules, allowing existing constructors to wrap or delegate to the new configuration struct pattern safely.

When should I use an Options Only pattern versus a Config struct in Go?▼

Use an Options Only pattern when dealing strictly with runtime dependencies, and choose a Config struct when your Go project requires serializable configuration with established zero-value defaults.

How do I handle default values in a Go configuration struct?▼

Handle default values in a Go configuration struct by enforcing zero-value defaults, allowing the system to initialize safely without explicit setup while providing overrides through runtime options.

Does the go-config pattern work for both Go libraries and applications?▼

The go-config pattern applies to both Go libraries and applications, providing decision patterns for library design and application wiring, alongside guidance for cross-cutting config composition.

Why does my Go library config pattern mix serializable settings with runtime dependencies?▼

Mixing serializable settings with runtime dependencies occurs without separation of concerns, which is resolved by implementing distinct Config and Options structs to decouple static configuration from dynamic runtime behavior.

Related Skills

Explore More Software Engineering Skills→
phant-appphant-app

go-functional-options

Implement Go functional options pattern with unexported struct and With* constructors.

Official
Advanced
muratmirgunmuratmirgun
8

go-functional-options

Design Go constructors using the functional options pattern.

Community
Intermediate
QunnnnQunnnn

go-uber-dig

Organize Go dependency injection wiring with uber-go/dig constructors.

Community
Intermediate
JylhisJylhis
1

golang-design-patterns

Guide idiomatic Go API design with functional options and validation.

Community
Advanced