From golang-boost
Guides the boost.Start() boot sequence for Go services using github.com/xgodev/boost: config registry loading, structured logger setup, and correct ordering in main.go.
How this skill is triggered — by the user, by Claude, or both
Slash command
/golang-boost:boost-startThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```go
boost.Start() is the first line of mainpackage main
import "github.com/xgodev/boost"
func main() {
boost.Start() // ALWAYS first.
// ... everything else ...
}
Start does three things, in order:
Start, calls to config.String/Int/Bool/Duration return real values; before, they return zero-values.Start, log.FromContext(ctx) returns the configured logger; before, it returns a no-op.config.Add key.| Symptom | Cause | Fix |
|---|---|---|
Factory constructor (echo.NewServer, fpubsub.NewClient, etc.) before boost.Start() | Constructor reads config that isn't loaded yet | Reorder: boost.Start() first |
log.FromContext(ctx) returns silent / no-op logger | Start never ran | Add boost.Start() as the first statement of main |
config.String("foo") returns "" even though env var is set | Same — registry empty | Same — boost.Start() first |
boost-wrapper-config.boost-wrapper-log.npx claudepluginhub xgodev/boost --plugin golang-boostWrites or reviews structured logging in Go services using github.com/xgodev/boost/wrapper/log. Handles logger creation, enrichment with fields, and migration from standard Go loggers.
Guides Go developers on structured logging with slog: choosing log levels, configuring handlers, writing key-value pairs, and adding request-scoped context for production observability.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.