Reference Quality Maintainer
Use this skill when implementing/refactoring behavior that should remain easy to learn from.
Quality Bar
- •Prefer explicit, descriptive names for classes, functions, and tests.
- •Keep module/package structure aligned with responsibility.
- •Reduce ambiguity before adding abstraction.
- •Keep examples small but complete enough to teach behavior.
Mandatory Checks
- •Naming clarity check: can intent be inferred without external context?
- •Structure check: is behavior in the correct module/layer?
- •Test check: is changed behavior covered by readable tests?
- •Validation check: run relevant Gradle checks for touched modules.
Anti-Patterns
- •Mixing processor internals into workload examples.
- •Hidden behavior changes without test updates.
- •Clever but opaque generation logic.
- •Documentation that drifts from implemented behavior.