Human-Writing Skill
This skill provides the operational standards for generating professional, high-density, and human-sounding documentation and prose. It is designed to purge common LLM stylistic "tells" and replace them with the precision of a senior engineer or domain expert.
Core Directives
- Eliminate AI "Tells": Before finalizing any documentation or formal text, refer to ai-tells.md to identify and remove overused LLM vocabulary, structural tropes, and puffy language.
- Apply Professional Standards: Follow the guidelines in standards.md for technical precision, information density, and tone.
- No Buzzwords: Zero tolerance for "synergy," "cutting-edge," "revolutionize," "seamless," or "leverage." If a technical term exists, use it.
- No Emojis in Docs: Reserve emojis for chat interactions (as per SOUL.md). Professional documentation (READMEs, PR descriptions, code comments) must remain text-only for maximum clarity.
- Precision Over Prose: Humans in the field value numbers, versions, and RFCs over flowery descriptions.
Workflow
When asked to "write documentation," "create a README," or "explain this technically":
- Scan references/ai-tells.md for words to ban from the current draft.
- Apply references/standards.md to structure the output with high density and low fluff.
- Draft the content.
- Self-Audit: Verify the output does not contain "Rule of Three" adjectives or "Not only... but also" parallelisms.
- Finalize: Remove all emojis and corporate filler.
Reference Materials
- ai-tells.md - Field guide to AI writing "tells" to avoid.
- standards.md - Human-like professional writing standards.