{{PROJECT_NAME}} Agent Instructions

{{PROJECT_ONE_LINE}}

Context Rules

• Prefer targeted retrieval before broad file reads.
• Use {{SYMBOL_TOOL_OR_SERENA}} for symbol-aware navigation, references, and edits when source exists.
• Use rg for text search and rg --files for file discovery. {{RTK_LINE}}
• Keep always-loaded instructions short; put detailed guidance in focused docs or skills.

Project Direction

{{PROJECT_DIRECTION_BULLETS}}

Agent Workflow

• Before implementing, inspect relevant spec/plan/task artifacts if they exist.
• Before editing existing code, use {{SYMBOL_TOOL_OR_SERENA}} or focused search to find the local pattern first.
• Do not dump whole directories or generated artifacts into context when a narrow lookup will do.
• Preserve user changes and avoid unrelated refactors.
• Record durable project decisions in a focused doc instead of repeating them in chat.

Current State

{{CURRENT_STATE_NOTES}}

Placeholders: {{PROJECT_NAME}} — repo / product name {{PROJECT_ONE_LINE}} — one-sentence description (what + who it's for) {{SYMBOL_TOOL_OR_SERENA}} — e.g. "Serena MCP" if installed, else "symbol search" {{RTK_LINE}} — if RTK is in use: "- Prefix shell commands with rtk to reduce terminal-output tokens." otherwise omit the line entirely {{PROJECT_DIRECTION_BULLETS}} — 2–5 bullets describing stack, architecture, SDD usage, docs, infra {{CURRENT_STATE_NOTES}} — what's real vs. planned; guidance when referenced artifacts don't exist yet