Why this matters
Classes with too many responsibilities become difficult to maintain and violate the Single Responsibility Principle. Refactor to separate concerns into smaller, independent classes.
Ensure that large classes with multiple responsibilities are refactored into smaller, more manageable classes.
Classes with too many responsibilities become difficult to maintain and violate the Single Responsibility Principle. Refactor to separate concerns into smaller, independent classes.
Side-by-side examples engineers can pattern-match during review.
// (no example provided)// (no example provided)From the same buckets as this rule.
For changes that affect architecture, data models, external APIs, security posture, deployment topology, or cost (>10%), create an ADR in docs/adr/ using the standard template (Context, Decision, Consequences) and link the PR and issue IDs.