Go development patterns: testing, concurrency, errors, review, and conventions.
npx skills add https://github.com/notque/vexjoy-agent --skill go-patterns
Umbrella skill for Go development: testing, concurrency, error handling, failure modes,
code review, SAP CC conventions, and quality gates. Routes to the correct reference
based on the Go task at hand.
| Signal | Load These Files | Why |
|---|---|---|
| Testing | testing.md | Writing, fixing, or reviewing Go tests |
| Concurrency | concurrency.md | Goroutines, channels, sync primitives, race conditions |
| Error handling | error-handling.md | Error wrapping, sentinels, custom types, errors.Is/As |
| Review patterns | preferred-patterns.md | Detecting code smells, over-engineering, bad Go patterns |
| Code review | code-review.md | Reviewing Go code or PRs for quality |
| SAP CC conventions | sapcc-conventions.md | Working in sapcc/* repos with go-bits |
| Quality gate | quality-gate.md | Running make check, linting, pre-commit validation |
Classify the task into one or more domains, then load the corresponding reference files.
Only load what is needed -- do not load all references for every task.
| Domain | Load Reference | When |
|--------|---------------|------|
| Testing | references/testing.md | Writing, fixing, or reviewing Go tests |
| Concurrency | references/concurrency.md | Goroutines, channels, sync primitives, race conditions |
| Error handling | references/error-handling.md | Error wrapping, sentinels, custom types, errors.Is/As |
| Review patterns | references/preferred-patterns.md | Detecting code smells, over-engineering, bad Go patterns |
| Code review | references/code-review.md | Reviewing Go code or PRs for quality |
| SAP CC conventions | references/sapcc-conventions.md | Working in sapcc/* repos with go-bits |
| Quality gate | references/quality-gate.md | Running make check, linting, pre-commit validation |
Multiple domains may apply. For example, reviewing a PR that includes concurrency code
should load both code-review.md and concurrency.md.
Read the selected reference file(s) using ${CLAUDE_SKILL_DIR}/references/<name>.md.
Each reference contains the full methodology, phases, code examples, and error handling
for that domain. Follow the instructions in the reference as if they were this skill's
instructions.
Some references point to their own sub-reference files for extended patterns:
Testing sub-references:
${CLAUDE_SKILL_DIR}/references/testing/go-test-patterns.md -- Full table-driven test, helper, mock examples${CLAUDE_SKILL_DIR}/references/testing/go-benchmark-and-concurrency.md -- b.Loop() benchmarks, synctestConcurrency sub-references:
${CLAUDE_SKILL_DIR}/references/concurrency/concurrency-patterns.md -- Worker pool, fan-out/fan-in, pipeline, rate limiter, graceful shutdownError handling sub-references:
${CLAUDE_SKILL_DIR}/references/error-handling/patterns.md -- gopls tracing, HTTP handler patterns, error wrapping in middlewareReview-pattern sub-references:
${CLAUDE_SKILL_DIR}/references/preferred-patterns/code-examples.md -- Extended before/after for all 7 failure modesCode review sub-references:
${CLAUDE_SKILL_DIR}/references/code-review/common-review-comments.md -- Go code patterns with good/bad examplesSAP CC conventions sub-references:
${CLAUDE_SKILL_DIR}/references/sapcc-conventions/sapcc-code-patterns.md -- Primary reference: code patterns, testing patterns, failure modes (merged from testing-patterns-detailed.md and preferred-patterns.md)${CLAUDE_SKILL_DIR}/references/sapcc-conventions/library-reference.md -- Complete approved/restricted library table${CLAUDE_SKILL_DIR}/references/sapcc-conventions/architecture-patterns.md -- Full 102-rule architecture spec${CLAUDE_SKILL_DIR}/references/sapcc-conventions/review-standards.md -- Lead + secondary review standards (merged)${CLAUDE_SKILL_DIR}/references/sapcc-conventions/extended-patterns.md -- Security, K8s, PR hygiene patternsapi-design-detailed.md, build-ci-detailed.md, error-handling-detailed.md,go-bits-philosophy-detailed.md, pr-mining-insights.md
Quality gate sub-references:
${CLAUDE_SKILL_DIR}/references/quality-gate/common-lint-errors.json -- Linter descriptions and fix suggestions${CLAUDE_SKILL_DIR}/references/quality-gate/makefile-targets.json -- Available make targets${CLAUDE_SKILL_DIR}/references/quality-gate/expert-review-patterns.md -- Manual review patterns${CLAUDE_SKILL_DIR}/references/quality-gate/examples.md -- Detailed usage examplesFollow the loaded reference methodology. Each reference has its own phases, gates,
and completion criteria. Apply them as written.
Scripts are organized by domain in sub-directories:
scripts/gen-table-test.sh, scripts/bench-compare.shscripts/check-errors.shscripts/check-interface-compliance.shscripts/check-sapcc-identify-endpoint.sh, scripts/check-sapcc-auth-ordering.sh,scripts/check-sapcc-json-strict.sh, scripts/check-sapcc-time-now.sh, scripts/check-sapcc-httptest.sh,
scripts/check-sapcc-todo-format.sh
scripts/quality_checker.py, scripts/validate.pyErrors are domain-specific. Load the relevant reference file and check its Error Handling
section for troubleshooting guidance.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Take notque/go-patterns from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.