skills.rest
joySUSY
joySUSYCOMMUNITY
Explore all skills by this author →
GitHub

go-coding-engine

Guides Go development with architecture, concurrency, error handling, testing, and toolchain references.

Updated Feb 21, 2026
Search Tags:#testing#concurrency#golang#go#error-handling#code-review#clean-architecture
One-click install
npx skills add https://github.com/joySUSY/violet-plugin-place --skill go-coding-engine-joysusy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: go-coding-engine
Source: https://github.com/joySUSY/violet-plugin-place/tree/main/plugins/go-coding-engine
Command: npx skills add https://github.com/joySUSY/violet-plugin-place --skill go-coding-engine-joysusy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing production-grade Go code requires consistent decisions across architecture, concurrency, error handling, testing, and tooling. This Skill consolidates those decisions into a single opinionated engine so Claude applies Clean Architecture, race-safe concurrency patterns, and disciplined error handling to every Go task instead of improvising each time. ## Core Features & Use Cases - Architecture-first design: Clean Architecture adapted for Go with domain, usecase, and adapter layers, plus a standard project layout (cmd/, internal/, pkg/). - Concurrency doctrine: Decision frameworks for goroutines, channels, errgroup, worker pools, pipelines, and race prevention with mandatory -race testing. - Error handling patterns: Wrapping with %w, sentinel errors, custom error types, errors.Join, and the Handle Once rule. - Testing and performance methodology: Table-driven tests, interface-based mocking, benchmarks, fuzzing, pprof profiling, and benchstat comparison. - Toolchain and ecosystem guidance: golangci-lint configuration, go vet, govulncheck, CI pipeline templates, library selection tables, and MCP server generation with the official Go SDK. - Use Case: Ask Claude to scaffold a new Go HTTP service, and it will produce a Clean Architecture layout with constructor injection, structured slog logging, graceful shutdown, table-driven tests, and a verification pipeline (build, vet, lint, race-tested). ## Quick Start Ask Claude to design or review any Go code, such as "build a concurrent job processing service in Go with tests", and the engine activates automatically on .go files and Go-related prompts.

Frequently Asked Questions about go-coding-engine

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

FAQPage Schema
How do I structure a Go project with Clean Architecture?▼

Organize code into cmd/ for entry points, internal/domain for pure business types and interfaces, internal/usecase for application logic, and internal/adapter for HTTP handlers and repository implementations. Imports flow inward only, and main.go wires dependencies via constructor injection.

How do I handle errors in Go without exceptions?▼

Return errors as values and wrap them with context using fmt.Errorf and the %w verb so callers can inspect them with errors.Is or errors.As. Handle each error once: either log it or return it, never both. Use sentinel errors for matchable conditions and custom types for structured details.

Should I use goroutines with channels or sync.Mutex in Go?▼

Prefer channels for passing data between goroutines and errgroup for coordination with error propagation. Use sync.Mutex or sync.RWMutex only when protecting simple shared state, and atomic types for counters. Every goroutine must have a known exit path via context cancellation.

What is the standard way to write tests in Go?▼

Use table-driven tests with t.Run subtests for multi-case scenarios, covering both success and error paths. Mock dependencies through small interfaces with function-field structs, and always run go test -race -count=1 to detect data races before declaring work complete.

Which Go linter should I use for production code?▼

Use golangci-lint, which aggregates over 50 linters including errcheck, staticcheck, gosec, and revive in a single pass. Combine it with go vet for suspicious constructs and govulncheck for dependency vulnerability scanning in your CI pipeline.

When should I not use an ORM in Go?▼

Avoid ORMs for simple queries where they hide performance characteristics. Prefer sqlc, which generates type-safe Go from SQL, or raw database/sql with the pgx driver for PostgreSQL. Reserve full ORMs like GORM only for teams committed to ActiveRecord-style patterns.

Related Skills

Explore More Software Engineering Skills→
pluginagentmarketplacepluginagentmarketplace
4

go-modules

Initialize, tidy, vendor, and verify Go modules across workspaces.

Community
Advanced
trungenglishtrungenglish
1

golang-gin-deploy

Containerize and deploy Go Gin APIs with multi-stage Docker builds and docker-compose.

Community
Advanced
kubuszokkubuszok
6

arch-native-bridge

Manage Rust C ABI interfacing with Scala for platform-specific FFI operations.

Official
Intermediate
astrovilleastroville

stack-detection

Detects project language and framework stacks to route engineering tasks to matching skills.

Official
Intermediate