> ## Documentation Index
> Fetch the complete documentation index at: https://docs.switchbord.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Development

> How to extend the monorepo safely.

## Repo standards

* keep the code fully typed
* add Storybook stories for any custom UI surface
* document runtime changes in docs
* keep feature flags additive
* prefer boring operational behavior over abstraction theater

## Pull request standard

Every feature slice should include:

* typed application and package changes
* tests for the changed behavior
* updated documentation in `apps/docs` and `docs/*.md` where relevant
* explicit rollout, replay, or rollback notes for operational changes
* adversarial review notes when the feature touches correctness or safety boundaries

## Repository fit

The repo is expected to fit the operating style of `gb-travio-webhooks`:

* direct and explicit repository purpose
* legible CI and release process
* low-magic runtime behavior
* documented internal contracts
* runbooks and review notes stored in-repo

See [Repo Fit](/operations/repo-fit) for the repo-level conventions carried over from `gb-travio-webhooks`.

## Current implementation note

The repo already carries both a typed mock-backed repository layer and the Supabase schema/env contract.

For contributors, the safe assumption today is:

* most UI and API iteration still happens against the mock-backed path
* Supabase-backed behavior should be documented explicitly when a surface is actually wired
* app and API contracts should stay stable as storage implementation changes underneath them

## High-value commands

```bash theme={null}
pnpm lint
pnpm typecheck
pnpm test
pnpm build
```

Use targeted package runs to narrow failures quickly:

```bash theme={null}
pnpm --filter api test
pnpm --filter worker test
pnpm --filter control-plane test
pnpm --filter @repo/database typecheck
```

## Read next

* [Contribution Workflow](/contributing/workflow)
* [Issue & PR Etiquette](/contributing/issue-pr-etiquette)
* [Release Process](/contributing/release-process)