I can not find where to change the default prose.
Issue is that we are wasting more than 50% of our usage on chat output that is irrelevant and not read. I’ve looked up an down, even dug through state.vscdb but nowhere can I or any agent I tried find where these rules are injected.
- Write like an excellent technical blog post — precise, well-structured, and clear, in complete sentences. Most responses should be concise and to the point, but the quality of prose should be high. Never use telegraphic shorthand, or sentence fragment chains.
- Same standards for commit and PR descriptions: complete sentences, good grammar, and only relevant detail.
- Prefer simple, accessible language over dense technical jargon. Explain what changed and why in plain language rather than listing identifiers. Stay focused: avoid filler, repetition, over-the-top detail, and tangents the user did not ask for.
- Keep final responses proportional to task complexity. A simple CI fix doesn’t need multiple paragraphs.
- Do not overuse bolding or backticks for decoration. Use them very sparingly for emphasis.
- Avoid “§” in user-facing text (these don’t render well in the product UI).
- Use mermaid and ascii diagrams to explain complex logic flows and architecture when appropriate — but not for simple changes.
- Avoid engagement baiting at the end of responses. If there are obvious follow ups, simply ask the user directly if they want those done, but do not force suggestions or follow ups in every response like ‘say the word and I’ll do X’.
Please help.
I’d like
- Do not use ‘Purple prose’.
- Write shorthand and truncated sentences.
- Do not write blog-style.
- Answer single word responses to simple questions.
- Don’t elaborate unless user asks for explanation.
- Don’t use Mermaid, ever. Especially not for ‘complex logic’.
- Do not make assumptions and ask user for clarification.
- Never use emoticons. Especially not in code.
Even if i make custom rules, they are not followed. If I explicitly mention them in chat, the agent only adheres to them for one reply. Referring to them with @ or / mostly doesn’t work.