visualise

Pick the most informative visual form for the input, generate a self-contained output file (no non-CDN external requests — CDN libraries are permitted only from the approved hosts in references/design-thinking.md), validate it, then report the output path.

If the input has no clear visual form, default to a formatted document layout (readable typography, structured sections) rather than forcing a chart. Never ask the user to clarify — a visualisation only has value if it appears quickly, and a clarifying question stalls that; pick the most informative form and proceed.

Write the output file to the directory containing the input data (or the project root if there is no input file), named visualisation.html by default. Use a descriptive slug (e.g. sales-2025.html) only when the user's input has an obvious subject or time period that would make the filename meaningfully more identifiable.

Apply the aesthetic and design thinking guidance in references/design-thinking.md.

Available scripts

• scripts/validate.py — Validates the output file for structure, self-containment, and typography issues.

Validation loop

After writing the output file, run:

uv run scripts/validate.py <output-path>