skills.rest
robpitcher
robpitcherCOMMUNITY
Explore all skills by this author →
GitHub

docs-standards

Enforce Microsoft Style Guide rules and squad formatting patterns in documentation pages.

Updated Apr 14, 2026
Search Tags:#documentation#consistency#readability#formatting#style-guide#squad-patterns
One-click install
npx skills add https://github.com/robpitcher/eShopOnWeb --skill docs-standards-robpitcher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/docs-standards
Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill docs-standards-robpitcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad documentation follows the Microsoft Style Guide with Squad-specific conventions. Consistency across docs builds trust and improves discoverability.

Core Features & Use Cases

  • Enforces Microsoft Style Guide rules: sentence-case headings, active voice, present tense, second person, and no ampersands in prose.
  • Applies squad formatting patterns to improve scannability and cross-references.
  • Use case: When creating or updating docs pages, apply the standard so pages are predictable and easy to navigate.

Quick Start

Start by applying the Microsoft Style Guide and Squad formatting to a new documentation page.

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 multiple squads?▼

To enforce documentation consistency across squads, apply a standardized style guide and formatting patterns during page creation and auditing. This ensures predictable structure, readability, and reliable cross-references across all squad documentation.

What Microsoft Style Guide rules apply to technical documentation formatting?▼

Microsoft Style Guide rules for technical documentation formatting include using sentence-case headings, active voice, present tense, second person, and no ampersands in prose. These rules improve readability and scannability.

How do I audit existing documentation pages for style guide compliance?▼

Auditing documentation pages for style guide compliance involves checking existing content against standardized formatting rules. You verify sentence-case headings, active voice, present tense, and proper cross-references to ensure readability.

Can I use squad formatting patterns to improve documentation readability?▼

Yes, you can use squad formatting patterns to improve documentation readability. These patterns standardize page structure and cross-references, making content predictable and easy to navigate for all squad members.

What's the best way to standardize squad documentation style?▼

The best way to standardize squad documentation style is enforcing a standardized formatting approach like the Microsoft Style Guide. Applying these rules during creation and editing builds trust and improves content discoverability across squads.

Why does documentation consistency matter for squad standards?▼

Documentation consistency matters for squad standards because it builds trust and improves discoverability. Predictable formatting, structure, and cross-references ensure pages are easy to navigate and read across the entire squad.

Related Skills

Explore More Content & Communication Skills→
sachinnair90sachinnair90

docs-standards

Standardize Markdown documentation to match Microsoft Style Guide and squad rules.

Community
Basic
channgchanng
20

docsify

Generate static documentation websites from markdown files with sidebar navigation.

Community
Basic
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate
nicolehaugennicolehaugen

docs-standards

Enforce Microsoft Style Guide and squad-specific conventions in technical documentation.

Community
Intermediate