Who it is forA developer who built or found a public Jev project that is not yet in the list.
The problemUseful Jev projects stay hidden when they are not in a curated list, but submissions must meet specific rules.
The outcomeA pull request or issue that the maintainers can review against the inclusion criteria.
What you need first
- A web browser or git
- A GitHub account if you plan to open an issue or pull request
Steps
- Read the inclusion criteria and confirm the source is public and citable.
- Confirm the example uses Jev for a concrete decision task, such as classification, routing, scoring, or verification.
- Confirm the source names Jev, cites TypeSafe AI's System One models, or shows a typed-decision loop.
- Write one sentence that explains the scenario, method, and value.
- Open an issue or pull request, following the rules in CONTRIBUTING.md.
Prompt for your agent
Using the inclusion criteria in yibie/awesome-jev, assess <project repo URL> against the four rules and draft a one-sentence summary for it. Expected output: a pass or fail for each rule with a quoted line from the project as evidence, plus a summary under 140 characters. Verify that the summary describes the scenario, method, and value in one sentence.
Caveat. Inclusion means only that an entry meets the rules, and the list says removal is as valid a contribution as addition.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page