[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ZX1ZJMGR2SD6AMBDZF5K0":3,"skill-same:01M79ZX1ZJMGR2SD6AMBDZF5K0":56},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79ZX1ZJMGR2SD6AMBDZF5K0","go-functions",null,"Use when organizing functions within a Go file, formatting function signatures, designing return values, or following Printf-style naming conventions. Also use when a user is adding or refactoring any Go function, even if they don't mention function design or signature formatting. Does not cover functional options constructors (see go-functional-options).","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-functions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: go-functions\ndescription: Use when organizing functions within a Go file, formatting function signatures, designing return values, or following Printf-style naming conventions. Also use when a user is adding or refactoring any Go function, even if they don't mention function design or signature formatting. Does not cover functional options constructors (see go-functional-options).\n---\n\n# Go Function Design\n\n## Resource Routing\n\n- `references\u002FSIGNATURES.md` - Read when designing parameters, return values, named results, or signature readability.\n- `references\u002FPRINTF-STRINGER.md` - Read when using fmt verbs, Stringer, GoStringer, Formatter, or Printf-style function naming.\n\n> **When this skill does NOT apply**: For functional options constructors (`WithTimeout`, `WithLogger`), see [go-functional-options](..\u002Fgo-functional-options\u002FSKILL.md). For error return conventions, see [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md). For naming functions and methods, see [go-naming](..\u002Fgo-naming\u002FSKILL.md).\n\n---\n\n## Function Grouping and Ordering\n\nOrganize functions in a file by these rules:\n\n1. Functions sorted in **rough call order**\n2. Functions **grouped by receiver**\n3. **Exported** functions appear first, after `struct`\u002F`const`\u002F`var` definitions\n4. `NewXxx`\u002F`newXxx` constructors appear right after the type definition\n5. Plain utility functions appear toward the end of the file\n\n```go\ntype something struct{ ... }\n\nfunc newSomething() *something { return &something{} }\n\nfunc (s *something) Cost() int { return calcCost(s.weights) }\n\nfunc (s *something) Stop() { ... }\n\nfunc calcCost(n []int) int { ... }\n```\n\n---\n\n## Function Signatures\n\nKeep the signature on a single line when possible. When it must wrap, put **all\narguments on their own lines** with a trailing comma:\n\n```go\nfunc (r *SomeType) SomeLongFunctionName(\n    foo1, foo2, foo3 string,\n    foo4, foo5, foo6 int,\n) {\n    foo7 := bar(foo1)\n}\n```\n\nAdd `\u002F* name *\u002F` comments for ambiguous arguments, or better yet, replace naked\n`bool` parameters with custom types.\n\n---\n\n## Pointers to Interfaces\n\nYou almost never need a pointer to an interface. Pass interfaces as values — the\nunderlying data can still be a pointer.\n\n```go\n\u002F\u002F Bad: pointer to interface\nfunc process(r *io.Reader) { ... }\n\n\u002F\u002F Good: pass the interface value\nfunc process(r io.Reader) { ... }\n```\n\n---\n\n## Printf and Stringer\n\n### Printf-style Function Names\n\nFunctions that accept a format string should end in `f` for `go vet` support.\nDeclare format strings as `const` when used outside `Printf` calls.\n\nPrefer `%q` over `%s` with manual quoting when formatting strings for logging\nor error messages — it safely escapes special characters and wraps in quotes:\n\n```go\nreturn fmt.Errorf(\"unknown key %q\", key) \u002F\u002F produces: unknown key \"foo\\nbar\"\n```\n\nSee **go-functional-options** when designing a constructor with 3+ optional\nparameters.\n\n---\n\n## Quick Reference\n\n| Topic | Rule |\n|-------|------|\n| File ordering | Type -> constructor -> exported -> unexported -> utils |\n| Signature wrapping | All args on own lines with trailing comma |\n| Naked parameters | Add `\u002F* name *\u002F` comments or use custom types |\n| Pointers to interfaces | Almost never needed; pass interfaces by value |\n| Printf function names | End with `f` for `go vet` support |\n\n---\n\n## Related Skills\n\n- **Error returns**: See [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md) when designing error return patterns or wrapping errors in multi-return functions\n- **Naming conventions**: See [go-naming](..\u002Fgo-naming\u002FSKILL.md) when naming functions, methods, or choosing getter\u002Fsetter patterns\n- **Functional options**: See [go-functional-options](..\u002Fgo-functional-options\u002FSKILL.md) when designing a constructor with 3+ optional parameters\n- **Formatting principles**: See [go-style-core](..\u002Fgo-style-core\u002FSKILL.md) when deciding line length, naked returns, or signature formatting\n","# Go Function Design\n\n## Resource Routing\n\n- `references\u002FSIGNATURES.md` - Read when designing parameters, return values, named results, or signature readability.\n- `references\u002FPRINTF-STRINGER.md` - Read when using fmt verbs, Stringer, GoStringer, Formatter, or Printf-style function naming.\n\n> **When this skill does NOT apply**: For functional options constructors (`WithTimeout`, `WithLogger`), see [go-functional-options](..\u002Fgo-functional-options\u002FSKILL.md). For error return conventions, see [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md). For naming functions and methods, see [go-naming](..\u002Fgo-naming\u002FSKILL.md).\n\n---\n\n## Function Grouping and Ordering\n\nOrganize functions in a file by these rules:\n\n1. Functions sorted in **rough call order**\n2. Functions **grouped by receiver**\n3. **Exported** functions appear first, after `struct`\u002F`const`\u002F`var` definitions\n4. `NewXxx`\u002F`newXxx` constructors appear right after the type definition\n5. Plain utility functions appear toward the end of the file\n\n```go\ntype something struct{ ... }\n\nfunc newSomething() *something { return &something{} }\n\nfunc (s *something) Cost() int { return calcCost(s.weights) }\n\nfunc (s *something) Stop() { ... }\n\nfunc calcCost(n []int) int { ... }\n```\n\n---\n\n## Function Signatures\n\nKeep the signature on a single line when possible. When it must wrap, put **all\narguments on their own lines** with a trailing comma:\n\n```go\nfunc (r *SomeType) SomeLongFunctionName(\n    foo1, foo2, foo3 string,\n    foo4, foo5, foo6 int,\n) {\n    foo7 := bar(foo1)\n}\n```\n\nAdd `\u002F* name *\u002F` comments for ambiguous arguments, or better yet, replace naked\n`bool` parameters with custom types.\n\n---\n\n## Pointers to Interfaces\n\nYou almost never need a pointer to an interface. Pass interfaces as values — the\nunderlying data can still be a pointer.\n\n```go\n\u002F\u002F Bad: pointer to interface\nfunc process(r *io.Reader) { ... }\n\n\u002F\u002F Good: pass the interface value\nfunc process(r io.Reader) { ... }\n```\n\n---\n\n## Printf and Stringer\n\n### Printf-style Function Names\n\nFunctions that accept a format string should end in `f` for `go vet` support.\nDeclare format strings as `const` when used outside `Printf` calls.\n\nPrefer `%q` over `%s` with manual quoting when formatting strings for logging\nor error messages — it safely escapes special characters and wraps in quotes:\n\n```go\nreturn fmt.Errorf(\"unknown key %q\", key) \u002F\u002F produces: unknown key \"foo\\nbar\"\n```\n\nSee **go-functional-options** when designing a constructor with 3+ optional\nparameters.\n\n---\n\n## Quick Reference\n\n| Topic | Rule |\n|-------|------|\n| File ordering | Type -> constructor -> exported -> unexported -> utils |\n| Signature wrapping | All args on own lines with trailing comma |\n| Naked parameters | Add `\u002F* name *\u002F` comments or use custom types |\n| Pointers to interfaces | Almost never needed; pass interfaces by value |\n| Printf function names | End with `f` for `go vet` support |\n\n---\n\n## Related Skills\n\n- **Error returns**: See [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md) when designing error return patterns or wrapping errors in multi-return functions\n- **Naming conventions**: See [go-naming](..\u002Fgo-naming\u002FSKILL.md) when naming functions, methods, or choosing getter\u002Fsetter patterns\n- **Functional options**: See [go-functional-options](..\u002Fgo-functional-options\u002FSKILL.md) when designing a constructor with 3+ optional parameters\n- **Formatting principles**: See [go-style-core](..\u002Fgo-style-core\u002FSKILL.md) when deciding line length, naked returns, or signature formatting\n",{"name":5,"description":7},"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-functions","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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kongnakornna\u002Fgolangapi --skill go-functions",{"tool":38,"command":39},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill go-functions",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill go-functions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-functions\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002FPRINTF-STRINGER.md","REFERENCE","参考文档",7856,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-functions\u002Freferences\u002FPRINTF-STRINGER.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002FSIGNATURES.md",3971,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-functions\u002Freferences\u002FSIGNATURES.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]