
from cc-skills-golang1,476
Authoritative guidance on choosing and using Go built-in and standard-library data structures, with practical best practices for slices, maps, arrays, container
Practical, engineer-focused guidance for selecting and optimizing Go data structures. Covers slice and map internals, capacity growth and preallocation, arrays vs slices, container/heap/list/ring usage, strings.Builder vs bytes.Buffer, generic collections, unsafe and weak pointers, and copy semantics. The skill provides concrete rules, code snippets, and cross-references to deeper reference docs included in the repo.
Use this skill when deciding which Go data structure to use for performance or correctness, when optimizing memory/copy behavior, when implementing generic containers, or when debugging slice/map aliasing and pointer safety issues. Useful during code reviews, performance tuning, and library design.
Designed for AI coding assistants and CLI-capable agents (Claude Code, Copilot/Code assistants, Cursor, Codex-style tools) that can read repo docs and run Go tooling.
A well-structured Go data structures reference skill covering slices, maps, arrays, container/ packages, generics, and pointers. No bundled scripts — pure knowledge skill with detailed SKILL.md and references/ deep dives. Clean frontmatter, specific triggers, good cross-references to sibling skills in the cc-skills-golang collection. No security concerns whatsoever.
High-quality reference skill from samber/cc-skills-golang collection. Exemplary architecture with progressive disclosure via references/ directory. Zero security surface — no scripts, no shell commands, no network calls.
samber/hot — In-memory Caching for Go
Guidance and patterns for using samber/hot in Go: eviction algorithms, TTL, loaders, sharding, stale-while-revalidate, and Prometheus monitoring.
Golang Code Style
Human-coded Go style guidelines for clarity, function design, control flow, and idiomatic practices — use when writing or reviewing Go code, creating linters, o