What problem does it solve? Documentation written by multiple contributors drifts in tone, heading style, and structure, which hurts readability and breaks automated doc tests. This Skill provides a single reference for Microsoft Style Guide rules plus Squad-specific formatting patterns so every page stays consistent. ## Core Features & Use Cases - Style rule enforcement: Sentence-case headings, active voice, second person, present tense, and no ampersands in prose. - Squad formatting patterns: Scannable structure with short paragraphs, bullet lists, "Try this" prompts at the top, experimental warnings, and cross-references at the bottom. - Test sync rule: Reminds contributors to update EXPECTED_* arrays in test/docs-build.test.ts whenever pages are added to features/, scenarios/, or guides/. - Use Case: When drafting a new feature page, apply the prescribed structure (H1 title, warning callout, try-this code block, overview, H2 sections) and update the doc build test assertions in the same commit. ## Quick Start Review my new documentation page against the Squad docs standards and fix any style or formatting violations.
