Files
calendar/agents/rules
Eunjae LeeGitHubDevin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
f691258a5c refactor(agents): move prescriptive content from knowledge-base to rules (#26925)
* refactor(agents): move prescriptive content from knowledge-base to rules

- Create architecture-page-level-auth.md for Next.js auth checks
- Create data-prefer-select-over-include.md for Prisma query optimization
- Create performance-dayjs-usage.md for Day.js performance guidelines
- Create quality-avoid-barrel-imports.md for import best practices
- Update knowledge-base.md to reference rules directory
- Remove duplicated prescriptive content from knowledge-base.md

Co-Authored-By: eunjae@cal.com <hey@eunjae.dev>

* chore(agents): remove redundant rules reference from knowledge-base

Co-Authored-By: eunjae@cal.com <hey@eunjae.dev>

* docs: add agents/rules reference to AGENTS.md extended documentation

Co-Authored-By: eunjae@cal.com <hey@eunjae.dev>

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-01-16 10:43:36 -03:00
..

Cal.com Engineering Rules

This directory contains modular, machine-readable engineering rules derived from Cal.com's Engineering Standards for 2026 and Beyond.

Structure

Rules are organized by section prefix, as defined in _sections.md:

Prefix Section Impact
architecture- Architecture CRITICAL
quality- Code Quality CRITICAL
data- Data Layer HIGH
api- API Design HIGH
performance- Performance HIGH
testing- Testing MEDIUM-HIGH
patterns- Design Patterns MEDIUM
culture- Team Culture MEDIUM

Files

  • _sections.md - Defines all sections, their ordering, and impact levels
  • _template.md - Template for creating new rules
  • {section}-{rule-name}.md - Individual rule files

Rule Format

Each rule file follows a consistent format with YAML frontmatter:

---
title: Rule Title Here
impact: CRITICAL | HIGH | MEDIUM | LOW
impactDescription: Optional description (e.g., "20-50% improvement")
tags: tag1, tag2, tag3
---

## Rule Title Here

**Impact: LEVEL (optional description)**

Brief explanation of the rule and why it matters.

**Incorrect (description):**
\`\`\`typescript
// Bad code example
\`\`\`

**Correct (description):**
\`\`\`typescript
// Good code example
\`\`\`

Reference: [Link](url)

Adding New Rules

  1. Copy _template.md to a new file with the appropriate section prefix
  2. Fill in the frontmatter (title, impact, tags)
  3. Write a clear explanation of the rule
  4. Provide incorrect and correct code examples
  5. Add a reference link if applicable

Usage

These rules are designed to be:

  • Human-readable: Engineers can browse and learn from them
  • Machine-readable: AI agents can parse and apply them
  • Modular: Individual rules can be updated without affecting others
  • Versionable: Changes are tracked in git history

Core Principles

From the blog post, our engineering philosophy is:

We are building infrastructure that must almost never fail. To achieve this, we move fast while shipping amazing quality software with no shortcuts or compromises.

The rules in this directory encode the specific practices that enable this philosophy.