[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWQ91AMYGRK8SXQBFATAD5":3,"skill-same:01M7CWQ91AMYGRK8SXQBFATAD5":58},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M7CWQ91AMYGRK8SXQBFATAD5","golang-project-layout",null,"Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd\u002Finternal\u002Fpkg directory conventions, or discussing package restructuring, package splits, or module splits.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills-golang\u002Fgolang-project-layout\u002Fskills\u002Fgolang-project-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-project-layout\ndescription: \"Provides a guide for setting up Golang project layouts and workspaces. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, deciding between cmd\u002Finternal\u002Fpkg directory conventions, or discussing package restructuring, package splits, or module splits.\"\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.2.1\"\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 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-lint` 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-lint` 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. → See `samber\u002Fcc-skills-golang@golang-refactoring` skill for safely moving or splitting existing code into the layout above via type-alias gradual code repair and staged PRs, without a big-bang break.\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-lint` 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-lint` 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. → See `samber\u002Fcc-skills-golang@golang-refactoring` skill for safely moving or splitting existing code into the layout above via type-alias gradual code repair and staged PRs, without a big-bang break.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":34,"compatibility":35,"user-invocable":36},{"author":25,"version":26,"openclaw":27},"samber","1.2.1",{"emoji":28,"install":29,"homepage":30,"requires":31},"📁",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":32},[33],"go","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,"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fsamber-cc-skills-golang\u002Fgolang-project-layout\u002Fskills\u002Fgolang-project-layout",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":36},[47,50,53],{"tool":48,"command":49},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill golang-project-layout",{"tool":51,"command":52},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill golang-project-layout",{"tool":54,"command":55},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill golang-project-layout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills-golang\u002Fgolang-project-layout\u002Fskills\u002Fgolang-project-layout\u002FSKILL.md",[],[59,66,71,78,83,90],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":67,"name":61,"nameZh":6,"description":62,"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},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\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},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":79,"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":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":91,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]