kernel-api-design
Installation
SKILL.md
Design the inbound server boundary so external requests enter the system through clear contracts, thin handlers, and explicit validation/auth rules.
Standards
Use the repo's actual framework and boundary primitives. Prefer the project's documented routing, schema, and middleware patterns over generic defaults.
This skill owns the inbound boundary:
- request parsing and validation
- route or action shape
- middleware ordering
- auth/authz at the boundary
- response envelope consistency
- handoff from transport layer to service layer
It does not own end-to-end subsystem tracing (kernel-trace), auth system design (kernel-better-auth), test strategy (kernel-testing), or general type-system rules (kernel-typescript).