back
loading skill details...
Use when creating Go packages, organizing imports, managing dependencies, or deciding how to structure Go code into packages. Also use when starting a new Go…
Go Packages and Imports When this skill does NOT apply: For naming individual identifiers within a package, see go-naming. For organizing functions within a single file, see go-functions. For configuring linters that enforce import rules, see go-linting. Package Organization Avoid Util Packages Package names should describe what the package provides. Avoid generic names like util, helper, common — they obscure meaning and cause import conflicts. // Good: Meaningful package names db := spannertest.NewDatabaseFromFile(...) _, err := f.Seek(0, io.SeekStart)
don't have the plugin yet? install it then click "run inline in claude" again.