API Steer

What problem does it solve?

API Steer clarifies how scenario endpoints are organized, typed, and governed so that downstream engineers and CLIs can rely on predictable, durable contracts instead of brittle, ad-hoc interfaces.

Core Features & Use Cases

• Domain-aligned organization: Group routers and handlers by bounded contexts, keep cross-cutting concerns in dedicated modules, and avoid giant misc files so new contributors can infer capabilities at a glance.
• Consistency conventions: Standardize errors, pagination, filtering, sorting, idempotency, authentication, and observability hooks so each endpoint fails, logs, and scales in familiar ways.
• Proto-first contracts & documentation: Treat proto schemas as the canonical contract, document CLI/API mappings, and consult interoperability-steer for canonical proto governance while planning additive change strategies.
• Use Case: When reshaping a brownfield API, audit the existing surface, note the top inconsistencies, and reorganize modules while keeping handlers thin and domain logic in services.

Quick Start

Ask the API Steer skill to audit your scenario API surface for domain-aligned modules, consistent contracts, and CLI mappings.