breach-encapsulation-naming
CommunityExplicit getter naming to preserve encapsulation.
Software Engineering#code-review#getter#domain-model#naming-convention#tell-dont-ask#breach-encapsulation
Authorj5ik2o
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Getter overuse breaks encapsulation in domain models; using a breachEncapsulationOf prefix makes such access explicit, helping teams respect Tell Don't Ask and prevent uncontrolled usage of getters.
Core Features & Use Cases
- Enforces explicit getter naming to signal encapsulation breaches in domain models across languages (Java, Kotlin, Scala, TypeScript, Python, Go, Rust).
- Provides a standardized breachEncapsulationOf<PropertyName>() pattern for accessors required for persistence or serialization.
- Supports code review, new implementations, and refactoring by guiding getter design decisions.
Quick Start
Refactor domain model getters to breachEncapsulationOf-prefixed accessors where persistence or serialization demands access.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: breach-encapsulation-naming Download link: https://github.com/j5ik2o/okite-ai/archive/main.zip#breach-encapsulation-naming Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.