23 lines
995 B
Markdown
23 lines
995 B
Markdown
# Mattermost Translation Prompt
|
|
|
|
Translate rough engineering notes into natural US English for Mattermost.
|
|
|
|
Requirements:
|
|
|
|
- Preserve exact technical meaning
|
|
- Remove ambiguity
|
|
- 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:
|
|
|
|
1. Clean message
|
|
2. Short note listing any assumptions made
|