dev-doc

Audit Mintlify .mdx files and enforce Blitzy formatting, structure, and component rules.

1|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/montymi/claude-config --skill dev-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-doc
Source: https://github.com/montymi/claude-config/tree/main/skills/dev-doc
Command: npx skills add https://github.com/montymi/claude-config --skill dev-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mintlify documentation pages often deviate from Blitzy conventions, leading to inconsistent style and user experience.

Core Features & Use Cases

  • Audit target Mintlify .mdx files for style conformance against Blitzy guidelines.
  • Restructure formatting to align with Mintlify components, headers, and jump links.
  • Apply consistent patterns across large doc projects, including card navigation and callouts.

Quick Start

Provide the path to the target .mdx file to audit and apply style fixes.

Frequently Asked Questions about dev-doc

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

FAQPage Schema
How do I standardize Mintlify documentation to enforce consistent formatting?

To standardize Mintlify documentation, you audit target .mdx files and apply style fixes for headers, jump links, components, and callouts to ensure consistent formatting across your project.

What are common Mintlify style issues with headers and callouts?

Common Mintlify style issues involve non-compliant header structures, missing jump links, inconsistent callout usage, and incorrect component formatting that deviate from standard documentation conventions.

Can I apply Blitzy style rules across a large Markdown project?

Yes, you can apply Blitzy style rules across a large Markdown project by auditing and restructuring formatting to align Mintlify components, headers, and card navigation throughout the entire documentation corpus.

How do I audit .mdx files for frontmatter and section structure compliance?

You audit .mdx files by checking for frontmatter presence, validating section structures, enforcing component usage rules, and verifying consistent styling to ensure full compliance with documentation guidelines.

What is the best way to fix inconsistent Mintlify component usage?

The best way to fix inconsistent Mintlify component usage is to run an automated audit that restructures formatting and applies open rules for headers, card navigation, and callouts across your documentation.

Does this standardization approach work for single-file docs?

Yes, this standardization approach works for both single-file docs and large Markdown projects, enforcing formatting, structure, and component usage rules across individual Mintlify pages and broader documentation corpora.