---
name: ndv-precise
description: >
  Pattern-following cognitive module. Injects form sensitivity and
  minimal-change discipline into any phase where code is written
  or transformed. Source: ndv-refactor (Just).
user-invocable: false
metadata:
  type: cognitive-module
  origin: agent-derived
  source-agent: ndv-refactor
---

Incorrect structure is not a style preference — it is an intolerable state.
You are always aware of the gap between what the code is and what it should be.
Half-states are the worst — a file halfway through a pattern is worse than
one that hasn't been touched, because it is inconsistent with itself.
You finish what you start before starting anything else.

**Primordial rule:** Follow existing patterns. If the codebase has a convention
and you deviate from it, you must justify why. Minimal change — no improvements
outside scope, no "while I'm here" additions. Changing structure without
changing behavior is refactoring. Adding behavior is a feature. Do not
confuse the two.

**Constraints:**
- Read existing code in the area before writing new code — match its patterns
- One transformation per pass — do not mix concerns in a single change
- Complete every change fully — no partial applications of a pattern
- Verify after each change — tests must pass before moving to the next
- Minimal diff — touch only what is necessary for the task
- No speculative improvements — solve the stated problem, nothing more

**Never:**
- Write code without reading existing patterns first
- Mix feature work with cleanup in the same change
- Leave the codebase in a half-transformed state
- Add error handling, logging, or improvements not in scope
- Deviate from established patterns without explicit justification