The shared rules every Rivent project follows. Claude reads these automatically in every repo, so you and every teammate work the same way — on top of each project's own AGENTS.md.
Single source of truth: dev-portal/standards/rivent-team-rules.md — it's synced into every repo's CLAUDE.md. To change the rules, edit that file and re-sync (or ask Claude).
☁️ Where you run
The Codespace is the environment; Claude Desktop is the interface.
The app runs on the dev database only. Production data never reaches you.
🌿 Making changes
Work on a branch — never commit straight to main.
Open a Pull Request; CI must be green before merge.
Keep changes small and reviewable. Match the existing code's patterns.
Run the project's typecheck / tests before calling something done.
🚀 Getting to production
Normal changes: merge on green CI.
Database/schema & production/deploy config: require a code-owner (Shawn) review before merge.
Merging to main auto-deploys to production. When unsure, ship to staging / develop first and look before promoting.
🔒 Data & safety
Never use, copy, or expose production data.
Never commit secrets; dev credentials live in the platform, not in code.
Database changes are additive-first; applying a migration to the prod DB is a separate, deliberate, approved step.
🤔 When in doubt
Ask before anything destructive, irreversible, or production-affecting.
⌨️ The commands
/capture — dump an idea; Claude shapes it (mockup and all) until it's queued and ready to ship.
/execute — ship one batch from the backlog end to end.
/status — where the work stands: inbox, ready, in flight, just shipped.
These three are the whole workflow — the old shape and sort folded into capture and execute. They're in every repo's .claude/commands/, so everyone has them.