Interactive Doc

Pair an Obsidian-friendly markdown source with a self-contained HTML companion. The .md is the canonical source of truth — token-efficient, wiki-linkable, what other agents and tools consume. The HTML is the experience for humans who want to read it instead of grep it. Same content, two surfaces.

Design tokens do not apply here. These docs are standalone, handmade artifacts that live in a repo or vault, not product UI governed by a project's design-token system — so design-token-guard / class-extraction-guard are out of scope. The HTML's own theming uses CSS variables in :root (see House style below); that local convention is the only "token" layer, and you should not try to wire these docs into an application's token pipeline or framework CSS.

The two workflows

This skill handles two distinct jobs. Identify which one applies before doing anything else.

Workflow A — Render existing research

The user has an existing markdown file (often deep-research notes, an Obsidian vault page, or a long analysis) and wants an HTML companion. The .md is canonical and read-only by default — your job is to read it carefully and produce HTML that respects what's there. You may, however, offer to suggest edits to the .md if rendering reveals genuine gaps or contradictions; only make those edits if the user says yes.