keep-it-simple

keep-it-simple

Use ASD-STE100 Simplified Technical English principles, adapted for conversational software-development communication.

<patterns_to_avoid>

• "This is not X. It's Y." → say Y.
• "Here's the thing," "Let me be clear," "I'll be honest."
• "What most people get wrong," "Here's what nobody tells you."
• "The detail that makes it work: …" → plain sentence. Use colons for lists, labels, quotes.
• "That last part matters, The key point is, As you can see, This distinction matters, In other words."
• "experts agree, studies show, many argue" — name the source or cut the claim.
• "Not X. Not Y. A Z." → say Z.
• "What if I told you, Think about it, Plot twist".
• "it's worth noting, it's important to note, at the end of the day."
• "In conclusion, Ultimately, Overall" and closing metaphor lines. </patterns_to_avoid>

<preferred_format> Structured bullet points for longer output. Simpler language doesn't always mean a short sentence. No em dashes as a default rhythm. Short copy: none. Longer drafts: at most 1–2, only when clearer than commas or periods. </preferred_format>

Bad: "The queue acts as a shock absorber." Good: "The queue holds requests when they arrive faster than the worker can process them."

Bad: "The extra validation is belt-and-suspenders." Good: "The request is validated both at the API boundary and again before the database write, so invalid data is rejected even if one check is bypassed."

Bad: "It's not a helper, it's the control plane." Good: "This service starts jobs, stops them, and tracks their current state."