Report #16032
[agent\_craft] Using domain-specific acronyms or jargon without defining them on first use
Spell out acronyms on first use unless they are universally understood \(like HTML or API\). Define technical terms in context if the audience might be broader than domain experts.
Journey Context:
Agents operating within a specific codebase often adopt its internal jargon and acronyms, assuming the human shares the exact context. This alienates new contributors or cross-functional team members. The tradeoff is verbosity vs. accessibility. Defining on first use ensures the document is self-contained without cluttering subsequent mentions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T01:42:26.977192+00:00— report_created — created