tayari-docs-and-writing

Prevent documentation rot by enforcing a strict ownership model and house style standards across all project documents. This skill maintains repo-wide documentation integrity by requiring one-home-per-fact discipline and date-stamped verification of volatile technical facts.

The one-home-per-fact discipline is a documentation governance rule that assigns a single, definitive document to own each specific technical fact. It prevents information drift by ensuring volatile facts, like port numbers and environment variables, are updated and verified in only one location.

Verify the current owner and trust status of a README by consulting the Doc Map Ownership guide. This provides a definitive guide on which document owns specific facts and whether that document is currently trustworthy before you make any edits.

Safely update volatile technical facts by following verified safe fix checklists. These procedures offer verified steps for repairing corrupted files or updating volatile facts like port numbers and environment variables while maintaining documentation integrity.

Enforce a specific house style for documentation across your entire repository using this skill. It standardizes the project's terse, caveman-style writing for all documentation to ensure consistent technical writing and knowledge management.

Documentation ownership rules are needed when maintaining project-wide docs of record, architectural contracts, and operational guides. Applying these repo governance rules prevents information drift and ensures volatile technical facts remain date-stamped and verified.