skills.rest
lbouriez
lbouriezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

docs-standards

Enforce Microsoft Style Guide consistency across Squad documentation pages.

Updated Mar 27, 2026
Search Tags:#documentation#writing#consistency#standards#guidelines#style-guide#squad
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill docs-standards-lbouriez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/docs-standards
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill docs-standards-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation teams struggle with inconsistent writing styles and scattered patterns across Squad pages, leading to confusion and poor discoverability.

Core Features & Use Cases

  • Enforces Microsoft Style Guide rules.
  • Provides Squad-specific formatting patterns.
  • Enables reliable cross-reference linking and consistent navigation.
  • Use Case: When creating or updating Squad docs, apply the standard to ensure scannability and brand consistency.

Quick Start

Review the Squad documentation and apply the Microsoft Style Guide rules to new and existing pages.

Frequently Asked Questions about docs-standards

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

FAQPage Schema
How do I standardize documentation formatting across multiple pages?▼

To standardize documentation formatting, apply consistent style guidelines like the Microsoft Style Guide across all pages. This enforces scannable content, reliable cross-references, and structured layouts including titles, callouts, and bottom references.

What is the best way to enforce a style guide for technical writing consistency?▼

The best way to enforce technical writing consistency is to apply a standardized style guide, such as the Microsoft Style Guide, to every documentation page. This ensures uniform voice, structured layouts, and reliable cross-reference linking.

Do I need YAML frontmatter for documentation pages using Microsoft style?▼

Yes, you need YAML frontmatter containing name and description fields for documentation pages using Microsoft style. This required metadata ensures proper page identification and supports consistent navigation across the documentation set.

How do I structure a documentation page for scannability and brand consistency?▼

To structure a documentation page for scannability, use a prescribed layout including a title, a warning or callout, a Try this prompt, an overview, content sections, and bottom references. This ensures brand consistency and improves reader discoverability.

Why does scattered documentation writing cause poor discoverability?▼

Scattered documentation writing causes poor discoverability because inconsistent styles and unstructured page layouts confuse readers and break cross-references. Enforcing a uniform style guide resolves this by standardizing formatting and navigation patterns.

Can I apply Microsoft Style Guide rules to existing documentation pages?▼

Yes, you can apply Microsoft Style Guide rules to existing documentation pages. Reviewing and updating current content with these standards ensures that all pages maintain scannability, consistent formatting, and reliable cross-references.

Related Skills

Explore More Content & Communication Skills→
nicholasgriffintnnicholasgriffintn
2

add-skill

Create and validate SKILL.md files with YAML frontmatter for OpenCode or Claude.

Community
Basic
sytonesytone
2

docs-standards

Apply Microsoft Style Guide rules and squad formatting patterns to documentation.

Community
Intermediate
jperezdelrealjperezdelreal

docs-standards

Standardize squad documentation against Microsoft style and squad-specific patterns.

Community
Intermediate
acmelemeacmeleme

docs-standards

Apply Microsoft Style Guide patterns to squad documentation for consistency.

Official
Basic