docs-standards

Apply Microsoft Style Guide rules and squad conventions to technical documentation.

Updated Apr 10, 2026

Search Tags:#documentation #writing #standards #guidelines #style-guide #scannability

Ready to run

npx skills add https://github.com/chdaly/eshop --skill docs-standards-chdaly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/docs-standards
Command: npx skills add https://github.com/chdaly/eshop --skill docs-standards-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad documentation often lacks consistency, making onboarding and knowledge transfer harder. This skill defines and enforces a common Microsoft Style Guide with squad-specific conventions to improve clarity and trust in docs.

Core Features & Use Cases

Enforces style rules (sentence case headings, active voice, present tense) and squad-specific formatting patterns.
Encourages scannability with concise paragraphs, bullets, and cross-references at the end of pages.
Use Case: Teams publish internal guides, templates, and onboarding materials that stay consistent over time.

Quick Start

Align your draft docs with the Microsoft Style Guide and squad conventions to start producing consistent, ready-to-publish content.

Frequently Asked Questions about docs-standards

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

FAQPage Schema

How do I standardize squad documentation to improve onboarding and knowledge transfer?▼

This skill standardizes squad documentation by applying Microsoft Style Guide rules and squad-specific conventions to enforce consistency. It improves scannability using concise paragraphs, structured headings, and bullets, making onboarding materials clearer and easier to maintain.

What are the Microsoft Style Guide rules for formatting technical guides?▼

Microsoft Style Guide rules for technical guides enforce sentence case headings, active voice, and present tense. They also require formatting patterns that encourage scannability, such as concise paragraphs, bullet points, and cross-references at the end of pages.

How do I enforce consistent writing standards when publishing internal guides?▼

To enforce consistent writing standards when publishing internal guides, apply frontmatter-based discovery and structured formatting rules. This ensures all team guides, templates, and onboarding materials satisfy style requirements and stay consistent over time.

Does this documentation style guide require any specific technical dependencies?▼

No specific technical dependencies are required to apply this documentation style guide. It operates independently to review drafts and align content with Microsoft Style Guide rules and squad-specific conventions for ready-to-publish technical docs.

What is the best way to improve scannability in squad onboarding materials?▼

The best way to improve scannability in squad onboarding materials is to use concise paragraphs, bullet points, and structured headings. Applying these formatting rules ensures technical docs remain clear and easy to scan for new team members.