Dygo Code Quality

---
name: dygo-code-quality
description: Improve or review ordinary dygo code changes for simplicity, focused scope, canonical ownership, clear boundaries, and verifiable behavior. Use for normal implementation and refactoring quality; use dygo-thermonuclear-review only for an explicitly severe audit.
---

# dygo Code Quality

Make the smallest coherent change that solves the stated problem.

## Before Editing

- State material assumptions.
- Inspect the current implementation and nearby conventions.
- Define an observable success condition.
- Identify the canonical package, metadata contract, SDK boundary, or Studio component that owns the behavior.

## Rules

- Keep every changed line tied to the task.
- Do not clean unrelated code or reformat unrelated files.
- Prefer direct code over speculative abstraction.
- Reuse an existing framework primitive when it expresses the same contract.
- Do not add a thin wrapper, flag, optional mode, or generic registry without a real repeated need.
- Keep business logic in Apps and reusable platform capability in the framework.
- Keep internals private until Business Apps need a stable public contract.
- Remove only dead code that the current change creates unless cleanup is in scope.
- Add a concise TODO only when a real deferred improvement has a clear boundary and cannot be completed in the current scope.
- Verify behavior in proportion to risk.

If a solution becomes much larger than the behavior it provides, stop and simplify it before finalization.