go-cms-api

What problem does it solve? It guides the design and implementation of public and admin HTTP APIs in the Go CMS backend so endpoints follow consistent route contracts, DTO mapping, validation, error handling, and authorization boundaries instead of ad-hoc handler logic. ## Core Features & Use Cases - CRUD and route conventions: Enforces resource-oriented endpoint patterns, common pagination/filtering/sorting vocabulary, and deterministic list ordering. - Transport boundary discipline: Keeps handlers as thin transport adapters with separate syntactic validation, domain validation, and authorization, plus typed error-to-status mapping. - Optional feature APIs: Prevents optional modules like Mail, Forms, Search, or Audit from leaking feature-specific imports into the generic kernel/app package. - Use Case: When adding a new management endpoint for the Forms module, use this Skill to wire it through a generic contribution contract, validate site context, and map domain errors to correct HTTP statuses. ## Quick Start Use the go-cms-api skill to design a new admin CRUD endpoint for the Forms module with proper validation, error mapping, and authorization wiring.