Breach Encapsulation Naming

Use when designing or reviewing domain-model accessors that expose internal state for persistence, serialization, tests, or framework integration. Applies the breachEncapsulationOf naming pattern so unavoidable getters are visibly treated as encapsulation breaches, not casual domain APIs. Trigger for getter naming conventions, persistence-only getters, serialization accessors, Tell Don't Ask pressure, or requests to prevent getter misuse.

amadeus-dlc Updated

File contents

amadeus-dlc/amadeus commit 584ec597f2

Frequently asked questions

npx get-skill add amadeus-dlc/breach-encapsulation-naming