Go Data Structures

What it does

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.

When to use it

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.

What's included

• Scripts: none (has_references=true — rich reference docs linked in the repo)
• References: slice internals, map internals, containers, pointers, generics and more (in-repo references/ folder)
• Instructions: concise best-practices, growth rules, preallocation patterns, and code examples for common pitfalls and correct patterns.

Compatible agents

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.