markdown-html-orchestrator

Topics in the source

• Markdown → HTML — Domain Orchestrator
• When to invoke
• Pre-flight gates (hard refusals)
• Routing logic (deterministic)
• Signal table
• Workflow
• Step 1 — Confirm onboarding
• Step 2 — Classify the input

Thariq Shihipar's argument (Claude Code HTML output essay, Medium 2026): markdown collapses past 100 lines for agent-generated artifacts. Long specs, code reviews, and architecture explainers lose density, hierarchy, and lightweight interaction the moment they exceed a screen of text. HTML restores all three — single-file, browser-native, shareable. This orchestrator forks context, classifies the input markdown deterministically, routes to the right converter sub-skill, and returns a digest with the output path. Heavy intake (full markdown bodies, diffs, slide decks) stays in the forked context. Domain status (complete): all five skills are live — orchestrator + design-system (onboarding + shared brand tokens) + the three converter sub-skills (md-document, md-review, md-slides). Always route conversions to the shipped converter's scripts; never hand-render HTML inline. | Symptom | Sub-skill | |---|---| | "Convert this RFC / spec / report / explainer to HTML" — long-form doc | md-document | | "Turn this PR writeup / code review into HTML" — markdown with diff blocks | md-review | | "Make a slide deck from this markdown" — --- boundaries or H1 cadence | md-slides | 1. Below the 100-l

This is an excerpt. Refer to the complete source and its current requirements.