Ground decisions in current code

Ground decisions in current code

When a change depends on an API, type or convention, read that source before editing. Current repository evidence reduces reliance on a model's memory of a similar project. Before generation, identify the claims the change must get right and fetch the source for each one. For an API call, read the installed signature. For a repository convention, read the nearest instructions and examples. For behavior, inspect the relevant test and caller. If a source is missing or stale, stop and state the uncertainty instead of filling the gap from memory. After the edit, reread the changed region against those sources.

• Load exact definitions, types and nearby tests for the symbols the edit will use.
• Use a structured edit format and reject malformed or ambiguously anchored changes before applying them.
• Read repository documentation or installed package types when a library API affects the change.