--- name: richdoc description: This skill should be used when the user asks to "write a research report", "create a plan document for review", "produce a polished design doc", "draft a comparison sheet", "generate a richdoc", "make a one-pager", "write a status report", "produce an executive summary", "create a decision document", "build a dashboard page", or any other rich HTML deliverable intended for human review in a browser. Authors plain .html files using a small fixed vocabulary of rd-* web components for layout and rich blocks. Includes a CLI for scaffolding, asset installation, schema introspection, and validation. --- # richdoc richdoc is for **AI-authored, human-read HTML documents**. The agent writes a normal `.html` file using a closed vocabulary of `rd-*` custom elements. Two shipped assets (`richdoc.css`, `richdoc.js`) give every component its editorial look and behavior. No build step on the consumer side; the file opens in any browser, with or without a server. ## When to use richdoc Plans, research reports, design docs, status one-pagers, decision memos, comparisons, postmortems, dashboards — anything where the reader is a person in a browser. Use markdown only when the renderer might be anything else (GitHub, chat, CLI). Anywhere else, richdoc is the better default. ## Authoring rules When writing a richdoc, the agent **must**: 1. Produce a complete HTML5 document with exactly one `` directly inside ``. Link `richdoc.css` and `richdoc.js` from ``. 2. Use **only** the `rd-*` tags listed below. Inventing new ones causes lint errors and renders as empty boxes. 3. For prose, use plain semantic HTML — `

`, `