Documentation Writing

This enforces the Eight Rules and Diataxis framework when writing software docs. It automatically activates when you mention creating READs, tutorials, or API docs, then makes sure everything lands in docs/, gets linked from at least one other file, and uses real runnable examples instead of foo/bar placeholders. The strict separation between doc types (tutorial vs how-to vs reference vs explanation) keeps things focused, and it actively blocks you from putting temporal stuff like test results or status updates in documentation. Opinionated in a way that actually saves time during code review.