Go Backend Clean Architecture
CheckedHelps with Go, backend development as part of developing backend services and APIs workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add rebyteai-template/rebyte-skills --skill go-backend-clean-architecture -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
eng0ai
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned eng0ai/eng0-template-skills at 0062e44684.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0062e44684
- Scanned
- 1 file, 56 lines
About this skill
What it does
This skill enables Go backend agents to generate code strictly adhering to Clean Architecture principles, ensuring high maintainability and separation of concerns. It structures applications into distinct layers—domain, application, interface, and infrastructure—to decouple business logic from external frameworks and databases.
When to use it
- Building new enterprise-grade Go services requiring long-term scalability.
- Refactoring legacy monolithic codebases into modular, testable components.
- Creating projects where business rules must remain independent of database or UI implementations.
- Developing systems that need rigorous unit testing without external dependencies.
Key capabilities
- Enforces strict dependency direction: inner layers (domain) have no knowledge of outer layers (infrastructure).
- Generates repository interfaces in the domain layer, deferring concrete implementation to the infrastructure layer.
- Structures entities and use cases to isolate core business logic from framework-specific concerns like HTTP or SQL.
- Organizes project directories to reflect architectural boundaries rather than technical file types.
Example prompts
- "Generate a Go user service using Clean Architecture with a domain entity, use case, and repository interface."
- "Refactor this existing Go handler to move business logic into the application layer while keeping the domain pure."
- "Create a new module for order processing that strictly follows Clean Architecture separation of concerns."
Tips & gotchas
Ensure your agent understands that interfaces defined in inner layers must be implemented by outer layers; reversing this breaks the architecture. This approach increases initial setup complexity compared to standard MVC patterns, so it is best suited for projects prioritizing long-term structural integrity over rapid prototyping.