What problem does it solve? Building a Markdown/MDX content pipeline requires choosing the right compiler, ordering remark/rehype plugins correctly, configuring syntax highlighting, embedding math and diagrams, and sanitizing user content against XSS. Getting any of these wrong produces broken rendering, silent plugin failures, or security holes. ## Core Features & Use Cases - Compiler Selection: Decision matrix covering @next/mdx, Velite, next-mdx-remote v6, Contentlayer2, and direct @mdx-js/mdx usage for Next.js, Astro, Vite, and Node.js projects. - Plugin Pipeline Design: Canonical remark/rehype plugin ordering, GFM, frontmatter, directives, custom plugin authoring with unist-util-visit, and TypeScript typing. - Highlighting, Math, and Diagrams: Shiki v4, rehype-pretty-code, expressive-code, starry-night, KaTeX math, and Mermaid embedding strategies. - Sanitization and Testing: rehype-sanitize schema design, DOMPurify client-side fallback, and vitest snapshot/XSS fixture testing. - Use Case: When building a Next.js 15 blog with typed frontmatter, math equations, and highlighted code blocks, follow the Velite example to wire remark-gfm, remark-math, rehype-katex, and rehype-pretty-code in the correct order. ## Quick Start Ask the assistant to design a Markdown/MDX processing pipeline for your project, specifying your framework, content source, and whether the content is user-authored.
