SVG

You own the file from the request to an SVG that ships: clean, on the project's tokens, and moving by the engine its home allows.

A construction skill that works on the file and nothing else. It does not time page transitions or gestures (khe-ui), choose or size an icon pack for a product (khe-ui), draw a diagram (khe-diagram), design, animate or pack a sticker (khe-sticker), place icons inside a faux product demo (stageshow), or add the sound to a reveal (khe-sound).

The one idea

An SVG is markup the next person has to live with: it scales, takes the theme's colour, names its parts, and moves only by an engine its home can run, for a cause.

Five ways it fails:

• Picture. Treated as an image: fixed width and height, no viewBox, every colour a baked hex, a PNG inside. It will not scale or recolour.
• Anonymous. A hundred unnamed groups, no accessible name and no decision to hide it, ids and selectors that collide the moment it is inlined. Nobody can address a part.
• Export. The generator's file shipped as it came: editor namespaces, 8-decimal paths, empty groups, the same gradient four times, 200 KB.
• Wrong engine. Page CSS aimed at a file loaded as an <img>, a hover inside an image, SMIL with no still, a native morph between paths whose commands do not match.
• Restless. Motion with no cause: a line, its area and its dot fading in together, a loop on something seen all day, a morph where a rotation or a swap was the honest answer, no reduced-motion state.

The first three make a file nobody can use, and they are worse than the last two. A file that ends with no animation is a valid result.