🚀 The fastest way to build CRUD APIs in TypeScript. Works with your favorite JavaScript framework and ORM, featuring filtering, sorting, pagination, and OpenAPI support.
Skill Claude Code
When and how to write a new ADR in docs/internals/adr/ — numbering, required sections, and how it must connect to code and the architecture docs. Use when a change makes a load-bearing decision (a seam, an invariant, a boundary rule) rather than just implementing one already on record.
Skill Claude Code
How to add a new key to KavoSettings — schema, default, merge semantics, validation, and docs — through the one layered precedence chain (global → entity → operation → per-call). Use when a change needs a new configurable behavior rather than a hardcoded constant.
Skill Claude Code
How to add a new Kavo exception — hierarchy placement, error-code catalog entry, problem-details wiring, and adapter error mapping. Use when a change needs to signal a new failure mode to callers rather than reusing an existing exception.
Skill Claude Code
The end-to-end procedure for adding, overriding, or disabling a Kavo operation — registry entry, DTO slots, handler, route metadata, and tests. Use when a change introduces a new CRUD operation or a custom per-entity operation.
Skill Claude Code
The canonical type: scheme shared by issue labels, branch names, and commit message prefixes. Use when labeling an issue, naming a branch, or writing a commit message.
Skill Claude Code
How to write tests for the Kavo monorepo — file placement, Vitest/SWC setup, fixtures, and the cases every change must pin down. Use when adding or updating tests in packages/core, packages/orms/typeorm, or packages/frameworks/nest.
Skill Claude Code
Use when writing a new page under docs/ or editing an existing one — new feature/guide/reference pages, ADR-adjacent architecture notes, or prose edits to docs already in the tree. Covers matching Kavo's dense, code-first doc voice and running a humanizer pass before landing the page.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: