What problem does it solve? Adding a printed form (invoice, act, receipt) to a model normally tempts developers to write PDF generation, template parsing, or client-side rendering code. This Skill shows how to supply only data and a template while the core @altera/server print runtime owns all rendering, eliminating duplicated rendering logic and formatting drift. ## Core Features & Use Cases - Four-artifact workflow: Create the SQL data command (<model>_print_data), the schemaVersion: 2 template file, the manifest prints block, and the print button on the edit form. - Template authoring guidance: Absolute vs flow placement, page breaks, repeat blocks for per-record blanks, char-cells and rotated text for regulated Ukrainian forms, conditional visibleWhen blocks, and amount-in-words formatting. - Layout verification: Probe templates with renderPrintPdfWithLayout and text measurers to catch overflow before printing. - Use Case: Add a printable invoice (накладна) to an existing model — write the SQL projection returning formatted strings, declare the template with header coordinates and flow tables, register via deno task sql:registry && sql:assemble && sql:publish, and wire the print button that opens the PDF in a new tab. ## Quick Start Ask the agent to add a printed invoice form to the invoice model with header fields, a lines table, totals, and signature blocks using the core print runtime.
