Organize Go command entrypoints under cmd/ with thin main.go files.
npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill cmd-builder
Please help me install this Agent Skill. Skill: cmd-builder Source: https://github.com/sjtw/tarkov-build-optimiser/tree/main/.cursor/skills/cmd-builder Command: npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill cmd-builder
This Skill helps Go developers organize and wire command-line entrypoints under the cmd/ directory, ensuring consistent layout and clean separation of concerns.
Create a new directory cmd/<name>/ with main.go and wire it to internal packages, keeping business logic in internal/ and the cmd minimal.
High-intent search queries and answers about installing and using this skill.
A Go CLI project structures multiple executables by placing one entrypoint per directory under cmd/<name>/main.go. This enforces a consistent layout where each subdirectory represents a distinct binary, keeping project organization predictable and clean.
Business logic should not go in main.go when building a Go CLI. The cmd directory must remain thin, handling only flags and environment setup, while delegating core behavior and wiring to internal packages for clean separation of concerns.
The standard cmd directory layout for Go applications enforces one entrypoint per subdirectory, named cmd/<name>/main.go. It handles wiring and environment setup exclusively, directing all business logic to the internal/ package directory to maintain thin executables.
Refactoring an existing Go CLI to use the cmd and internal pattern involves moving business logic to internal packages and keeping only flag parsing and environment setup in cmd/<name>/main.go. This ensures the entrypoint stays thin and wiring is cleanly delegated.
You need to create a new cmd entrypoint in a Go project when adding a separate executable binary. Create a new directory cmd/<name>/ with a main.go file, wire it to existing internal packages, and ensure it only handles flags and environment setup without duplicating logic.
You should not place multiple main.go files in a single cmd directory in Go. The pattern enforces one entrypoint per directory under cmd/<name>/ to maintain a predictable project structure and prevent conflicting binary definitions within the same package.
333-333-333Create a Go microservice scaffold with a standard directory structure.
SuperlendExplain and analyze DWARF debug information in compiled binaries.
haipham22Organize Go project directories and workspaces by project type and module boundaries.
samberIdentify and apply optimal Go project layouts for single-module and monorepo structures.
