What problem does it solve?
Fumadocs projects fail to scaffold, route, index, and render documentation correctly when the adapter, loader configuration, UI layout wiring, or MDX pipeline details are inconsistent, leading to broken sidebars, missing search, stale content, or build-time errors.
Core Features & Use Cases
- Fumadocs framework guidance: Choose the correct Fumadocs stack components (fumadocs-core, fumadocs-mdx, fumadocs-ui) and configure them for your React framework adapter.
- Deterministic setup and wiring: Map user intent to the right task class (setup, routing/page tree, MDX pipeline, UI layouts/components, search/i18n, integrations, debugging).
- Practical operational procedures: Validate configuration conflicts, regenerate .source outputs, and debug common failure modes such as Tailwind version mismatch and provider import path issues.
- Use case: When you need to migrate an existing docs app to Fumadocs or fix a broken sidebar/search UI after changing loader or layouts, follow the skill’s staged checklist and reference pitfall catalog to restore correctness quickly.
Quick Start
Use the fumadocs skill to diagnose why your docs sidebar is blank and your search dialog does not return results after configuring the loader and layouts.