[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ZFQY6BDKTYKJCYP9HAT2K":3,"skill-same:01M79ZFQY6BDKTYKJCYP9HAT2K":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":59},"01M79ZFQY6BDKTYKJCYP9HAT2K","golang-data-structures",null,"Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container\u002Flist\u002Fheap\u002Fring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container\u002F packages, unsafe or weak pointers, or questioning slice\u002Fmap internals. Not for applying optimization patterns once profiling has identified a bottleneck (→ See `samber\u002Fcc-skills-golang@golang-performance` skill).","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-data-structures\ndescription: \"Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container\u002Flist\u002Fheap\u002Fring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container\u002F packages, unsafe or weak pointers, or questioning slice\u002Fmap internals. Not for applying optimization patterns once profiling has identified a bottleneck (→ See `samber\u002Fcc-skills-golang@golang-performance` skill).\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.2.2\"\n  openclaw:\n    emoji: \"🗃\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__* mcp__context7__resolve-library-id mcp__context7__query-docs\npaths:\n  - \"**\u002F*.go\"\n---\n\n**Persona:** You are a Go engineer who understands data structure internals. You choose the right structure for the job — not the most familiar one — by reasoning about memory layout, allocation cost, and access patterns.\n\n# Go Data Structures\n\nBuilt-in and standard library data structures: internals, correct usage, and selection guidance.\n\n- For safety pitfalls (nil maps, append aliasing, defensive copies) see `samber\u002Fcc-skills-golang@golang-safety` skill.\n- For channels and sync primitives see `samber\u002Fcc-skills-golang@golang-concurrency` skill.\n- For string\u002Fbyte\u002Frune choice see `samber\u002Fcc-skills-golang@golang-design-patterns` skill.\n\n## Best Practices Summary\n\n1. **Preallocate slices and maps** with `make(T, 0, n)` \u002F `make(map[K]V, n)` when size is known or estimable — avoids repeated growth copies and rehashing\n2. **Arrays** SHOULD be preferred over slices only for fixed, compile-time-known sizes (hash digests, IPv4 addresses, matrix dimensions)\n3. **NEVER rely on slice capacity growth timing** — the growth algorithm changed between Go versions and may change again; your code should not depend on when a new backing array is allocated\n4. **Use `container\u002Fheap`** for priority queues, **`container\u002Flist`** only when frequent middle insertions are needed, **`container\u002Fring`** for fixed-size circular buffers\n5. **`strings.Builder`** MUST be preferred for building strings; **`bytes.Buffer`** MUST be preferred for bidirectional I\u002FO (implements both `io.Reader` and `io.Writer`)\n6. Generic data structures SHOULD use the **tightest constraint** possible — `comparable` for keys, custom interfaces for ordering\n7. **`unsafe.Pointer`** MUST only follow the 6 valid conversion patterns from the Go spec — NEVER store in a `uintptr` variable across statements\n8. **`weak.Pointer[T]`** (Go 1.24+) SHOULD be used for caches and canonicalization maps to allow GC to reclaim entries\n\n## Slice Internals\n\nA slice is a 3-word header: pointer, length, capacity. Multiple slices can share a backing array (→ see `samber\u002Fcc-skills-golang@golang-safety` for aliasing traps and the header diagram).\n\n### Capacity Growth\n\n- \u003C 256 elements: capacity doubles\n- > = 256 elements: grows by ~25% (`newcap += (newcap + 3*256) \u002F 4`)\n- Each growth copies the entire backing array — O(n)\n\n### Preallocation\n\n```go\n\u002F\u002F Exact size known\nusers := make([]User, 0, len(ids))\n\n\u002F\u002F Approximate size known\nresults := make([]Result, 0, estimatedCount)\n\n\u002F\u002F Pre-grow before bulk append (Go 1.21+)\ns = slices.Grow(s, additionalNeeded)\n```\n\n### `slices` Package (Go 1.21+)\n\nKey functions: `Sort`\u002F`SortFunc`, `BinarySearch`, `Contains`, `Compact`, `Grow`. For `Clone`, `Equal`, `DeleteFunc` → see `samber\u002Fcc-skills-golang@golang-safety` skill.\n\n**[Slice Internals Deep Dive](.\u002Freferences\u002Fslice-internals.md)** — Full `slices` package reference, growth mechanics, `len` vs `cap`, header copying, backing array aliasing.\n\n## Map Internals\n\nMaps are hash tables with 8-entry buckets and overflow chains. They are reference types — assigning a map copies the pointer, not the data.\n\n### Preallocation\n\n```go\nm := make(map[string]*User, len(users)) \u002F\u002F avoids rehashing during population\n```\n\n### `maps` Package Quick Reference (Go 1.21+)\n\n| Function          | Purpose                      |\n| ----------------- | ---------------------------- |\n| `Collect` (1.23+) | Build map from iterator      |\n| `Insert` (1.23+)  | Insert entries from iterator |\n| `All` (1.23+)     | Iterator over all entries    |\n| `Keys`, `Values`  | Iterators over keys\u002Fvalues   |\n\nFor `Clone`, `Equal`, sorted iteration → see `samber\u002Fcc-skills-golang@golang-safety` skill.\n\n**[Map Internals Deep Dive](.\u002Freferences\u002Fmap-internals.md)** — How Go maps store and hash data, bucket overflow chains, why maps never shrink (and what to do about it), comparing map performance to alternatives.\n\n## Arrays\n\nFixed-size, value types. Copied entirely on assignment. Use for compile-time-known sizes:\n\n```go\ntype Digest [32]byte           \u002F\u002F fixed-size, value type\nvar grid [3][3]int             \u002F\u002F multi-dimensional\ncache := map[[2]int]Result{}   \u002F\u002F arrays are comparable — usable as map keys\n```\n\nPrefer slices for everything else — arrays cannot grow and pass by value (expensive for large sizes).\n\n## container\u002F Standard Library\n\n| Package | Data Structure | Best For |\n| --- | --- | --- |\n| `container\u002Flist` | Doubly-linked list | LRU caches, frequent middle insertion\u002Fremoval |\n| `container\u002Fheap` | Min-heap (priority queue) | Top-K, scheduling, Dijkstra |\n| `container\u002Fring` | Circular buffer | Rolling windows, round-robin |\n| `bufio` | Buffered reader\u002Fwriter\u002Fscanner | Efficient I\u002FO with small reads\u002Fwrites |\n\nContainer types use `any` (no type safety) — consider generic wrappers. **[Container Patterns, bufio, and Examples](.\u002Freferences\u002Fcontainers.md)** — When to use each container type, generic wrappers to add type safety, and `bufio` patterns for efficient I\u002FO.\n\n## strings.Builder vs bytes.Buffer\n\nUse `strings.Builder` for pure string concatenation (avoids copy on `String()`), `bytes.Buffer` when you need `io.Reader` or byte manipulation. Both support `Grow(n)`. **[Details and comparison](.\u002Freferences\u002Fcontainers.md)**\n\n## Generic Collections (Go 1.18+)\n\nUse the tightest constraint possible. `comparable` for map keys, `cmp.Ordered` for sorting, custom interfaces for domain-specific ordering.\n\n```go\ntype Set[T comparable] map[T]struct{}\n\nfunc (s Set[T]) Add(v T)          { s[v] = struct{}{} }\nfunc (s Set[T]) Contains(v T) bool { _, ok := s[v]; return ok }\n```\n\n**[Writing Generic Data Structures](.\u002Freferences\u002Fgenerics.md)** — Using Go 1.18+ generics for type-safe containers, understanding constraint satisfaction, and building domain-specific generic types.\n\n## Pointer Types\n\n| Type | Use Case | Zero Value |\n| --- | --- | --- |\n| `*T` | Normal indirection, mutation, optional values | `nil` |\n| `unsafe.Pointer` | FFI, low-level memory layout (6 spec patterns only) | `nil` |\n| `weak.Pointer[T]` (1.24+) | Caches, canonicalization, weak references | N\u002FA |\n\n**[Pointer Types Deep Dive](.\u002Freferences\u002Fpointers.md)** — Normal pointers, `unsafe.Pointer` (the 6 valid spec patterns), and `weak.Pointer[T]` for GC-safe caches that don't prevent cleanup.\n\n## Copy Semantics Quick Reference\n\n| Type | Copy Behavior | Independence |\n| --- | --- | --- |\n| `int`, `float`, `bool`, `string` | Value (deep copy) | Fully independent |\n| `array`, `struct` | Value (deep copy) | Fully independent |\n| `slice` | Header copied, backing array shared | Use `slices.Clone` |\n| `map` | Reference copied | Use `maps.Clone` |\n| `channel` | Reference copied | Same channel |\n| `*T` (pointer) | Address copied | Same underlying value |\n| `interface` | Value copied (type + value pair) | Depends on held type |\n\n## Third-Party Libraries\n\nFor advanced data structures (trees, sets, queues, stacks) beyond the standard library:\n\n- **`emirpasic\u002Fgods`** — comprehensive collection library (trees, sets, lists, stacks, maps, queues)\n- **`deckarep\u002Fgolang-set`** — thread-safe and non-thread-safe set implementations\n- **`gammazero\u002Fdeque`** — fast double-ended queue\n\nWhen using third-party libraries, refer to their official documentation and code examples for current API signatures.\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) — prefer it over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-performance` skill for struct field alignment, memory layout optimization, and cache locality\n- → See `samber\u002Fcc-skills-golang@golang-safety` skill for nil map\u002Fslice pitfalls, append aliasing, defensive copying, `slices.Clone`\u002F`Equal`\n- → See `samber\u002Fcc-skills-golang@golang-concurrency` skill for channels, `sync.Map`, `sync.Pool`, and all sync primitives\n- → See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for `string` vs `[]byte` vs `[]rune`, iterators, streaming\n- → See `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill for struct composition, embedding, and generics vs `any`\n- → See `samber\u002Fcc-skills-golang@golang-code-style` skill for slice\u002Fmap initialization style\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Growing a slice in a loop without preallocation | Each growth copies the entire backing array — O(n) per growth. Use `make([]T, 0, n)` or `slices.Grow` |\n| Using `container\u002Flist` when a slice would suffice | Linked lists have poor cache locality (each node is a separate heap allocation). Benchmark first |\n| `bytes.Buffer` for pure string building | Buffer's `String()` copies the underlying bytes. `strings.Builder` avoids this copy |\n| `unsafe.Pointer` stored as `uintptr` across statements | GC can move the object between statements — the `uintptr` becomes a dangling reference |\n| Large struct values in maps (copying overhead) | Map access copies the entire value. Use `map[K]*V` for large value types to avoid the copy |\n\n## References\n\n- [Go Data Structures (Russ Cox)](https:\u002F\u002Fresearch.swtch.com\u002Fgodata)\n- [The Go Memory Model](https:\u002F\u002Fgo.dev\u002Fref\u002Fmem)\n- [Effective Go](https:\u002F\u002Fgo.dev\u002Fdoc\u002Feffective_go)\n","**Persona:** You are a Go engineer who understands data structure internals. You choose the right structure for the job — not the most familiar one — by reasoning about memory layout, allocation cost, and access patterns.\n\n# Go Data Structures\n\nBuilt-in and standard library data structures: internals, correct usage, and selection guidance.\n\n- For safety pitfalls (nil maps, append aliasing, defensive copies) see `samber\u002Fcc-skills-golang@golang-safety` skill.\n- For channels and sync primitives see `samber\u002Fcc-skills-golang@golang-concurrency` skill.\n- For string\u002Fbyte\u002Frune choice see `samber\u002Fcc-skills-golang@golang-design-patterns` skill.\n\n## Best Practices Summary\n\n1. **Preallocate slices and maps** with `make(T, 0, n)` \u002F `make(map[K]V, n)` when size is known or estimable — avoids repeated growth copies and rehashing\n2. **Arrays** SHOULD be preferred over slices only for fixed, compile-time-known sizes (hash digests, IPv4 addresses, matrix dimensions)\n3. **NEVER rely on slice capacity growth timing** — the growth algorithm changed between Go versions and may change again; your code should not depend on when a new backing array is allocated\n4. **Use `container\u002Fheap`** for priority queues, **`container\u002Flist`** only when frequent middle insertions are needed, **`container\u002Fring`** for fixed-size circular buffers\n5. **`strings.Builder`** MUST be preferred for building strings; **`bytes.Buffer`** MUST be preferred for bidirectional I\u002FO (implements both `io.Reader` and `io.Writer`)\n6. Generic data structures SHOULD use the **tightest constraint** possible — `comparable` for keys, custom interfaces for ordering\n7. **`unsafe.Pointer`** MUST only follow the 6 valid conversion patterns from the Go spec — NEVER store in a `uintptr` variable across statements\n8. **`weak.Pointer[T]`** (Go 1.24+) SHOULD be used for caches and canonicalization maps to allow GC to reclaim entries\n\n## Slice Internals\n\nA slice is a 3-word header: pointer, length, capacity. Multiple slices can share a backing array (→ see `samber\u002Fcc-skills-golang@golang-safety` for aliasing traps and the header diagram).\n\n### Capacity Growth\n\n- \u003C 256 elements: capacity doubles\n- > = 256 elements: grows by ~25% (`newcap += (newcap + 3*256) \u002F 4`)\n- Each growth copies the entire backing array — O(n)\n\n### Preallocation\n\n```go\n\u002F\u002F Exact size known\nusers := make([]User, 0, len(ids))\n\n\u002F\u002F Approximate size known\nresults := make([]Result, 0, estimatedCount)\n\n\u002F\u002F Pre-grow before bulk append (Go 1.21+)\ns = slices.Grow(s, additionalNeeded)\n```\n\n### `slices` Package (Go 1.21+)\n\nKey functions: `Sort`\u002F`SortFunc`, `BinarySearch`, `Contains`, `Compact`, `Grow`. For `Clone`, `Equal`, `DeleteFunc` → see `samber\u002Fcc-skills-golang@golang-safety` skill.\n\n**[Slice Internals Deep Dive](.\u002Freferences\u002Fslice-internals.md)** — Full `slices` package reference, growth mechanics, `len` vs `cap`, header copying, backing array aliasing.\n\n## Map Internals\n\nMaps are hash tables with 8-entry buckets and overflow chains. They are reference types — assigning a map copies the pointer, not the data.\n\n### Preallocation\n\n```go\nm := make(map[string]*User, len(users)) \u002F\u002F avoids rehashing during population\n```\n\n### `maps` Package Quick Reference (Go 1.21+)\n\n| Function          | Purpose                      |\n| ----------------- | ---------------------------- |\n| `Collect` (1.23+) | Build map from iterator      |\n| `Insert` (1.23+)  | Insert entries from iterator |\n| `All` (1.23+)     | Iterator over all entries    |\n| `Keys`, `Values`  | Iterators over keys\u002Fvalues   |\n\nFor `Clone`, `Equal`, sorted iteration → see `samber\u002Fcc-skills-golang@golang-safety` skill.\n\n**[Map Internals Deep Dive](.\u002Freferences\u002Fmap-internals.md)** — How Go maps store and hash data, bucket overflow chains, why maps never shrink (and what to do about it), comparing map performance to alternatives.\n\n## Arrays\n\nFixed-size, value types. Copied entirely on assignment. Use for compile-time-known sizes:\n\n```go\ntype Digest [32]byte           \u002F\u002F fixed-size, value type\nvar grid [3][3]int             \u002F\u002F multi-dimensional\ncache := map[[2]int]Result{}   \u002F\u002F arrays are comparable — usable as map keys\n```\n\nPrefer slices for everything else — arrays cannot grow and pass by value (expensive for large sizes).\n\n## container\u002F Standard Library\n\n| Package | Data Structure | Best For |\n| --- | --- | --- |\n| `container\u002Flist` | Doubly-linked list | LRU caches, frequent middle insertion\u002Fremoval |\n| `container\u002Fheap` | Min-heap (priority queue) | Top-K, scheduling, Dijkstra |\n| `container\u002Fring` | Circular buffer | Rolling windows, round-robin |\n| `bufio` | Buffered reader\u002Fwriter\u002Fscanner | Efficient I\u002FO with small reads\u002Fwrites |\n\nContainer types use `any` (no type safety) — consider generic wrappers. **[Container Patterns, bufio, and Examples](.\u002Freferences\u002Fcontainers.md)** — When to use each container type, generic wrappers to add type safety, and `bufio` patterns for efficient I\u002FO.\n\n## strings.Builder vs bytes.Buffer\n\nUse `strings.Builder` for pure string concatenation (avoids copy on `String()`), `bytes.Buffer` when you need `io.Reader` or byte manipulation. Both support `Grow(n)`. **[Details and comparison](.\u002Freferences\u002Fcontainers.md)**\n\n## Generic Collections (Go 1.18+)\n\nUse the tightest constraint possible. `comparable` for map keys, `cmp.Ordered` for sorting, custom interfaces for domain-specific ordering.\n\n```go\ntype Set[T comparable] map[T]struct{}\n\nfunc (s Set[T]) Add(v T)          { s[v] = struct{}{} }\nfunc (s Set[T]) Contains(v T) bool { _, ok := s[v]; return ok }\n```\n\n**[Writing Generic Data Structures](.\u002Freferences\u002Fgenerics.md)** — Using Go 1.18+ generics for type-safe containers, understanding constraint satisfaction, and building domain-specific generic types.\n\n## Pointer Types\n\n| Type | Use Case | Zero Value |\n| --- | --- | --- |\n| `*T` | Normal indirection, mutation, optional values | `nil` |\n| `unsafe.Pointer` | FFI, low-level memory layout (6 spec patterns only) | `nil` |\n| `weak.Pointer[T]` (1.24+) | Caches, canonicalization, weak references | N\u002FA |\n\n**[Pointer Types Deep Dive](.\u002Freferences\u002Fpointers.md)** — Normal pointers, `unsafe.Pointer` (the 6 valid spec patterns), and `weak.Pointer[T]` for GC-safe caches that don't prevent cleanup.\n\n## Copy Semantics Quick Reference\n\n| Type | Copy Behavior | Independence |\n| --- | --- | --- |\n| `int`, `float`, `bool`, `string` | Value (deep copy) | Fully independent |\n| `array`, `struct` | Value (deep copy) | Fully independent |\n| `slice` | Header copied, backing array shared | Use `slices.Clone` |\n| `map` | Reference copied | Use `maps.Clone` |\n| `channel` | Reference copied | Same channel |\n| `*T` (pointer) | Address copied | Same underlying value |\n| `interface` | Value copied (type + value pair) | Depends on held type |\n\n## Third-Party Libraries\n\nFor advanced data structures (trees, sets, queues, stacks) beyond the standard library:\n\n- **`emirpasic\u002Fgods`** — comprehensive collection library (trees, sets, lists, stacks, maps, queues)\n- **`deckarep\u002Fgolang-set`** — thread-safe and non-thread-safe set implementations\n- **`gammazero\u002Fdeque`** — fast double-ended queue\n\nWhen using third-party libraries, refer to their official documentation and code examples for current API signatures.\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) — prefer it over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-performance` skill for struct field alignment, memory layout optimization, and cache locality\n- → See `samber\u002Fcc-skills-golang@golang-safety` skill for nil map\u002Fslice pitfalls, append aliasing, defensive copying, `slices.Clone`\u002F`Equal`\n- → See `samber\u002Fcc-skills-golang@golang-concurrency` skill for channels, `sync.Map`, `sync.Pool`, and all sync primitives\n- → See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for `string` vs `[]byte` vs `[]rune`, iterators, streaming\n- → See `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill for struct composition, embedding, and generics vs `any`\n- → See `samber\u002Fcc-skills-golang@golang-code-style` skill for slice\u002Fmap initialization style\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Growing a slice in a loop without preallocation | Each growth copies the entire backing array — O(n) per growth. Use `make([]T, 0, n)` or `slices.Grow` |\n| Using `container\u002Flist` when a slice would suffice | Linked lists have poor cache locality (each node is a separate heap allocation). Benchmark first |\n| `bytes.Buffer` for pure string building | Buffer's `String()` copies the underlying bytes. `strings.Builder` avoids this copy |\n| `unsafe.Pointer` stored as `uintptr` across statements | GC can move the object between statements — the `uintptr` becomes a dangling reference |\n| Large struct values in maps (copying overhead) | Map access copies the entire value. Use `map[K]*V` for large value types to avoid the copy |\n\n## References\n\n- [Go Data Structures (Russ Cox)](https:\u002F\u002Fresearch.swtch.com\u002Fgodata)\n- [The Go Memory Model](https:\u002F\u002Fgo.dev\u002Fref\u002Fmem)\n- [Effective Go](https:\u002F\u002Fgo.dev\u002Fdoc\u002Feffective_go)\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":36,"compatibility":37,"user-invocable":38},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.2.2",{"emoji":30,"install":31,"homepage":32,"requires":33},"🗃",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":34},[35],"go","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__* mcp__context7__resolve-library-id mcp__context7__query-docs","Designed for Claude Code, Codex or similar harness, and for projects using Golang.",true,"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":38},[49,52,55],{"tool":50,"command":51},"npx","npx skills add kongnakornna\u002Fgolangapi --skill golang-data-structures",{"tool":53,"command":54},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill golang-data-structures",{"tool":56,"command":57},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill golang-data-structures","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002FSKILL.md",[60,66,70,74,78,82],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"evals\u002Fevals.json","REFERENCE","参考文档",20105,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002Fevals\u002Fevals.json",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcontainers.md",4088,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002Freferences\u002Fcontainers.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fgenerics.md",2571,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002Freferences\u002Fgenerics.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fmap-internals.md",2579,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002Freferences\u002Fmap-internals.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fpointers.md",4273,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002Freferences\u002Fpointers.md",{"path":83,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fslice-internals.md",1962,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-data-structures\u002Freferences\u002Fslice-internals.md",[87,95,102,109,116,123],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]