full-styleguide-check

Validate Markdown/MDX documentation against the complete HashiCorp style guide.

78|252|Updated Feb 7, 2024
One-click install
npx skills add https://github.com/hashicorp/web-unified-docs --skill full-styleguide-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-styleguide-check
Source: https://github.com/hashicorp/web-unified-docs/tree/main/content/well-architected-framework/docs/.claude/skills/full-styleguide-check
Command: npx skills add https://github.com/hashicorp/web-unified-docs --skill full-styleguide-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates documentation against the complete HashiCorp style guide to ensure publication-ready content.

Core Features & Use Cases

  • Comprehensive validation against the full style guide, covering tone, structure, formatting, links, and terminology across Markdown/MDX content.
  • Publication readiness checks that help editors prepare docs for release by surfacing style violations and providing actionable guidance.
  • Use Case: Before submitting a page for approval, run this check to enforce consistency with style guidelines and reduce back-and-forth edits.

Quick Start

Run the style guide check on your docs folder: /full-styleguide-check docs/**/*.mdx

Frequently Asked Questions about full-styleguide-check

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

FAQPage Schema
How do I validate markdown documentation against a style guide before publication?

Validate markdown documentation against a style guide by running a pre-publication check that surfaces tone, structure, formatting, link, and terminology issues across Markdown and MDX files to ensure publication-ready content.

What is pre-publication style guide linting for MDX files?

Pre-publication style guide linting for MDX files is a validation process that checks documentation content against comprehensive style rules to enforce consistency and reduce back-and-forth edits before page approval.

Can I automatically fix style guide violations in documentation?

You can address style guide violations in documentation using potential auto-fix capabilities provided in the validation report, which offers actionable guidance for correcting tone, formatting, and terminology issues.

Does the HashiCorp documentation style guide check work with MDX files?

The HashiCorp documentation style guide check works with both Markdown and MDX files across the docs site, applying comprehensive validation rules to ensure content meets publication readiness standards.

What's the best way to enforce terminology consistency in technical docs?

The best way to enforce terminology consistency in technical docs is to run a comprehensive style guide validation check that surfaces terminology issues alongside tone and structure violations during pre-publication reviews.

Why do I need a style guide reference to check documentation quality?

You need a complete style guide reference to check documentation quality because the validation process requires the full style guide ruleset to accurately surface violations and provide actionable guidance for publication-ready content.