← Files ImagoARCHIVED FILE
references/visual-routing.md
1.34 KB · Nov 15, 2026 · 06:42 UTC
# Visual output routing Use **intent + required output properties** before selecting tools. Words like design or visualize alone do not establish a new image: a user requesting an editable deck, vector mark, UI implementation or interactive map needs a different artifact. | User asks | Route | Outcome | |--|--|--| | Create an illustration | `create-image` | Rendered image when native tool exists | | Change the uploaded image | `edit-image` + `localized-image-edit` | Modified image, preservation checked | | Improve a screenshot visually | `ui-screenshot-redesign` | Static mockup only unless implementation requested | | Make a print-ready SVG logo | `brand-and-icon` plus supported vector workflow | Actual SVG if possible; don't deliver raster pretending SVG | | Chart from data with exact numbers | `data-to-visual` using deterministic chart/tool | Accurate values and axes | | Concept map | `diagram-and-map` | Clearly illustrative; geographic route requires map service | | Write a prompt | `write-visual-prompt` | Text prompt, no generation claim | Image tools not present: state limitation and offer supported substitute only when useful. An image source is required for an edit; do not hallucinate absent attachments. Prefer one edit operation per revision to reduce drift. For user-provided images, source controls truth over related internet examples.
SHA-256: 27984a29208735d676989477e0f59a6efb33b2bc28c459426480d33951d58bb5