Apply Microsoft Style Guide rules and squad formatting patterns to documentation.
npx skills add https://github.com/sytone/botnexus --skill docs-standards-sytone
Please help me install this Agent Skill. Skill: docs-standards Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/docs-standards Command: npx skills add https://github.com/sytone/botnexus --skill docs-standards-sytone
Squad teams often struggle with inconsistent documentation across guides, references, and tutorials, leading to confusion and poor discoverability. This Skill enforces a Microsoft Style Guide baseline and squad-specific conventions to ensure clarity, consistency, and maintainability.
Apply the Microsoft Style Guide and Squad formatting patterns to new documentation pages.
High-intent search queries and answers about installing and using this skill.
To enforce consistent documentation structure, apply Microsoft Style Guide rules to align sentence-case headings, active voice, and present tense across all docs. This standardizes tone and improves content discoverability for squad teams.
The correct heading hierarchy for reference pages starts with a Title (H1), followed by a warning or callout, a Try this section, an Overview, a horizontal rule, and then content sections using H2. This structure ensures scannability and consistent cross-references.
To review and format documentation for scannability and warnings, apply squad-specific formatting patterns that structure content with practical prompts and explicit warnings for experimental features. This maintains readability and alerts users to unstable functionality.
Yes, editing documentation requires updating test synchronization expectations. When documentation pages are added or modified, you must synchronize test expectations to ensure the tests align with the updated structure and content rules defined in the docs.
A limitation of relying on a style guide baseline for cross-references is that it primarily enforces structural consistency and tone rather than validating the actual technical accuracy of the linked targets. It ensures formatting alignment but requires manual verification for link integrity.
AshleyHollisAutomate documentation formatting to enforce Microsoft Style Guide rules.
Ahnd6474Convert acceptance criteria into validated JSON test plans and Playwright spec files.
wade56754Audit ASDD documentation files for accuracy and propose P0/P1/P2 fixes.
QuintenpsEnforce Microsoft Style Guide and squad conventions in documentation commits.
