docs-standards

Enforce Microsoft Style Guide and Squad documentation patterns across project docs.

Updated Aug 27, 2026

Search Tags:#documentation #consistency #structure #style-guide #scannability #squad-patterns

Ready to run

npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill docs-standards-carlossardo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/docs-standards
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill docs-standards-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad projects often suffer from inconsistent documentation styles, leading to reduced discoverability and onboarding friction. This Skill codifies Microsoft Style Guide conventions combined with Squad-specific patterns to ensure docs are predictable, scannable, and easy to maintain.

Core Features & Use Cases

Enforces Microsoft Style Guide rules (sentence-case headings, active voice, second person, present tense, no ampersands in prose) across documentation.
Applies Squad-specific formatting patterns (scannability-first layout, "Try this" prompts, experimental warnings, cross-references at the bottom) to improve readability and consistency.
Provides a reusable documentation blueprint that covers typical pages (title, warning, overview, content sections) to accelerate authoring and review.

Quick Start

Review your project docs and apply the Microsoft Style Guide + Squad patterns to convert them into consistent, scannable, and maintainable documentation.

Frequently Asked Questions about docs-standards

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

FAQPage Schema

How do I enforce consistent documentation standards across multiple project docs?▼

To enforce consistent documentation standards, apply the Microsoft Style Guide rules alongside Squad-specific formatting patterns. This ensures sentence-case headings, active voice, and scannable layouts across all product pages, guides, and references.

What is the Microsoft Style Guide for technical documentation?▼

The Microsoft Style Guide for technical documentation defines writing conventions like sentence-case headings, active voice, second person, present tense, and no ampersands in prose. Applying these rules makes your docs predictable and easy to maintain.

How do I structure a SKILL.md file to improve onboarding and discoverability?▼

Structure a SKILL.md file by enforcing frontmatter presence with name and description, plus a three-section description pattern. Add scannability-first layouts, experimental warnings, and cross-references at the bottom to improve onboarding.

Does this documentation style guide work for Squad project references and scenarios?▼

Yes, this documentation style guide works for Squad project references and scenarios. It applies standardized patterns to all product docs pages, ensuring naming and structure conformance to improve discoverability across your project.

What's the best way to make technical documentation scannable and easy to maintain?▼

The best way to make technical documentation scannable is to apply a scannability-first layout using Squad-specific patterns. Include "Try this" prompts, experimental warnings, and cross-references at the bottom to accelerate authoring and review.

Why do my Squad project docs suffer from onboarding friction?▼

Squad project docs suffer from onboarding friction due to inconsistent documentation styles. Codifying Microsoft Style Guide conventions combined with Squad-specific patterns ensures docs are predictable, scannable, and easy to maintain.