content-source-router

What problem does it solve?

When a static site needs to fetch and render content coming from multiple places, routing the request to the correct source can be error-prone and lead to missing pages or wrong content being served.

Core Features & Use Cases

• Multi-source dispatch: Routes requests to the correct backend for local markdown, local MDX (React components), or headless-CMS-synced content based on explicit hints, path prefixes, and file extensions.
• No silent fallbacks: Returns a structured unknown-source result when nothing matches, forcing callers to handle gaps explicitly instead of guessing.
• Precedence rules that prevent ambiguity: Enforces a strict priority order so explicit source hints override path/extension detection, and path detection beats extension detection.

Quick Start

Use the content-source-router skill when your site receives a request to render content without naming a specific source, and let it select between local markdown, local MDX, or CMS-synced content based on the request details.