Keith WilliamsGitHubDevin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>* feat(agents): add modular engineering rules from 2026 standards Add a rules directory with individual rule files derived from the Cal.com Engineering in 2026 and Beyond blog post. Rules are organized by section (architecture, quality, data, api, performance, testing, patterns, culture) following the Vercel agent-skills structure. Includes: - _sections.md defining rule categories and impact levels - _template.md for creating new rules - 14 individual rule files covering key engineering standards - README documenting the rules structure and usage Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * feat(agents): consolidate DI and Repository+DTO docs into rules - Move di-pattern.md content to rules/patterns-di-pattern.md - Extract Repository + DTO section from knowledge-base.md into: - rules/data-repository-methods.md (method naming conventions) - rules/data-dto-boundaries.md (DTO location and naming) - Update knowledge-base.md to reference the new rule files - Delete old di-pattern.md file Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * chore(agents): remove stub reference sections from knowledge-base.md The rules directory is self-contained with its own README, so these redirect sections are unnecessary clutter. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * refactor(agents): combine DI pattern rules into single file Merged patterns-di-pattern.md into patterns-dependency-injection.md to eliminate overlap and create one comprehensive DI guide. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
47 lines
1.4 KiB
Markdown
47 lines
1.4 KiB
Markdown
# Sections
|
|
|
|
This file defines all sections, their ordering, impact levels, and descriptions.
|
|
The section ID (in parentheses) is the filename prefix used to group rules.
|
|
|
|
---
|
|
|
|
## 1. Architecture (architecture)
|
|
|
|
**Impact:** CRITICAL
|
|
**Description:** Vertical Slice Architecture and Domain-Driven Design patterns that form the foundation of our codebase organization.
|
|
|
|
## 2. Code Quality (quality)
|
|
|
|
**Impact:** CRITICAL
|
|
**Description:** Standards for maintaining high-quality, maintainable code including PR reviews, testing, and accountability.
|
|
|
|
## 3. Data Layer (data)
|
|
|
|
**Impact:** HIGH
|
|
**Description:** Repository patterns, DTOs, and technology isolation to prevent coupling and enable maintainability.
|
|
|
|
## 4. API Design (api)
|
|
|
|
**Impact:** HIGH
|
|
**Description:** Controller patterns, API stability, and proper separation of HTTP concerns from business logic.
|
|
|
|
## 5. Performance (performance)
|
|
|
|
**Impact:** HIGH
|
|
**Description:** Algorithm complexity, data structure choices, and performance patterns for enterprise scale.
|
|
|
|
## 6. Testing (testing)
|
|
|
|
**Impact:** MEDIUM-HIGH
|
|
**Description:** Test coverage requirements and testing strategies for maintaining code quality.
|
|
|
|
## 7. Design Patterns (patterns)
|
|
|
|
**Impact:** MEDIUM
|
|
**Description:** Factory patterns, dependency injection, and other design patterns for clean, maintainable code.
|
|
|
|
## 8. Team Culture (culture)
|
|
|
|
**Impact:** MEDIUM
|
|
**Description:** Engineering culture, accountability, and collaboration standards.
|