docusaurus-conventions

Enforce Docusaurus file naming, frontmatter, and MDX conventions for reliable builds.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio --skill docusaurus-conventions-ayeshakhalid192007-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docusaurus-conventions
Source: https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio/tree/main/.claude/skills/docusaurus-conventions
Command: npx skills add https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio --skill docusaurus-conventions-ayeshakhalid192007-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Docusaurus content often fails to build due to naming, MDX syntax, and link pitfalls. This skill codifies safe conventions for RoboLearn docs to ensure builds succeed on the first try.

Core Features & Use Cases

  • Enforces correct file naming patterns (e.g., README.md for module index, NN-descriptive-name.md for lessons) to ensure deterministic routing and ordering.
  • Validates safe MDX usage by avoiding problematic characters and Mermaid diagrams; provides guidelines for internal linking and ID uniqueness.
  • Provides recovery and debugging patterns to fix common build errors such as duplicate IDs and MDX syntax issues, improving author productivity.

Quick Start

To apply these conventions, update lesson and module files to follow the documented naming patterns and frontmatter requirements, then run a local build to verify a clean output.

Frequently Asked Questions about docusaurus-conventions

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

FAQPage Schema
Why does my Docusaurus documentation build fail on the first try?

Docusaurus builds often fail due to incorrect file naming, invalid MDX syntax, duplicate frontmatter IDs, or broken internal links. Applying strict content authoring conventions ensures deterministic routing and a clean build output.

How do I fix MDX syntax issues in Docusaurus content?

To fix MDX syntax issues, avoid problematic characters and do not use Mermaid diagrams in your MDX files. Following documented MDX safety rules and recovery patterns resolves common build errors and improves author productivity.

What file naming conventions ensure deterministic routing in Docusaurus?

Use README.md for module index files and NN-descriptive-name.md for lessons to ensure deterministic routing and ordering. Strict naming patterns prevent routing conflicts and help your documentation build reliably.

Does Docusaurus support Mermaid diagrams in MDX files?

Docusaurus does not safely support Mermaid diagrams in MDX files under these conventions. To ensure build stability, avoid problematic characters and Mermaid, relying instead on standard non-Mermaid diagram usage.

How do I resolve duplicate frontmatter ID errors during a Docusaurus build?

Resolve duplicate frontmatter ID errors by enforcing frontmatter structure and ID uniqueness across modules and lessons. Documented recovery patterns provide debugging steps to fix these common build errors quickly.