# Repository agent instructions

When technical prose contains `<!-- techviz:generate id=... -->`, use the `technical-visualizer` skill. Do not hand-author SVG or author VizSpec from the schema alone.

Required order:

The `techviz references` output includes exact preview and executable runtime-spec paths; inspect them when available.

1. `techviz prepare` around the marker.
2. `techviz references` to inspect matched logical grammars.
3. `techviz prompt` and use the generated prompt in full.
4. Produce VizSpec 1.1 JSON only; select a composition profile and cite line ranges on every factual boundary/group, node, and edge.
5. `techviz lint` and correct all errors. Disconnected-card output is a hard failure except for a grounded `comparison` or `timeline` profile.
6. `techviz build` to render and update the Markdown block.
7. For multi-diagram work, run `techviz audit-batch` and reject template collapse.
8. Review the SVG at normal reading size and inspect the editable source diff.

Publication SVGs are diagram-only: no visible global title, question/subtitle, footer, takeaway band, watermark, or decorative narrative panel. Titles and descriptions remain metadata and accessibility text.

Never invent undocumented topology, protocols, vendor services, trust boundaries, ordering, or comparison criteria. Unsupported hypotheses must be explicit assumptions and are publication blockers unless the author approves them.