report-designer

# Report Designer The polish pass: takes an existing document — a draft, a published ReportRoom page, or pasted HTML — and raises it to the design bar without touching the substance. Follow the shared flow in the root `SKILL.md` (`get_design_system` is the source of truth; lint before republish). ## When to use - "Make it beautiful / less plain / more professional" - A page published earlier needs a visual upgrade - Another skill's output was approved on content but the user wants another design pass ## What a design pass covers Work through these in order; each is a check, not an automatic rewrite: 1. **Hierarchy** — is the most important thing visually the biggest thing? Title states the conclusion; section headings scannable as a story on their own. 2. **Typography & rhythm** — design-system type scale applied; line lengths readable; whitespace between sections doing the separating (not horizontal rules everywhere). 3. **Data presentation** — numbers that compare become charts; tables get aligned columns and clear headers; every chart labeled well enough to survive being screenshot alone. 4. **Color & emphasis** — design-system palette only; emphasis (callouts, highlights) reserved for the few things that deserve it. If everything is highlighted, nothing is. 5. **Dark mode & responsiveness** — verify both render correctly, especially charts and images. 6. **Link presentation** — title/description/OG image make the page unfurl well when shared in Slack/LinkedIn/iMess...