Can I vibecode Rephrasy?

NOT REALLY · don't bother

price $18.99/moyou'd save $227.88/yrbuild time one sitting for the wrapper; the detector-grade part is not a build, it's an ongoing arms racecategory ✍️ ai writingreplaced by 0 people

You can one-shot a rewriting wrapper that makes text sound less robotic, and for that job the DIY build is genuinely fine. What you cannot one-shot is the actual product: custom fine-tuned models plus a continuous evaluation loop against detectors (GPTZero, Turnitin, Copyleaks, Pangram) that retrain specifically on LLM-rewritten text. A prompted rewrite moves detector scores inconsistently, and detectors drift monthly, so a static prompt that works today quietly stops working. If your bar is 'reads naturally', build it; if your bar is 'passes detectors reliably', the moat is the model and the eval treadmill, not the text box.

the prompt

Build me a local AI-text humanizer workbench. This is the honest consolation build: it makes AI text read naturally, it does NOT promise to beat AI detectors.

Stack: Node 22 + Express, vanilla JS frontend, SQLite via better-sqlite3. No build step.

- One page on localhost:5180: input textarea left, output pane right, a Humanize button, and a strength select (light touch / standard / heavy rewrite).
- Humanize calls an LLM (Anthropic or OpenAI, key in .env) with a fixed system prompt per strength level that: varies sentence length and rhythm, cuts hedging and filler ('delve', 'moreover', 'it's important to note'), swaps uniform paragraph shapes for uneven ones, and keeps meaning, facts, names, and numbers intact. Stream the output.
- A word-level diff view between input and output (the `diff` npm package) so I can see exactly what changed.
- A Re-roll button that re-humanizes the current output with a different seed phrase in the prompt, keeping the last 5 attempts switchable via tabs.
- Every run saved to SQLite: timestamp, strength, input, output. History page with the last 100 runs and copy buttons.
- Cmd+Enter runs humanize.
- .env.example with the key name; README states clearly: output is for readability, no detector-bypass guarantee, and text leaves the machine only for the LLM call.
- Out of scope, deliberately: detector score checking, browser extension, accounts, multi-language tuning, API access.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

why people still pay

Because 'sounds human to me' and 'passes Turnitin' are different products. Prompt-based rewrites are exactly what modern detectors train on, so DIY results are hit-or-miss and degrade as detectors update. Paying customers are buying a maintained pass rate: someone else fine-tunes models, re-benchmarks against every detector release, and eats the retraining cost when the arms race moves.

what you lose

xfine-tuned models trained specifically to survive AI detectors

xcontinuous re-testing as GPTZero/Turnitin/Copyleaks/Pangram update

xbuilt-in detector scoring to verify output before you use it

x50+ language support and custom writing styles

xChrome extension and REST API

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced Rephrasy ($18.99/mo) with one prompt"