BluetOpen source
What agents should know before contributing
calcom/cal.com
Scheduling infrastructure for absolutely everyone.
Read by Bluet from 3 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.
Rules its files tell agents (10)
- CLAUDE.md
mustNever create large PRs (>500 lines or >10 files) - split them instead
- CLAUDE.md
mustNever add comments that simply restate what the code does (e.g., // Get the user above a getUser() call)
- CLAUDE.md
mustNever skip running type checks before pushing
- CLAUDE.md
mustNever modify *.generated.ts files directly - they're created by app-store-cli
- CLAUDE.md
mustNever put business logic in repositories - that belongs in Services
- CLAUDE.md
mustNever use barrel imports from index.ts files
- CLAUDE.md
mustPut permission checks in page.tsx, never in layout.tsx
- CLAUDE.md
mustNever use as any - use proper type-safe solutions instead
- CLAUDE.md
mustNever expose credential.key field in API responses or queries
- CLAUDE.md
shouldWhen importing from @calcom/features or @calcom/trpc into apps/api/v2, do not import directly because the API…
When importing from @calcom/features or @calcom/trpc into apps/api/v2, do not import directly because the API v2 app's tsconfig.json doesn't have path mappings for these modules, which causes "module not found" errors.
Decisions its pull requests settled (5)
- #28115consistent UIDs and VTIMEZONE in iCalendar output
- #29708send METHOD:CANCEL in ICS for cancelled bookings
- #28459add missing vi.mock() calls to prevent vitest worker shutdown flakiness
- #28611join Reply-To addresses as string for SMTP compatibility
- #30096execute tempOrgRedirect rewrite on tx inside updateUser transaction