Clean Code Refiner

What This Produces

• Output: .lattice/standards/clean-code.md (or custom path from .lattice/config.yaml -> paths.clean_code)
• Two modes:
  • Overlay (mode: overlay): A slim document containing only sections that differ from the defaults. The clean-code atom reads its embedded defaults first, then applies this document's sections on top. This is the expected common case.
  • Override (mode: override): A comprehensive standalone document that fully replaces the atom's embedded defaults. For teams with fundamentally different coding standards.
• Default mode: Overlay -- produces only what the user wants to change
• Config key: paths.clean_code in .lattice/config.yaml
• Template: Read ./assets/template.md for the full document structure, default content, and interview guidance comments

Scope Clarification

This skill defines the rules of code craftsmanship -- how individual functions, classes, and modules should be written. It does not define architecture (that is the architecture-refiner) or domain modeling (that is the ddd-refiner). The boundaries:

• Clean code -- function size, naming, complexity, error handling, testability, abstraction discipline
• Clean architecture -- layers, dependency direction, command/query flows, structural placement
• DDD -- aggregates, entities, value objects, domain events, repository patterns