[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JGRHCBDSVV20M5N8JH9WB6":3,"skill-same:01M6JGRHCBDSVV20M5N8JH9WB6":111},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":69},"01M6JGRHCBDSVV20M5N8JH9WB6","golang-project-layout",null,"Provides a guide for setting up Golang project layouts and workspaces. Use this whenever starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, or deciding on directory structure. Apply this for any Go project initialization or restructuring work.","muratovv\u002Fai-hats","muratovv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7502801?v=4","01M6JGCBN4KEJX012GPJVSH04T","Fedor Muratov","01M6JGCBSNMN7CW3RGTPPE0MN2",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"layout","project","golang","golang project layout","read","initialization","structure","main","workspaces","up","write","directory","work","monorepo","projects","Bash","code","packages","ai coding agents","cli","2026-11-10 10:12:30",false,"---\nname: golang-project-layout\ndescription: >-\n  Provides a guide for setting up Golang project layouts and workspaces.\n  Use this whenever starting a new Go project, organizing an existing\n  codebase, setting up a monorepo with multiple packages, creating CLI\n  tools with multiple main packages, or deciding on directory structure.\n  Apply this for any Go project initialization or restructuring work.\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.1.3\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent AskUserQuestion\n---\n\n**Persona:** You are a Go project architect. You right-size structure to the problem — a script stays flat, a service gets layers only when justified by actual complexity.\n\n# Go Project Layout\n\n## Architecture Decision: Ask First\n\nWhen starting a new project, **ask the developer** what software architecture they prefer (clean architecture, hexagonal, DDD, flat structure, etc.). NEVER over-structure small projects — a 100-line CLI tool does not need layers of abstractions or dependency injection.\n\n→ See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for detailed architecture guides with file trees and code examples.\n\n## Dependency Injection: Ask Next\n\nAfter settling on the architecture, **ask the developer** which dependency injection approach they want: manual constructor injection, or a DI library (samber\u002Fdo, google\u002Fwire, uber-go\u002Fdig+fx), or none at all. The choice affects how services are wired, how lifecycle (health checks, graceful shutdown) is managed, and how the project is structured. See the `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for a full comparison and decision table.\n\n## 12-Factor App\n\nFor applications (services, APIs, workers), follow [12-Factor App](https:\u002F\u002F12factor.net\u002F) conventions: config via environment variables, logs to stdout, stateless processes, graceful shutdown, backing services as attached resources, and admin tasks as one-off commands (e.g., `cmd\u002Fmigrate\u002F`).\n\n## Quick Start: Choose Your Project Type\n\n| Project Type | Use When | Key Directories |\n| --- | --- | --- |\n| **CLI Tool** | Building a command-line application | `cmd\u002F{name}\u002F`, `internal\u002F`, optional `pkg\u002F` |\n| **Library** | Creating reusable code for others | `pkg\u002F{name}\u002F`, `internal\u002F` for private code |\n| **Service** | HTTP API, microservice, or web app | `cmd\u002F{service}\u002F`, `internal\u002F`, `api\u002F`, `web\u002F` |\n| **Monorepo** | Multiple related packages\u002Fmodules | `go.work`, separate modules per package |\n| **Workspace** | Developing multiple local modules | `go.work`, replace directives |\n\n## Module Naming Conventions\n\n### Module Name (go.mod)\n\nYour module path in `go.mod` should:\n\n- **MUST match your repository URL**: `github.com\u002Fusername\u002Fproject-name`\n- **Use lowercase only**: `github.com\u002Fyou\u002Fmy-app` (not `MyApp`)\n- **Use hyphens for multi-word**: `user-auth` not `user_auth` or `userAuth`\n- **Be semantic**: Name should clearly express purpose\n\n**Examples:**\n\n```go\n\u002F\u002F ✅ Good\nmodule github.com\u002Fjdoe\u002Fpayment-processor\nmodule github.com\u002Fcompany\u002Fcli-tool\n\n\u002F\u002F ❌ Bad\nmodule myproject\nmodule github.com\u002Fjdoe\u002FMyProject\nmodule utils\n```\n\n### Package Naming\n\nPackages MUST be lowercase, singular, and match their directory name. → See `samber\u002Fcc-skills-golang@golang-naming` skill for complete package naming conventions and examples.\n\n## Directory Layout\n\nAll `main` packages must reside in `cmd\u002F` with minimal logic — parse flags, wire dependencies, call `Run()`. Business logic belongs in `internal\u002F` or `pkg\u002F`. Use `internal\u002F` for non-exported packages, `pkg\u002F` only when code is useful to external consumers.\n\nSee [directory layout examples](references\u002Fdirectory-layouts.md) for universal, small project, and library layouts, plus common mistakes.\n\n## Essential Configuration Files\n\nEvery Go project should include at the root:\n\n- **Makefile** — build automation. See [Makefile template](assets\u002FMakefile)\n- **.gitignore** — git ignore patterns. See [.gitignore template](assets\u002F.gitignore)\n- **.golangci.yml** — linter config. See the `samber\u002Fcc-skills-golang@golang-linter` skill for the recommended configuration\n\nFor application configuration with Cobra + Viper, see [config reference](references\u002Fconfig.md).\n\n## Tests, Benchmarks, and Examples\n\nCo-locate `_test.go` files with the code they test. Use `testdata\u002F` for fixtures. See [testing layout](references\u002Ftesting-layout.md) for file naming, placement, and organization details.\n\n## Go Workspaces\n\nUse `go.work` when developing multiple related modules in a monorepo. See [workspaces](references\u002Fworkspaces.md) for setup, structure, and commands.\n\n## Initialization Checklist\n\nWhen starting a new Go project:\n\n- [ ] **Ask the developer** their preferred software architecture (clean, hexagonal, DDD, flat, etc.)\n- [ ] **Ask the developer** their preferred DI approach — see `samber\u002Fcc-skills-golang@golang-dependency-injection` skill\n- [ ] Decide project type (CLI, library, service, monorepo)\n- [ ] Right-size the structure to the project scope\n- [ ] Choose module name (matches repo URL, lowercase, hyphens)\n- [ ] Run `go version` to detect the current go version\n- [ ] Run `go mod init github.com\u002Fuser\u002Fproject-name`\n- [ ] Create `cmd\u002F{name}\u002Fmain.go` for entry point\n- [ ] Create `internal\u002F` for private code\n- [ ] Create `pkg\u002F` only if you have public libraries\n- [ ] For monorepos: Initialize `go work` and add modules\n- [ ] Run `gofmt -s -w .` to ensure formatting\n- [ ] Add `.gitignore` with `\u002Fvendor\u002F` and binary patterns\n\n## Related Skills\n\n→ See `samber\u002Fcc-skills-golang@golang-cli` skill for CLI tool structure and Cobra\u002FViper patterns. → See `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for DI approach comparison and wiring. → See `samber\u002Fcc-skills-golang@golang-linter` skill for golangci-lint configuration. → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for CI\u002FCD pipeline setup. → See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for architectural patterns.\n","**Persona:** You are a Go project architect. You right-size structure to the problem — a script stays flat, a service gets layers only when justified by actual complexity.\n\n# Go Project Layout\n\n## Architecture Decision: Ask First\n\nWhen starting a new project, **ask the developer** what software architecture they prefer (clean architecture, hexagonal, DDD, flat structure, etc.). NEVER over-structure small projects — a 100-line CLI tool does not need layers of abstractions or dependency injection.\n\n→ See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for detailed architecture guides with file trees and code examples.\n\n## Dependency Injection: Ask Next\n\nAfter settling on the architecture, **ask the developer** which dependency injection approach they want: manual constructor injection, or a DI library (samber\u002Fdo, google\u002Fwire, uber-go\u002Fdig+fx), or none at all. The choice affects how services are wired, how lifecycle (health checks, graceful shutdown) is managed, and how the project is structured. See the `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for a full comparison and decision table.\n\n## 12-Factor App\n\nFor applications (services, APIs, workers), follow [12-Factor App](https:\u002F\u002F12factor.net\u002F) conventions: config via environment variables, logs to stdout, stateless processes, graceful shutdown, backing services as attached resources, and admin tasks as one-off commands (e.g., `cmd\u002Fmigrate\u002F`).\n\n## Quick Start: Choose Your Project Type\n\n| Project Type | Use When | Key Directories |\n| --- | --- | --- |\n| **CLI Tool** | Building a command-line application | `cmd\u002F{name}\u002F`, `internal\u002F`, optional `pkg\u002F` |\n| **Library** | Creating reusable code for others | `pkg\u002F{name}\u002F`, `internal\u002F` for private code |\n| **Service** | HTTP API, microservice, or web app | `cmd\u002F{service}\u002F`, `internal\u002F`, `api\u002F`, `web\u002F` |\n| **Monorepo** | Multiple related packages\u002Fmodules | `go.work`, separate modules per package |\n| **Workspace** | Developing multiple local modules | `go.work`, replace directives |\n\n## Module Naming Conventions\n\n### Module Name (go.mod)\n\nYour module path in `go.mod` should:\n\n- **MUST match your repository URL**: `github.com\u002Fusername\u002Fproject-name`\n- **Use lowercase only**: `github.com\u002Fyou\u002Fmy-app` (not `MyApp`)\n- **Use hyphens for multi-word**: `user-auth` not `user_auth` or `userAuth`\n- **Be semantic**: Name should clearly express purpose\n\n**Examples:**\n\n```go\n\u002F\u002F ✅ Good\nmodule github.com\u002Fjdoe\u002Fpayment-processor\nmodule github.com\u002Fcompany\u002Fcli-tool\n\n\u002F\u002F ❌ Bad\nmodule myproject\nmodule github.com\u002Fjdoe\u002FMyProject\nmodule utils\n```\n\n### Package Naming\n\nPackages MUST be lowercase, singular, and match their directory name. → See `samber\u002Fcc-skills-golang@golang-naming` skill for complete package naming conventions and examples.\n\n## Directory Layout\n\nAll `main` packages must reside in `cmd\u002F` with minimal logic — parse flags, wire dependencies, call `Run()`. Business logic belongs in `internal\u002F` or `pkg\u002F`. Use `internal\u002F` for non-exported packages, `pkg\u002F` only when code is useful to external consumers.\n\nSee [directory layout examples](references\u002Fdirectory-layouts.md) for universal, small project, and library layouts, plus common mistakes.\n\n## Essential Configuration Files\n\nEvery Go project should include at the root:\n\n- **Makefile** — build automation. See [Makefile template](assets\u002FMakefile)\n- **.gitignore** — git ignore patterns. See [.gitignore template](assets\u002F.gitignore)\n- **.golangci.yml** — linter config. See the `samber\u002Fcc-skills-golang@golang-linter` skill for the recommended configuration\n\nFor application configuration with Cobra + Viper, see [config reference](references\u002Fconfig.md).\n\n## Tests, Benchmarks, and Examples\n\nCo-locate `_test.go` files with the code they test. Use `testdata\u002F` for fixtures. See [testing layout](references\u002Ftesting-layout.md) for file naming, placement, and organization details.\n\n## Go Workspaces\n\nUse `go.work` when developing multiple related modules in a monorepo. See [workspaces](references\u002Fworkspaces.md) for setup, structure, and commands.\n\n## Initialization Checklist\n\nWhen starting a new Go project:\n\n- [ ] **Ask the developer** their preferred software architecture (clean, hexagonal, DDD, flat, etc.)\n- [ ] **Ask the developer** their preferred DI approach — see `samber\u002Fcc-skills-golang@golang-dependency-injection` skill\n- [ ] Decide project type (CLI, library, service, monorepo)\n- [ ] Right-size the structure to the project scope\n- [ ] Choose module name (matches repo URL, lowercase, hyphens)\n- [ ] Run `go version` to detect the current go version\n- [ ] Run `go mod init github.com\u002Fuser\u002Fproject-name`\n- [ ] Create `cmd\u002F{name}\u002Fmain.go` for entry point\n- [ ] Create `internal\u002F` for private code\n- [ ] Create `pkg\u002F` only if you have public libraries\n- [ ] For monorepos: Initialize `go work` and add modules\n- [ ] Run `gofmt -s -w .` to ensure formatting\n- [ ] Add `.gitignore` with `\u002Fvendor\u002F` and binary patterns\n\n## Related Skills\n\n→ See `samber\u002Fcc-skills-golang@golang-cli` skill for CLI tool structure and Cobra\u002FViper patterns. → See `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for DI approach comparison and wiring. → See `samber\u002Fcc-skills-golang@golang-linter` skill for golangci-lint configuration. → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for CI\u002FCD pipeline setup. → See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for architectural patterns.\n",{"name":5,"license":15,"metadata":44,"description":7,"allowed-tools":47,"compatibility":48,"user-invocable":49},{"author":45,"version":46},"samber","1.1.3","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent AskUserQuestion","Designed for Claude Code or similar AI coding agents, and for projects using Golang.",true,"master","b4819add93efbaf4d80627118ec34680406b309b","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout",1,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats","https:\u002F\u002Fgithub.com\u002Fmuratovv","2026-11-05 20:59:10",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":49},[59,62,65],{"tool":60,"command":61},"npx","npx skills add muratovv\u002Fai-hats --skill golang-project-layout",{"tool":63,"command":64},"bunx","bunx skills add muratovv\u002Fai-hats --skill golang-project-layout",{"tool":66,"command":67},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill golang-project-layout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002FSKILL.md",[70,76,80,86,91,95,99,103,107],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002F.gitignore","ASSET","资产文件",421,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Fassets\u002F.gitignore",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002FMakefile",2539,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Fassets\u002FMakefile",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fevals.json","REFERENCE","参考文档",12008,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Fevals\u002Fevals.json",{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"LICENSE","许可证",1070,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002FLICENSE",{"path":92,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":93,"sourceHtmlUrl":94},"metadata.yaml",651,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Fmetadata.yaml",{"path":96,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fconfig.md",1444,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Freferences\u002Fconfig.md",{"path":100,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fdirectory-layouts.md",4678,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Freferences\u002Fdirectory-layouts.md",{"path":104,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Ftesting-layout.md",5227,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Freferences\u002Ftesting-layout.md",{"path":108,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkspaces.md",2544,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-project-layout\u002Freferences\u002Fworkspaces.md",[112,137,162,185,209,222],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":39},"01M6PVFB1SM738R2SRSRSF7CY6","tool-evaluation-protocol","Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML\u002FLLM frameworks, testing approaches), or following up on a hype-driven recommendation.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Ftool-evaluation-protocol\u002FSKILL.md",[],[119,120,121,122,123,124,125,126,127,128,129,130,28,131,132,20,133,134,135,136],"protocol","Evaluation","tool","tool evaluation protocol","testing","ml","libraries","adoption","methodology","Tools","use","dependency","frameworks","time","recommendation","for","bounded","candidate",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":39},"01M6PVF7HATBEX1G7N50E2QT57","systematic-debugging","4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[144,145,146,147,119,148,149,150,151,152,129,153,154,155,156,157,158,159,160,161],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","error","with","bug-fix","phase",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":173,"publishedAt":39},"01M6PVF3MTQN3RPF73AN34856J","skill-template","Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-template\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[174,175,176,177,178,151,179,129,180,156,181,182,183,134,184],"template","skill template","validation","compliance","hats","guide","new skill","structural","canonical","which","Existing",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":39},"01M6PVF06SCV28QARM5MQPANC9","skill-optimization","Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-optimization\u002FSKILL.md",[191],{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},[193,194,195,196,197,198,199,200,201,202,129,203,204,205,206,207,208],"Optimization","skill optimization","components","component","issues","library","audit","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":39},"01M6PVEXM9717016T9MW82HDCT","silent-fallback-gate","PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsilent-fallback-gate\u002FSKILL.md",[],[216,217,218,219,29,220,129,221,134],"gate","fallback","silent fallback gate","python","edit","hook",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":39},"01M6PVESM49C5NT7SB7N3F76VS","retro-to-framework","Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fretro-to-framework\u002FSKILL.md",[228],{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},[230,231,232,233,196,234,33,235,202,151,129,236,237,20,238,239,240,241,242,243],"framework","retro","retro to framework","change","retrospective","convert","incident","across","problem","about","more","skill update","single","generic"]