Apply Go development principles for maintainable, testable codebases.
npx skills add https://github.com/tinywasm/devflow --skill core-principles-tinywasm
Please help me install this Agent Skill. Skill: core-principles Source: https://github.com/tinywasm/devflow/tree/main/skills/core-principles Command: npx skills add https://github.com/tinywasm/devflow --skill core-principles-tinywasm
Go teams often struggle with tangled dependencies, bloated main packages, and inconsistent project structure. This Skill provides a principled blueprint to enforce SRP, DI, framework-less development, and strict file organization across Go projects.
Integrate these principles into your current Go project by auditing modules for SRP, DI interfaces, and minimal main packages.
High-intent search queries and answers about installing and using this skill.
Structure a Go project using clean architecture by enforcing Dependency Injection through interfaces for external dependencies, keeping main.go thin, and avoiding global state to improve code testability. Maintain a flat project structure with strict file organization.
The best way to build a framework-less Go web application is using the standard library directly. This approach minimizes external dependencies, ensures predictable structure across large codebases, and leverages native Go capabilities for web development.
The Single Responsibility Principle (SRP) in Go requires each file to have a single, well-defined purpose with naming reflecting its role. Strict file organization mandates a maximum of 500 lines per file to ensure maintainability.
In a framework-less Go application, you should implement UI interactivity using CSS-first whenever possible. JavaScript should only be used as a last resort to maintain minimal dependencies and predictable structure.
You should move Go tests to a dedicated tests/ directory when strict file organization and test management guidance require it. This helps maintain the 500-line file limit and keeps the flat project structure predictable.
Go codebases get tangled dependencies and bloated main packages when lacking strict architectural principles. Applying SRP, mandatory Dependency Injection, and keeping main.go minimal resolves these issues for better maintainability.
vlad-ryzhkovAudit Go backend repositories for API endpoints, infrastructure, and test coverage.
humanerd-drewExtract modules from Python files while managing name collisions and circular references.
hellopoisonxRecommend production-ready Go libraries while enforcing a standard-library-first rule.
matdev83Configure Go application dependencies with type-safe dependency injection.
