tpscloud / gophers

# gophers
Skills for AI coding agents that work on Go programs:
- Cobra and pflag command-line interfaces
- Viper configuration
- Wails desktop apps, v2 and v3
The skills concentrate on the structural choices and library behavior that
cause real bugs rather than on syntax. Every library behavior a skill states
as fact has a test, and every Go example lives under `examples/`, built and
tested in CI against pinned module versions, so the guidance does not drift.
> [!NOTE]
> These are early versions of the skills. We have been dogfooding them for a
> few months. As CI gains more measures of how well each skill works, the
> results go into
> SECURITY.md
> alongside the security and quality reports.
## Skills
These are third-party skills and are not affiliated with the projects they
document.
SECURITY.md has the
independent security and quality reports.
**cobra**: command trees, flags, hooks, completion, generated docs, and testable output and exit codes
**viper**: layered file, environment, and flag configuration, typed decoding, and reloads
**wails2**: Wails v2 desktop apps: bound Go methods and generated bindings, the startup context and runtime calls, embedded assets, build tags, and Linux GTK3 and WebKitGTK dependencies
**wails3**: Wails v3 desktop apps, a prerelease: services and generated bindings, errors as rejected promises, typed events, dialogs and windows, the wails3 CLI and Taskfile, server mode, and cgo with GTK4 and WebKitGTK 6.0 on Linux
The cobra and viper skills are separate on purpose: Cobra does not need Viper,
and neither skill adds it to a program that does not need layered
configuration.
## Install
Install with Vercel's skills CLI :
 [code] 
> [!NOTE]
> This is the recommended route. One command installs into Claude Code, Codex,
> and dozens of other agents from one shared copy, either per project (committed
> with your code) or for your user. It needs no clone, and `npx skills update`
> pulls new versions later.
It asks which skills and agents to install. Add `--skill cobra` (repeatable)
to pick skills, `-a claude-code` or `-a codex` to pick an agent, and `-g` to
install for your user instead of the current project. `--list` shows the
skills without installing.
### From a checkout
The skills also load straight from a clone of this repository. Replace
`/path/to/gophers` with its absolute path.
Claude Code, as a plugin for one session (skills are then named
`/gophers:cobra` and so on):
 [code] 
Claude Code or Codex, as personal skills that stay installed:
 [code] 
Start a new session afterwards. Symlinked skills follow the checkout, so keep
it in place.
### Examples
The Go programs the skills cite live in `examples/ /`, one Go module per
skill so each keeps its own pinned versions. An installed skill links to them
on GitHub. To run one, clone the repository and work from its module, for
example `cd examples/cobra && go run ./cli/cmd/catalog list --json` or
`go test ./...`.
## Development
AGENTS.md has the editing rules. CI uses