The kit format and how to make a kit: the sheets and their panels, the layer types, the workflow. Read first.

A sheet's template ('jersey' 2048x2048 or 'bib' 2048x1024). style 'guide': the panels and where the game's male (blue) and female (pink) riders' kit edges, seams, zip and pockets fall, for placing layers. style 'clean': white panels with thin outlines, names and which way is up, the zip line, pockets, cuff and gripper bands: the canvas to paint a whole sheet on (route B, e.g. with an image model; paint everything, leave no outlines or words). save_to: also write the full-size PNG to this path (local servers).

Add a picture the kit uses: a logo for an 'image' layer (PNG with transparency is best) or a whole painted sheet for {"sheet": ...}. Give a local file path (local servers) or base64 PNG/JPEG data. Use the id it returns in the kit. Names: letters, digits, _ and -. In a chat app that can't send a picture's bytes, skip this: build with layers.

The pictures added so far.

Check a kit object against the format. Returns 'valid' or the problems to fix.

The kit's two finished sheets as pictures (jersey, then bib), to check the flat layout.

The kit on the game's rider, in the game's look; follow it with compare_to_reference and fix what differs. body: 'male' or 'female'. views (any of front, front34_left, left, back, right, front34_right; default front, front34_left, back). front34_left = the front turned to show the rider's left side, like most product photos.

The user's reference picture beside the kit on the game's rider from a similar angle, to spot what differs (colours, where panels and logos sit, sizes). Pick the view nearest the reference's angle. The rider is cropped to the jersey (jersey_only, default) or to the jersey and bibs, as product pictures are framed. If you can't send the picture's bytes (a chat app), leave the reference out: you get the rider's views alone to set beside the picture you can see. grid (default on) draws the FRONT and BACK panels' coordinates on the rider (a line every 0.1 of u and v, thicker at u = 0.5): read off where and how big each logo, stripe and panel edge is in the reference, and set the same numbers in the kit.

Write the kit file (.kit.zip: kit.json, the two finished sheets, its pictures, previews) and hand it back. Only after the compare loop shows the kit matching the user's pictures (see get_kit_spec's workflow); it refuses a kit that was never compared, or one with invented parts, until user_approved=true (the user has seen and agreed). The result carries the file itself (an embedded resource, application/zip, also readable later as kit://) for you to save or pass on, plus where the server wrote it (path: local servers; default its work folder) and a preview to check.

Open a .kit.zip (made here or elsewhere) to keep working on it: returns its kit object (to edit and pass to the other tools) and adds its pictures as assets; also shows it on the riders.