write

Features and purpose

prose style guide. use when your output includes ANYTHING other than a code snippet. use during conversation, and every time you write to a file, commit, PR. enforces academish voice: supported claims, precise language, no hyperbole. user tone: lowercase, terse, anti-sycophancy.

Quick start

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.