🟢 One session — A few hours, sittable in one gonext.jsai-sdk
Spending 40 minutes fighting a regex that should take 2
“I know roughly what I want to match, I have examples, but I always end up trial-and-erroring a regex on some tester for way too long.”— Hacker News ↗
The gap
Regex testers assume you already have the pattern. Going from 'these should match, these shouldn't' to a correct, explained pattern — and verifying it live against your examples — is the part nobody packages well.
For
Developers who don't write regex daily
Paste-ready build prompt
Build a 'regex from examples' tool in Next.js. User provides strings that SHOULD match and ones that SHOULDN'T; an LLM proposes a pattern with a plain-English explanation, and the UI live-tests it against all examples, highlighting any it gets wrong. First 3 steps: (1) two lists (match / no-match) + generate, (2) LLM returns `{pattern, explanation}`, (3) client-side live testing against both lists with pass/fail badges and a copy button.