Development

​

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

• 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

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

​

Current implementation note

• 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

pnpm lint
pnpm typecheck
pnpm test
pnpm build

pnpm --filter api test
pnpm --filter worker test
pnpm --filter control-plane test
pnpm --filter @repo/database typecheck

​

Read next

• Contribution Workflow
• Issue & PR Etiquette
• Release Process