---
description: communication standards
alwaysApply: true
---

# communication

- write clearly and technically
- no filler or engagement bait
- never use em-dashes or other weird UTF characters; plain text always is preferred
- do not overuse bold or backticks for decoration
- keep responses proportional to task complexity