Brokle Error Handling FAQs

Question 1

What does the Brokle Error Handling skill do?

Accepted Answer

This skill enables Claude to implement, review, and debug a standardized 'industrial' error handling flow in Go. It enforces a three-layer pattern where errors move from Repository (Domain Errors) to Service (AppErrors) and finally to Handlers (HTTP Responses).

Question 2

When should I use this Claude Code skill?

Accepted Answer

Use this skill whenever you are working on the Brokle codebase or similar Go projects requiring strict clean architecture. It is ideal for implementing database error wrapping, service-layer business logic errors, and automated HTTP status mapping.

Question 3

How does this skill improve my Go development workflow?

Accepted Answer

It automates the creation of consistent, professional error patterns. By mandating domain alias imports and standardized GORM error checking, it reduces boilerplate, prevents logging bloat in core services, and ensures your API responses remain uniform.

Question 4

What are the mandatory domain alias patterns?

Accepted Answer

The skill enforces professional aliasing for Go imports to prevent naming collisions. For example, instead of direct imports, it mandates aliases like 'authDomain' for 'brokle/internal/core/domain/auth' and 'userDomain' for user-related domain logic.

Question 5

Does it support automated HTTP status code mapping?

Accepted Answer

Yes. The skill ensures that the handler layer uses centralized response helpers. This automatically maps specific AppError types—such as ValidationError, ConflictError, or NotFoundError—to their corresponding HTTP status codes (400, 409, 404, etc.) without manual intervention.

Brokle Error Handling

Brokle Error Handling

Key Features

Use Cases

Key Features

Use Cases