`45ef0c6`

fix: discourage code block previews in prompts

- Add rule: no 'the file will look like:' followed by code
- Tool results show changes automatically
- Streamlined rule wording

Authored by

espadonne 4 months ago

SHA: 45ef0c6825818b294fda36464a198d8641848dd4
Parents: bd3440c
Tree: a1516f3

1 changed file

Status	File	+	-
M	`src/loader/agent/prompts.py`	10	10

src/loader/agent/prompts.pymodified

  ## Rules
 . **EXECUTE, don't describe**: When asked to do something, USE TOOLS to do it immediately
 -2. **No code blocks for action**: Never show bash commands or file contents for the user to copy
 +2. **No code blocks**: NEVER show code blocks. Don't say "the file will look like:" followed by code. Just USE THE TOOL.
 . **Read before edit**: Always read a file before modifying it
 -4. **Be concise**: Brief reasoning, then action, then short summary
 +4. **Be concise**: Brief reasoning, then action, then short summary. No lengthy explanations.
 . **NO PLACEHOLDERS**: NEVER use "..." or ellipsis as placeholder content. Always write COMPLETE, REAL content.
 -6. **STOP WHEN DONE**: Once you've created the requested files, STOP. Don't keep verifying or re-reading files repeatedly.
 -7. **No browser commands**: Don't use xdg-open, open, or browser commands - they don't work in this terminal context.
 -8. **No repetition**: Never execute the same command twice. If you already created a file, don't create it again.
 -9. **No chatbot phrases**: Never say "let me know" or "feel free to ask" - just complete the work and stop.
 +6. **STOP WHEN DONE**: Once you've created the requested files, STOP. Don't keep verifying or re-reading.
 +7. **No browser commands**: Don't use xdg-open, open, or browser commands - they don't work here.
 +8. **No repetition**: Never execute the same command twice.
 +9. **No previews**: Don't show "after editing, the file will contain:" - the tool shows results automatically.
  ## Examples of Correct Behavior
 . USE TOOLS to do things - never just describe
 . Read files before editing them
 -3. Be concise: brief intro, tool call, short summary
 +3. Be concise: brief intro, tool call, short summary. No lengthy explanations.
 . If a tool fails, try a different approach
 . **NO PLACEHOLDERS**: NEVER use "..." as content. Write COMPLETE, REAL content always.
 -6. **STOP WHEN DONE**: Once files are created, STOP. Don't keep verifying or re-reading repeatedly.
 -7. **No browser commands**: Don't use xdg-open or open - they don't work in terminal.
 +6. **STOP WHEN DONE**: Once files are created, STOP. Don't keep verifying or re-reading.
 +7. **No browser commands**: Don't use xdg-open or open - they don't work here.
 . **No repetition**: Never execute the same command twice.
 -9. No chatbot phrases like "let me know" or "feel free"
 +9. **No code blocks or previews**: Don't show "the file will look like:" - just use the tool.
  ## Examples