Extracting brand kits: reference pixels → a kit the engine honors

Use the project and capability policy for scope, current state and metered work.

The one idea

No summarization anywhere in the path. A reference described in prose converges on house style with the reference's palette — the pixels are the ground truth. You (the agent) are the extractor: you SEE the reference, curate its frames, and reproduce its motifs as ordinary authored graphics, verified against the reference by looking. The kit you produce carries (a) exemplar frames the compose maker and judge both see, and (b) motif skins — card HTML the designer reproduces — plus code-checked facts (caption profile, density, palette). Once bound to a project, the engine takes over: the planner plans to your density, the designer sees your exemplars (view_style_reference), the judge grades every candidate against them, and a half-applied kit fails the compose loudly instead of shipping house style.

Everything below drives the public /v1 API with your API key. Frames never pass through chat — they go straight to storage via presigned PUTs.