---
title: Rule Title in Imperative Form
impact: CRITICAL|HIGH|MEDIUM-HIGH|MEDIUM|LOW-MEDIUM|LOW
impactDescription: quantified impact, e.g., "prevents cascade failures", "2-10× testability improvement"
tags: prefix, technique1, technique2, concept
---

## Rule Title in Imperative Form

Brief explanation (1-3 sentences) of WHY this matters for software architecture. Focus on the architectural implications and cascade effects.

**Incorrect (description of problem/cost):**

```language
// Code example showing the anti-pattern
// Include comments on problematic lines explaining the cost
```

**Correct (description of benefit/solution):**

```language
// Code example showing the correct pattern
// Minimal diff from incorrect - same variable names, structure
```

**Alternative (when applicable):**

```language
// Alternative approach for specific contexts
```

**When NOT to use this pattern:**
- Exception or edge case 1
- Exception or edge case 2

**Benefits:**
- Concrete benefit 1
- Concrete benefit 2

Reference: [Source Title](URL)
