Skip to main content

Inspection checklist

Written for version 0.1.7. Source: inspection-checklist.md.

The assistant runs these checks on the rendered figure before showing it to you. They add no extra approval steps; How it works sets those.

Content and connections

  • Each view says what was agreed, including the decisions and exceptions it needs.
  • Planned, live and unconfirmed behaviour are told apart, and each output shows only the sources that really feed it.
  • Every arrow is traced end to end: right start, right end, right direction, right meaning. Equivalent inputs don’t look like a sequence.
  • Objects that appear in several views have the same label, look and role in each.
  • A prerequisite sits beside the step it affects, not in an unrelated footer.

Geometry, checked by code where practical

  • Text and images fit their boxes and the canvas, with nothing clipped or overlapping.
  • No collisions between text and icons, labels and arrows, or arrows and boxes, apart from intended arrow ends and declared container-boundary crossings (rules A5, A6 and T2).
  • Junctions, arrowheads, crossings, reversals and avoidable bends are inspected (A3, A4, A7, A9, A10 and A11).
  • Columns line up; padding and spacing are consistent (L1, L2 and L4).
  • Applicable rules on Design principles are assessed using their measure, review and look methods; these tags do not mean validators exist. Findings name the rule, associations and justified exceptions. Unsupported or unavailable checks are recorded as not checked, never pass. Revisions trigger checks of moved elements, connected routes/labels and affected neighbours; scaling or global style changes trigger a whole-view check.
  • The SVG parses, every referenced asset exists, and exports match the current source.

A passing geometry check isn’t proof of good design, and a trivial edit doesn’t need a test harness.

Looking at it

  • At its intended size, the main action is obvious, the start and end are clear, grouping helps, and contrast is enough. Use destination requirements and the scoped W3C contrast guidance on Design principles; a font-size floor does not prove readability.
  • No crowded boxes next to large empty areas; fix the layout before adding more arrow routing.
  • Illustrations match each other and mean something; logos are genuine.
  • Phone width is checked honestly. If it’s illegible, there’s an enlarged view or agreed crops, keeping the approved illustration.
  • Every changed view and export is re-inspected; old screenshots don’t count.

Independent review for substantial work

The reviewer gets the current render, the content brief, the style reference, the target size and the planned-versus-live distinctions. They report where each problem is, what it is, why it matters and the smallest fix, without changing the content. Factual review is kept separate from visual design review. Minor edits don’t trigger a full review.

Interactive and delivery checks

When the figure is interactive: exact-region highlight, complete hover, moving the pointer into the panel, click to pin, touch, keyboard and focus, Escape or close, zoom and pan, behaviour at the screen edges, and scrolling, in every view. The text account and static exports stay current.

The figure is shown through the chat’s own viewer; local file links are extra, not something a phone can open. The assistant reports which browsers and devices it actually tested, which tests were simulated, and what it couldn’t check.