Turns a Design_Brief into verified frontend code via a manual closed loop: hands the brief to GLM 5.2 (code author), renders the result, screenshots it, and verifies on three lenses (visual compare, Pre-Flight tell-scan, and motion compare), sending design-only feedback until the result matches the source (or brief intent for inspiration briefs), avoids the generic-AI look, and moves like the source. Use when a Design_Brief exists or when a raw design needs the full pipeline (runs image-to-prompt, video-to-prompt, or inspiration-to-prompt first), for example "verify this against the mockup" or "run the generate-and-verify loop." Manual loop, no API keys required.
Produces faithful frontend code from a natural-language Design_Brief when GLM 5.2 is the code author. Covers brief format, fidelity rules, anti-tell rules, stack-specific delivery shape, and iterative visual feedback handling. Load on the GLM 5.2 side (OpenCode, ZCode, chat.z.ai system prompt). Pairs with generate-and-verify on the orchestrator side.
Turns a design image, screenshot, or mockup into a structured natural-language Design_Brief covering layout, components, text_content, spacing, colors, typography, states, motion, atmosphere, interactions, images, and target_stack. Use when someone shares a UI image and wants to rebuild, recreate, clone, or turn it into frontend code, for example "rebuild this screenshot" or "turn this mockup into code". First step of the caecus pipeline; hands off to generate-and-verify.
Turns a design from an inspiration gallery (link or screenshot: Dribbble, Awwwards, recent.design, etc.) into a natural-language Design_Brief that captures style, layout, and patterns as INSPIRATION, not a 1:1 copy. Use when someone wants to build something new in a reference style, for example "make something in the style of this Dribbble shot" or "build a landing page inspired by this". Feeds the brief into generate-and-verify with inspiration_only true.
Turns a UI screen recording, product demo, or interface animation into a structured natural-language Design_Brief covering layout, components, text_content, spacing, colors, typography, states, motion, atmosphere, interactions, images, and target_stack. Use when someone shares a video or recording of a UI and wants to rebuild or recreate it as frontend code, for example "recreate this screen recording" or "build the UI from this demo video". Feeds the brief into generate-and-verify.