domo-proposal-pdf-renderer

Render, build, generate, produce, or export a Domo client proposal as a polished, signature-quality PDF (.pdf) suitable for offline review, enterprise procurement workflows, formal RFP responses, and any moment that calls for a flat, brand-clean artifact a client can read on a plane, forward to legal, or print on letterhead. Use this skill when the browser-print PDF produced by the **Export to PDF** button inside the interactive proposal isn't polished enough — when you need to suppress the browser's URL/timestamp chrome, add a Domo-branded footer with page numbers, and guarantee identical output regardless of which browser the recipient happens to open the file in. This skill is the polished-PDF companion to `domo-interactive-proposal-builder`. Both consume the same source-of-truth engagement content JSON — two outputs from one payload: 1. `domo-interactive-proposal-builder` → interactive HTML proposal (review) 2. `domo-proposal-pdf-renderer` → polished offline PDF (RFP/procurement) Numbers, hour ranges, ROI math, solution shape, deliverable detail — identical across the two formats because they both derive from the same JSON. MANDATORY TRIGGERS: render proposal pdf, generate proposal pdf, polished pdf, bulletproof pdf, signature-quality pdf, rfp pdf, procurement pdf, offline proposal, headless pdf, server-side pdf, playwright pdf, domo-branded pdf, proposal pdf for enterprise, proposal pdf for legal review, build the pdf for, generate the pdf for, render the pdf for. The output is a PDF rendered by headless Chromium against the same `template.html` that the interactive proposal renders to. Every panel is flattened, every solution card is force-expanded, every deliverable's detail blocks (What it includes / Who it's for / Outcome & value) are visible. The Pacific Drift palette is preserved via `print-color-adjust: exact`. No browser-imposed header. A Domo-branded footer with page numbers is rendered by Playwright's footer template (not the page itself, so it stays fixed at the bottom of every page regardless of content flow). Document metadata (Title, Author, Subject) is set so the PDF reads cleanly in document managers and email previews. Do NOT use this skill for: the casual self-service PDF most clients can produce by clicking the Export to PDF button inside the interactive proposal (that's already wired into `domo-interactive-proposal-builder` and is sufficient for ~95% of clients), Discovery Briefs (use `domo-discovery-brief`), or any artifact that isn't a Domo client proposal rendered from the shared engagement content JSON.