go-design-principles

What problem does it solve?

This Skill eliminates the risk of writing inconsistent, non-idiomatic Go code that violates core design principles, which leads to hard-to-maintain codebases, frequent bugs, and onboarding friction for team members.

Core Features & Use Cases

• SOLID Principles Reframed for Go: Adapts classic SOLID rules (SRP, OCP, LSP, ISP, DIP) to Go's composition and interface-first paradigm, avoiding unnecessary object-oriented ceremony.
• Idiomatic Design Guardrails: Enforces best practices including consumer-owned interfaces, forbidden generic package names (util/common/helpers), primitive type wrapping, immutability, and feature envy detection to keep code clear and maintainable.
• Type-Driven Design Guidance: Supports creation of sealed sum-type interfaces, state machine models, and validating constructors to make illegal states unrepresentable at compile time.
• Use Case: Use this Skill during Go code reviews, when designing new domain models or packages, or when refactoring legacy Go code to align with team design standards and reduce technical debt.

Quick Start

Request a design review of your Go package to identify violations of SOLID principles, generic naming, and feature envy, and get actionable refactoring guidance aligned with Go best practices.