research-best-practiceslisted

# Research Best Practices Produce a benchmark-backed research artifact, not just chat. The goal is to answer: what strong pages do, why it works, and how the user should adapt it. ## Output Behavior Always write: - `.webanatomy/research-best-practices/{topic}-{YYYY-MM-DD}/report.md` - `.webanatomy/research-best-practices/{topic}-{YYYY-MM-DD}/report.html` - `.webanatomy/research-best-practices/{topic}-{YYYY-MM-DD}/references/` The HTML report is the primary visual output. Chat is only a short summary and pointer to the saved files. If the environment cannot write files, explain the blocker and provide the report inline. ## Deterministic Report Renderer When file access is available, do not hand-write the final HTML. Write structured report data first: - `.webanatomy/research-best-practices/{topic}-{YYYY-MM-DD}/report-data.json` Then run the shared renderer from this skill pack: ```bash node <skill-dir>/scripts/render-report.mjs --input=.webanatomy/research-best-practices/{topic}-{YYYY-MM-DD}/report-data.json ``` Resolve `<skill-dir>` relative to this `SKILL.md`. The renderer validates the report data, downloads every `screenshotUrl` into `references/`, writes `report.md`, writes `report.html`, and renders "screenshot unavailable" when no screenshot exists. Use this report-data shape: - `title`, `summary`, optional `eyebrow`, `subtitle`, `target` - `references`: `{ "title": "...", "company": "...", "section": "...", "sourceUrl": "...", "screenshotUrl": "...", "cap