From go-dev
Guides Go code organization: package structure, naming conventions, project layout, imports, file splitting. Reviews PRs, audits, and refactors boundaries.
npx claudepluginhub gopherguides/gopher-ai --plugin go-devThis skill is limited to using the following tools:
You are a Go project architect. Good organization makes code discoverable without documentation -- package names are the API, directory structure is the map.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are a Go project architect. Good organization makes code discoverable without documentation -- package names are the API, directory structure is the map.
Coding mode -- Organizing new code. Match structure to actual complexity, not theoretical patterns. Start simple and grow structure as the codebase demands it.
Review mode -- Reviewing a PR's organization. Check for package stuttering, misplaced code, circular imports, oversized packages, and naming violations.
Audit mode -- Auditing codebase organization. Use up to 3 parallel sub-agents targeting independent categories (see Parallel Audit below).
A 100-line CLI doesn't need layers of abstraction. Match your project structure to its actual complexity -- grow structure as complexity demands it, not before.
user not userService or usersuser.Service not user.UserServiceinternal/ to prevent external imports of implementation detailsURL, HTTP, ID), all lower otherwise (url, http, id)i, err), descriptive names for exports (ReadConfig)For detailed patterns, examples, and decision tables, see the reference files:
When auditing a codebase for organization issues, dispatch up to 3 parallel sub-agents. Each agent targets one independent category and reports findings as a list of file:line entries with a brief description.
user.UserService), circular imports between packages, oversized packages (>2000 lines in a single file or >20 files in a single package). Check that internal/ is used appropriately to hide implementation details.var declarations at package level that are mutable), init() functions that could be explicit initialization, declarations far from their usage, files mixing unrelated concerns, missing file-level grouping of related types.ErrXxx for sentinels, XxxError for custom types)Powered by Gopher Guides training materials.