carrot-foundation/schemas

rule-schema-versioning

Schema version injection, $id format, and SCHEMA_VERSION environment variable

rule-json-schema

Generated JSON Schema structure — required fields, validation patterns, and $ref usage

finish-work

Use when a task is complete and needs the full check, commit, and PR workflow

rule-code-preservation

Preserve existing behavior during refactoring — no silent deletions or reversions

unit-test

Use when writing or updating tests for schemas, especially when 100% coverage is required

update-examples

Use when schemas have changed and example JSON files need regeneration and validation

zod

Use when authoring or modifying Zod schemas -- composition, metadata, and validation patterns

create-schema

Use when scaffolding a new schema type directory with data, attributes, tests, and index

schema-reviewer

Reviews schema design quality — Zod patterns, metadata completeness, composition correctness, naming, backward compatibility

check

Use when running quality gates before committing, creating a PR, or validating the project builds correctly

coderabbit

Use when triggering a CodeRabbit review on current changes or a pull request

commit

Use when staging and committing code changes with conventional commit messages

create-branch

Use when starting new work and need a branch following naming conventions

create-pr

Use when work is ready for review and a pull request needs to be created

debug

Use when schema generation fails, validation errors occur, or tests fail unexpectedly

review-pr

Use when reviewing a pull request for schema quality, test coverage, and conventions

rule-code-comments

When and how to write effective comments — favor self-documenting code

rule-code-style

Readable, consistent, and well-structured code across the schemas package

rule-commit

Conventional commit messages with schemas-specific scopes

rule-naming-conventions

Naming standards — snake_case properties, kebab-case files, PascalCase types and exports

rule-package-management

pnpm only, exact versions, Node >= 22, and minimal dependencies

rule-pull-request

PR creation workflow, title format, description template, and quality gates

rule-testing

Vitest patterns, 100% coverage thresholds, and fixture-driven schema validation

rule-typescript

TypeScript conventions — strict mode, type patterns, and inference preferences

rule-zod

Zod schema authoring — strictObject, safeExtend, meta(), and composition layers

verifier

Validates completed work — tests at 100% coverage, schemas generate correctly, versions consistent, examples valid