skills.rest
jonnymuir
jonnymuirCOMMUNITY
Explore all skills by this author →
Website𝕏@jonnymooGitHub

docs-standards

Validate documentation against the Microsoft Style Guide and team formatting conventions.

1|Updated Dec 23, 2025
Search Tags:#documentation#technical writing#formatting#style guide#standards
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill docs-standards-jonnymuir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/docs-standards
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill docs-standards-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality, consistent documentation across a team by enforcing specific style guides and structural patterns.

Core Features & Use Cases

  • Style Enforcement: Applies Microsoft Style Guide rules to ensure professional, active-voice, and scannable content.
  • Structural Consistency: Standardizes the layout of feature and scenario pages to improve user discoverability.
  • Use Case: Use this Skill when drafting new technical documentation to ensure your headings, tone, and formatting align with squad-wide conventions before publishing.

Quick Start

Ask the docs-standards skill to review the current document for compliance with the Microsoft Style Guide and squad patterns.

Frequently Asked Questions about docs-standards

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

FAQPage Schema
How do I enforce documentation consistency across a technical writing team?▼

You can enforce documentation consistency by validating content against established style guides and team-specific formatting conventions, ensuring standardized layouts, active voice, and proper structural patterns for technical writing workflows.

What is the Microsoft Style Guide used for in technical writing?▼

The Microsoft Style Guide is used to enforce professional, active-voice, and scannable content standards in technical writing, ensuring your headings, tone, and formatting align with squad-wide conventions before publishing.

How do I check a document for style guide compliance before a pull request review?▼

To check style guide compliance, validate your document against the Microsoft Style Guide and team-specific formatting conventions, ensuring adherence to established patterns for headings, voice, tense, and structural layout before submitting a pull request.

Can I standardize the structural layout of feature and scenario pages?▼

Yes, you can standardize the structural layout of feature and scenario pages by enforcing specific team conventions, which standardizes the layout to improve user discoverability and maintain consistent formatting across documentation.

Does this documentation validation work for ongoing maintenance tasks?▼

Yes, documentation validation applies to ongoing maintenance tasks, pull request reviews, and new technical writing workflows, requiring adherence to established patterns for headings, voice, tense, and structural layout to maintain quality.

Why does my technical documentation fail formatting consistency checks?▼

Technical documentation fails formatting consistency checks when content does not adhere to established patterns for headings, voice, tense, and structural layout defined by the Microsoft Style Guide and team-specific formatting conventions.

Related Skills

Explore More Content & Communication Skills→
HaykTarkhanyanHaykTarkhanyan

markdown-mermaid-writing

Embed Mermaid diagrams in Markdown for version-controlled technical documentation.

Community
Advanced
cwidacwida
8

write-docs

Write and review LPTS documentation using Snowflake and DuckDB style guidelines.

Official
Intermediate
metabasemetabase
48.6k

clojure-review

Review Clojure and ClojureScript diffs for Metabase coding standard violations.

Official
Advanced
QuintenpsQuintenps

docs-standards

Enforce Microsoft Style Guide and squad conventions in documentation commits.

Community
Basic