go-sdk-bootstrap

What problem does it solve?

Manually wiring a Go service with github.com/trypanic/go-sdk is error-prone due to non-obvious conventions like package identifier divergences (e.g. the postgres directory uses the database package name), strict constructor triplet rules, and required initialization order that cannot be inferred from standard Go documentation alone. This Skill eliminates that guesswork to ensure correct, production-ready setup.

Core Features & Use Cases

• Canonical Wiring Rules: Encodes all go-sdk component mappings, package name divergences, and constructor usage (including the New / NewWithoutTracing / NewWithInstrumenter triplet) to avoid compile errors and misconfigured tracing/logging.
• Verified Bootstrap Template: Provides a tested main.go template that follows correct initialization order (OTLP setup before logger init, shared resource pools, deferred shutdown in reverse construction order) for reliable service startup.
• Guardrails & Best Practices: Includes strict errorkit error wrapping rules, a list of prohibited anti-patterns, and post-scaffold verification steps to ensure the service adheres to SDK standards.
• Use Case: Ideal for Go teams building new services with trypanic/go-sdk, or developers adding go-sdk components to existing services who want to avoid common pitfalls and ensure consistent, maintainable code.

Quick Start

Use the go-sdk-bootstrap skill to scaffold a new Go service with logger, telemetry, postgres, and messaging wired correctly according to trypanic/go-sdk conventions.