Brokle API Routes FAQs

Question 1

What does the Brokle API Routes skill do?

Accepted Answer

This skill provides expert guidance for implementing and managing standardized API architectures. It focuses on the 'dual-route' pattern, separating programmatic SDK access from administrative dashboard access, while automating request validation and documentation.

Question 2

How does this skill improve my development workflow?

Accepted Answer

It eliminates guesswork by providing boilerplate-ready handler patterns, consistent error mapping (from application logic to HTTP statuses), and predefined pagination structures, allowing you to focus on business logic rather than boilerplate plumbing.

Question 3

When should I use this skill in Claude Code?

Accepted Answer

You should use this skill whenever you are creating, modifying, or reviewing API endpoints in a Go/Gin project. It is particularly useful for establishing URL structures, defining request/response models, and setting up middleware for authentication.

Question 4

How does this skill handle API security and authentication?

Accepted Answer

It implements two distinct security patterns: SDK routes (/v1/*) utilize long-lived API keys for programmatic integrations, while Dashboard routes (/api/v1/*) use Bearer JWT tokens for secure web-based administrative access.

Question 5

Does this skill help with API documentation?

Accepted Answer

Yes. It provides standardized Go-Swagger/OpenAPI comment patterns for every handler. This ensures that your API documentation is automatically generated and stays in sync with your actual code implementation.

Brokle API Routes

Brokle API Routes

Key Features

Use Cases

Key Features

Use Cases