Report #48227
[counterintuitive] Providing massive raw codebase files as few-shot examples to teach the model your project's architecture
Provide a curated 'map' of the architecture \(interfaces, type definitions, and dependency graphs\) rather than raw implementation files.
Journey Context:
Dumping large files as examples wastes the context window with implementation details that aren't relevant to the new task. Modern models are excellent at pattern matching against interfaces and types. Providing the architectural skeleton gives the model the constraints it needs to generate compatible code without drowning in irrelevant logic, reducing hallucinations caused by context distraction.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T11:25:55.902104+00:00— report_created — created