Silvio Ubaldino de Sousa Neto avatar

Silvio Ubaldino de Sousa Neto

Community

@silvioubaldino

3Followers
|
30Public Repos
|
4Published Skills

Go clean-architecture development skills covering dependency injection, Gin HTTP handlers, usecase business logic, and table-driven unit testing conventions.

Skills Distribution
DomainDeveloper To...Go Backend Develop.. (40%)Clean Architecture.. (25%)HTTP API Design (20%)Unit Testing & Tes.. (15%)

Agent Skills by Silvio Ubaldino de Sousa Neto

Showing 4 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Silvio Ubaldino de Sousa Neto

FAQPage Schema
What tasks can I accomplish with silvioubaldino's Go skills?▼

You can wire new clean-architecture features with DI and route registration, write Gin HTTP handlers with error wrapping, implement usecase business logic with transaction boundaries and interface-at-point-of-use, and create table-driven Go unit tests using testify and testify/mock.

Who are these Go clean-architecture skills designed for?▼

Backend engineers working in a Go clean-architecture codebase with internal/bootstrap, internal/usecase, and internal/infrastructure/api layers. They suit developers adding endpoints, usecases, repository interfaces, or test coverage while enforcing established project conventions.

How do the skills enforce testing conventions?▼

The go-unit-tests skill governs creation and editing of *_test.go files, enforcing table-driven test structure, the AAA (Arrange-Act-Assert) pattern, and testify with testify/mock for mocking dependencies across usecases, repositories, services, and handlers.

What prerequisites does the codebase need to use these skills?▼

A Go project following clean architecture with internal/bootstrap/registry, cmd/api/main.go, internal/usecase, and internal/infrastructure/api directories. The stack assumes Gin for HTTP routing, Firebase auth or internal API keys, and testify for testing.

How is authentication handled for new API routes?▼

The go-bootstrap skill guides route registration decisions, helping you determine whether new routes require Firebase authentication, an internal API key, or no authentication, based on the feature being wired into the application.