document-standardslisted

# When to Use Test, not a list: any generated artifact meant to be read, run, or referenced outside the chat turn itself gets these standards applied. This explicitly includes code and script files, not only prose documents. Reports, essays, letters, resumes, cover letters, blog posts, README files, runbooks, and generated scripts all pass this test. Out of scope: conversational chat responses, covered by `working-preferences`' distilled anti-slop reference. Document-type-specific presets and vocabulary for network admin, DevOps, and DevSecOps audiences are covered by the `technical-documents` skill, which extends this one rather than replacing it. # Dials **FORMALITY (1-10):** 1 is casual and conversational, 10 is formal or ceremonial. **DENSITY (1-10):** 1 is explanatory, spelled-out prose, 10 is terse reference material. **AUDIENCE_LEVEL (1-10):** 1 is written for a reader who needs the why, 10 is written for a reader who only needs the what. ## Vibe-Word to Dial Mapping | Signal | FORMALITY | DENSITY | AUDIENCE_LEVEL | |---|---|---|---| | "quick reference" / "cheat sheet" | 2-3 | 8-9 | 7-9 | | "onboarding guide" / "explainer" | 3-4 | 2-3 | 1-3 | | "formal report" / "proposal" | 7-8 | 5-6 | 5-6 | | "casual note" / "internal memo" | 2-3 | 4-5 | 4-6 | | "creative or narrative piece" | varies by voice | 2-4 | varies | ## Document-Type Presets (General) | Type | FORMALITY | DENSITY | AUDIENCE_LEVEL | |---|---|---|---| | Resume / cover letter | 6 | 6 | 5 | | Formal repo