docs-standards

Enforce Microsoft Style Guide and Squad-specific conventions in project documentation.

3|Updated Mar 15, 2026

Search Tags:#documentation #consistency #readability #style guide #writing standards #squad

Ready to run

npx skills add https://github.com/bradygaster/docx-mcp-server --skill docs-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/bradygaster/docx-mcp-server/tree/main/.squad/templates/skills/docs-standards
Command: npx skills add https://github.com/bradygaster/docx-mcp-server --skill docs-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensures all documentation adheres to established Microsoft Style Guide rules and Squad-specific conventions, improving readability, trust, and discoverability.

Core Features & Use Cases

Style Guide Enforcement: Applies rules like sentence-case headings, active voice, and second-person perspective.
Formatting Conventions: Implements patterns for scannability, practical prompts, experimental warnings, and cross-references.
Use Case: Maintain a consistent and professional tone across all Squad documentation, making it easier for new contributors to understand and follow established practices.

Quick Start

Ensure all new documentation follows the defined Microsoft Style Guide and Squad Formatting Patterns.

Frequently Asked Questions about docs-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce documentation consistency across a team project?▼

Documentation consistency is enforced by applying Microsoft Style Guide rules and squad-specific conventions during the creation and review of all project documents to ensure scannability and a professional tone for contributors.

What writing standards does this approach use to improve readability?▼

Writing standards based on the Microsoft Style Guide improve readability by enforcing sentence-case headings, active voice, and second-person perspective, alongside specific squad conventions for prose style and document structure.

How do I apply a style guide to review technical documentation?▼

Applying a style guide to review technical documentation involves checking content against established formatting patterns for practical prompts, experimental warnings, and cross-references to verify adherence to required prose style and document structure.

Can I use Microsoft Style Guide conventions for squad-specific documentation?▼

Yes, you can use Microsoft Style Guide conventions for squad-specific documentation by combining baseline style rules with custom squad formatting patterns to maintain consistency, trust, and discoverability across project files.

What formatting conventions improve scannability in project documentation?▼

Formatting conventions that improve scannability in project documentation include implementing structured patterns for practical prompts, experimental warnings, and cross-references, alongside using sentence-case headings and active voice.