@ericosiu argues Jev Images is underused for marketing: AI search visibility, ad creative gaps, CRO audits, pain-point reports.
ericosiu @ericosiu
EN
- 2.1k views
- 22 likes
- 0 bookmarks
- 0 reposts

About this case
Guide/thread with screenshots on marketing use cases for Jev Images (visibility reports, competitor ad gaps, CRO audits, painful-moments reports, free tools). For marketers and SEO/GEO builders.
Original posthttps://x.com/ericosiu/status/2112648227464106130
Related cases
- @NathanFlurry shares a tip learned the hard way at Rivet: Jev does not reason, which is by design, and they should have read the manual first. A single prompt that asked for the severity of an issue, with SEV1 through SEV4 as outputs, gave meh results and defeated what makes Jev useful, because an LLM would spend reasoning tokens to reach a conclusion. After reading the manual they split it into small questions: did production go down or become unusable, are they blocked with no workaround, and is something in Rivet broken or failing. Code then returns SEV1 if blocked, SEV2 if down, SEV3 if broken, and otherwise SEV4. He says that works. When a ticket is weighted badly, they give it to an LLM with what they expected, the LLM adds it to a test suite and adjusts the decision logic, and they backtest the new logic on old issues. Within a few tickets the classifier was solid. He calls this a feature of Jev, not a limitation: more control over how each decision is weighed than a generic LLM, and easier to reason about, monitor, and backtest how agents will behave. In their internal support tool the Jev question counts are 13 for support classification and customer status, 6 for severity, 6 for team replies and problem identification, 6 for follow-up timing, 4 for linked dependencies and later conversations, 2 for the addressed teammate, and 2 for conversation grouping. He ends with: Jev is awesome. A screenshot of a real-world classifier is attached.@NathanFlurry
- @AnnatarXBT posts about a 14-page paper on building a company brain: a cheap decision layer in front of an expensive reasoning model. The architecture is pulled from the TypeSafe and Anthropic docs. Opus 5.5 thinks, Jev decides, and the code holds the branch. You ask a typed question and get a typed answer. Jev returns it with a calibrated probability in 0.44s for $0.00035. A 0.999 goes straight into the if statement, and about 99% of turns end right there. The same gate, placed next to Fable 5.2, is broken down in the article below. The post quotes an earlier @AnnatarXBT post, which calls itself a full harness guide for Claude Fable 5.2 and Jev engineering: one evening with it and Claude does the work of a small dev team, and no $550/month course is needed. That quoted post links https://x.com/i/article/2120740198405357568.@AnnatarXBT
- @nolansym posts a new AI pattern, Jev Composite Scorecard. Ask atomic score questions, then weight them in code. The demo weights are clarity 40%, completeness 40%, and risk 20%, on a PR description. He built it with @aisdk v7 and the @shadcn registry.@nolansym
- @TiagerBao posts Chinese notes on a third-party compilation, "Jev Engineering for Coding Agents," of TypeSafe founder Diogo Almeida's thinking. He writes that writing code is only about 4–10% of tokens, and that the notes are not a shipped complete plan.@TiagerBao