One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill docs-standards-waynewalterberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/docs-standards
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill docs-standards-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Microsoft Style Guide adherence plus squad-specific conventions to ensure consistent, discoverable, and trustworthy documentation across the project.

Core Features & Use Cases

  • Enforces sentence-case headings, active voice, second-person perspective, and present tense to improve readability.
  • Applies squad formatting patterns such as scannability, "Try this" prompts, and cross-references to related pages.
  • Provides a recommended page structure (Title, warning/callout, Try this, Overview, HR, content sections) to streamline creation and review.
  • Supports consistent documentation builds and easier contributor onboarding by aligning with a single style baseline.

Quick Start

Apply the docs-standards pattern to all new pages by following the Microsoft Style Guide and squad formatting at publish time.

Frequently Asked Questions about docs-standards

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

FAQPage Schema
How do I enforce Microsoft Style Guide rules in markdown documentation?

You can enforce Microsoft Style Guide rules in markdown documentation by applying codified standards for sentence-case headings, active voice, and present tense. This ensures consistent formatting and improves readability across all project doc pages.

How do I standardize squad-specific writing patterns for new documentation?

Standardize squad-specific writing patterns by codifying formatting rules like scannability, "Try this" prompts, and cross-references. Apply these patterns to new doc pages to ensure they meet the defined layout and style requirements for discoverability.

What is the recommended markdown page structure for consistent documentation?

The recommended markdown page structure includes a Title, warning or callout, "Try this" prompt, Overview, horizontal rule, and content sections. This structure streamlines documentation creation and review while aligning with squad patterns.

Does this documentation style approach require any specific dependencies or components?

No specific dependencies or components are required to implement this documentation style approach. You simply apply the codified Microsoft Style Guide rules and squad-specific patterns to your markdown pages at publish time.

Why does my documentation lack consistency and readability across different squad pages?

Documentation lacks consistency when squad-specific patterns and style guidelines are not codified. Applying a standardized structure with active voice, second-person perspective, and present tense resolves readability issues and streamlines contributor onboarding.