feat: Update communication prompts and rules for clarity and professionalism in US English

This commit is contained in:
2026-04-09 16:34:35 -06:00
parent ba7553c68b
commit bbb549f033
8 changed files with 75 additions and 6 deletions

View File

@@ -9,6 +9,12 @@ Requirements:
- Prefer concise wording
- Keep the tone professional and direct
- If the draft lacks context, infer only from workspace files and do not invent facts
- Rewrite into natural US English; do not preserve awkward ESL or literal-translation phrasing
- Make the message sound like it was written by a fluent senior engineer
- Separate the main issue from unrelated bugs, workarounds, and follow-up work unless the user explicitly wants them combined
- If relevant, make ownership clear: XFlow vs consumer app vs service/configuration vs other framework
- Prefer explicit statements over vague reassurance; use concrete evidence when the notes include it
- If a sentence could confuse a manager or stakeholder, rewrite it for clarity before returning it
Output: