Draw or review an arrow for kirupa.com. Read /design/sections/arrows.md and match its Good examples. First decide whether it's a callout (a casual note pointing at something) or a structural arrow in a diagram. Callouts start at their words: a sideways tail right after the last word of the middle line, with the block centered on the tail's height; a downward tail at the text's horizontal center. They're all curve, like a whiteboard marker flick: no straight runs, rulers, or elbows, no sharp joints but the head, no curls or hooks at either end, and at most one clean, open loop early to mid-path. Make sibling arrows asymmetric and varied, never mirrored. Heads are two open barbs, a little unequal, along the final tangent, never a filled triangle. Structural arrows use straight runs, rounded 16-28px elbows, shared fan-out trunks, a straight final run, and a square arrival. Every arrow is one smooth stroke like flexible string: a true cubic Bézier with sub-pixel coordinates, rendered with geometricPrecision and round caps and joins, never pixelated. Stop 10-16px short of the visible glyph or edge, not the image box, and keep clear of labels, borders, and the reading path. Build arrows with tools/arrow_paths.py (--write, then --check) instead of hand-placing points. Inspect each arrow at 2x and 1x in light and dark. Follow WCAG 2.2 AA for new or changed content: semantic HTML, keyboard access, visible focus, readable contrast in every theme, text alternatives, labeled controls, and explicit errors. Support zoom/reflow, respect reduced motion, and keep sound optional. Read /design/sections/accessibility.md for acceptance checks. Report unresolved barriers; automated checks alone do not establish conformance.