skills.rest
jperezdelreal
jperezdelrealCOMMUNITY
Explore all skills by this author →
GitHub

docs-standards

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

Updated Apr 6, 2026
Search Tags:#documentation#style-guide#writing-guidelines#content-quality#docs-standards#squad-patterns#microsoft-style
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill docs-standards-jperezdelreal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/docs-standards
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill docs-standards-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad documentation often suffers from inconsistency and poor discoverability. This Skill enforces the Microsoft Style Guide plus squad-specific conventions to produce uniform, readable docs across the team.

Core Features & Use Cases

  • Enforces sentence-case headings, active voice, present tense, and avoidance of ampersands in prose.
  • Provides squad-oriented formatting patterns to improve scannability, readability, and quick reference.
  • Supports cross-references at the bottom of docs to link related pages and reduce duplication.

Quick Start

Start by applying the docs-standards guidelines to your next squad documentation draft and review it against the described rules.

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 enforce Microsoft style guidelines?▼

Standardize squad documentation by enforcing sentence-case headings, active voice, present tense, and specific frontmatter rules. This ensures consistency across draft creation, review, and publishing workflows while complying with squad-specific patterns and Microsoft style.

What is the best way to improve readability and scannability across project docs?▼

Improve project docs readability by applying squad-oriented formatting patterns that enforce consistent tone, tense, and heading conventions. Standardizing documentation structure reduces duplication and makes cross-referenced pages easier to scan.

How do I enforce heading conventions and frontmatter requirements during a docs review?▼

Enforce heading conventions and frontmatter requirements by reviewing draft documentation against established squad patterns. Check for sentence-case headings, active voice, and proper cross-references at the bottom of docs to ensure full compliance.

Can I use squad-specific patterns to standardize documentation without external dependencies?▼

Yes, you can standardize documentation using squad-specific patterns without external dependencies. The guidelines apply directly to draft creation and review workflows, enforcing formatting rules and content structure independently.

Why should documentation avoid ampersands in prose and use cross-references?▼

Documentation should avoid ampersands in prose and use bottom cross-references to maintain a professional Microsoft style tone. This practice reduces content duplication, improves scannability, and properly links related pages across the squad.

Related Skills

Explore More Content & Communication Skills→
bahayonghangbahayonghang
3

kb-compile

Compile markdown captures into draft knowledge with summaries and indices.

Community
Intermediate
CoachSteffCoachSteff
1

knowledgebase

Organize institutional knowledge with categories, tags, versioning, and full-text search.

Community
Advanced
channgchanng
20

docsify

Generate static documentation websites from markdown files with sidebar navigation.

Community
Basic
barichterbarichter

docs-standards

Validate documentation against Microsoft Style Guide and Squad-specific conventions.

Community
Intermediate