pdf-export
PDF report generation for client-facing deliverables
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- pdf-export
- owner
- core-engine-dev
- scope
- co-price
- status
- active
- version
- 1.1.0
- description
- PDF report generation for client-facing deliverables
- last_reviewed
- 1787616000000
- prerequisites
- statement data rendered; human approval for client-facing artifacts
- catalog-parity
- skip
03 SKILL.md 正文
PDF Export Skill (v1.1 — print-pipeline approach)
What changed in v1.1
The former guidance recommended jspdf/pdfmake. Superseded: v10.1 H-3 adopted
the browser print pipeline as the single PDF path —
SimulationDashboardheader exposes a Print action (window.print()).- Chrome (header/sidebar) is removed via Tailwind
print:hiddenutilities. src/app/globals.csscarries an@media printblock forcing a white background and visible overflow so multi-page financial tables paginate cleanly.
Rationale (recorded per ADR culture)
| Criterion | jsPDF/pdfmake | Browser print pipeline |
|---|---|---|
| Runtime dependencies | +1 heavy lib | 0 |
| Text selectability | manual | inherent |
| Table pagination | manual | native |
| Maintenance | custom layout code | CSS only |
Procedure
- Verify the target view renders complete data (no virtualized truncation).
- Trigger print (button or Ctrl/Cmd+P) → destination "Save as PDF".
- For client-facing deliverables, run through the engagement-director approval gate BEFORE sending out (disclaimers + ledger-cited figures check).
Boundaries
- Do not reintroduce canvas-raster or heavyweight PDF libs without PM approval.
- Programmatic server-side PDF generation (headless) remains OUT of scope; if a future requirement demands it, open an ADR first.
Context
See docs/co-price.context.md for project context and the consulting engagement lifecycle.
When to Use
- When a co-price task requires PDF report generation for client-facing deliverables within the engagement lifecycle.
Execution Steps
- Receive dispatch from PM with task parameters and document anchors.
- Execute the skill procedure against the artifacts named in the task scope.
- Report results to the dispatching agent with evidence links.
Output Format
Structured markdown report delivered to the dispatching agent, citing document anchors (for example [Ref: biz_logic.*]) where applicable.
Related Skills
- Owner agent:
core-engine-dev. Seevariant.jsonskills registry for the full co-price skill set.
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.