Building a site-scoring production app with Jev and Opus 5.5
A developer feeds a URL into a pipeline where Gemini takes a screenshot, Jev scores it against fixed criteria, and Opus 5.5 writes the code, at under a cent per scan.
built a full production app with opus 5.5 and jev... fed it a url, it screenshots the site, scores it against a list of known patterns, and ships a shareable report here's the actual pipeline: - gemini flash takes the screenshot, that's the only vision step needed - jev scores it against a fixed list of criteria in a fraction of a second, no text generation, just structured ratings - opus 5.5 writes the entire app, front to back, off a single planning prompt - product os turns the plan into a spec, then a roadmap, then working code, task by task - code review, security audits, and testing happen automatically as it builds, not after - a deploy checklist gets generated too, walks you through auth setup, hosting, env variables, step by step - cost to run per scan lands in fractions of a cent, both models chosen specifically because they're cheap at their job what actually makes this work: opus 5.5 handles everything generative, jev handles every decision that doesn't need generation, and neither model gets used for a job it's not built for that split is why the whole thing runs on pennies instead of frontier-model pricing pair that with a structured build system instead of one long freeform prompt, and a non-coder ships a live, secured, production app in an afternoon, not a sprint
This post quotes another post: x.com/rewind02/status/2102712931766915139