recipe-custom-dashboardlisted

# Recipe: Custom Dashboard (Disposable, Verified-Data) Instead of a fixed dashboard product, write a **small program per question**: fetch verified data through the FlowLeap CLI, compute every number in code, and emit one self-contained HTML file. This skill owns **presentation craft only** — the *analysis* (which query, which corpus, how to read the result) lives in the analytical recipes. Do the analysis there first, then render here. Vocabulary (agent-v2 `CONTEXT.md`): **Portfolio Analytics** = grounded PATSTAT aggregates for one harmonized applicant (`data_edition` stamped). **Topic Analytics** = full-corpus filing analytics over the quarterly Google-Patents slice (corpus-slice stamped). **Verified-Data Contract** = every figure on the page is interpolated from a computed variable, never typed by the model. ## Mandatory rules These are product decisions, not style preferences. A dashboard that breaks one of them is wrong even if it looks right. 1. **Numbers only from code — including prose.** Every value in the HTML (chart, table, and every narrative sentence) is interpolated from a computed variable. The model never literal-types a figure. Use the template's `renderNarrative(computed)` helper for sentences; embed backend-authored `summary` strings **verbatim** as canonical captions. In chat, the dashboard is the source of record: the script prints a summary block — quote its numbers, never re-type them from memory. 2. **Data via CLI subprocess only.**