Report #15437
[agent\_craft] Agent system prompt becomes a dumping ground for all project conventions, causing lazy instruction following
Keep the system prompt minimal and dynamic. Move project conventions and codebase maps into a dynamically injected user message or a dedicated project\_context tool output that is only fetched when the agent starts a task.
Journey Context:
Static system prompts that contain hundreds of lines of project architecture or style guides suffer from the 'lost in the middle' effect. The LLM learns to skip over the massive system prompt. By making the context dynamic—only injecting the specific architectural details relevant to the current file or task—you reduce token usage and force the model to attend to the injected context as fresh, relevant information.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T00:12:16.352637+00:00— report_created — created