@fernforge/alchemy
Advanced tools
Turn AI prose into human-quality writing. A drop-in ruleset that tells your coding agent how to write docs, READMEs, commits, and replies without the tell-tale LLM patterns.
Turn lead into gold: AI prose into writing that reads like a person wrote it.
Hand this ruleset to your coding agent (Claude Code, Cursor, Copilot, any LLM) and the docs, READMEs, commit messages, and replies it writes stop carrying the usual generated-text tells. You know the ones. The em-dash in every other sentence. "It's not just a tool, it's a workflow." The stray delve and robust and seamless. The conclusion that restates the intro and adds nothing.
The whole thing is one file: ALCHEMY.md. Everything else just gets it into
your project.
npx @fernforge/alchemy init
That writes ALCHEMY.md and links it from your CLAUDE.md, AGENTS.md, .cursorrules, or
Copilot instructions if you have one. Your agent reads the rules whenever it writes after that.
Just want to read or paste them?
npx @fernforge/alchemy print
Or copy ALCHEMY.md into wherever your tool reads project instructions. It's
plain Markdown and tied to no particular agent.
The rules are grounded in what people actually flag as AI writing, not guesses: Wikipedia's "Signs of AI writing," the Kobak et al. study measuring which words spiked in research papers after ChatGPT, Pangram's phrase-frequency data, and the long-running arguments on Reddit and in r/Professors about spotting it.
They cover the banned constructions ("not just X, but Y," the rule-of-three flourish, the helpful-assistant outro), the vocabulary that fingerprints LLM text, the punctuation tells led by em-dash overuse, vague attribution, and a self-check the agent runs over its own prose before handing it back.
One rule sits above the rest: no single word or dash proves anything. The tell is density, the same handful of tics clustered together over flat, evenly-weighted text. So the rules weight co-occurrence over any one hit, and they never tell you to cut a word that happens to be the right one.
This README follows its own rules. If it reads fine, that's the pitch.
Alchemists tried to turn base metal into gold and never managed it. This is the easier version of the trick, and it mostly works by subtraction: cutting the padding the model adds by default until what's left could pass for human.
The goal was never to beat an AI detector. It's to write something worth reading. Specific, uneven, willing to have a point of view. A fooled detector is a side effect.
Found a tic the rules miss? Open an issue or a PR with a real before/after example. Keep it concrete. The rules earn their place by being specific, not by being long.
MIT
FAQs
Turn AI prose into human-quality writing. A drop-in ruleset that tells your coding agent how to write docs, READMEs, commits, and replies without the tell-tale LLM patterns.
We found that @fernforge/alchemy demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Research
/Security News
Ten malicious OpenAPI React Query Codegen versions were published to npm in the Mini Shai-Hulud attack, all with valid provenance.
Security News
Socket joins more than 100 technology, cybersecurity, and financial organizations calling for a global surge in cyber defense.
Product
Enterprise security teams can now detect malware, credential theft, suspicious network activity, and risky updates across Microsoft Edge extensions.