running MuseScore Studio 4.4.2+ (or experimentally Dorico) via WebSocket bridge.
- **Rendering** — `render_score` exports PDF, PNG, MIDI, audio or MusicXML through the MuseScore command line.
Follow the code standards
workstream bids or consulting delivery programmes, route control
operations through `skills/product-business/consulting-delivery-control-room`.
- Before promising Word, PDF, Excel, workbook, scoring matrix, application
register, budget, or dashboard outputs, route through
`skills/product-business/document-spreadsheet-tooling-readiness`.
- For high
install:export` + ffmpeg) when the user explicitly asks for headless screenshots, MP4/GIF, PDF, or PPTX.
If the user's request is **not** a visual design deliverable, exit this skill cleanly
diff banners, word-level marks, search highlights) must hide behind `html.mindle-print-mode` so PDF export reads clean.
## Working with the subsystems
### Annotations
- The selection bridge is debounced 150ms
Core project guidelines for the pdfvision codebase. Apply these rules when working on any code, documentation, or configuration files within the pdfvision project.
design |
| `get_variables` | Read design tokens / variables |
| `export_nodes` | Export nodes to image / PDF files |
| `export_html` | Export nodes to HTML (Tailwind or CSS) |
There is no `open_document` tool
redirect and scheme bypasses, parsers that fetch on their own (XXE, SVG, HTML-to-PDF), cloud metadata, and keeping the response from becoming an oracle. Use when fetching a client
fails when `output/data/optimization_results.csv` is absent; pass `--allow-draft` only for intentional early drafts. PDF Publishing Information reads `publication.doi`, optional `publication.repository_url`, and `publication.repository_label` from `projects/{name}/manuscript/config.yaml` via `infrastructure/rendering/_pdf_latex_helpers.py