Your prose has a smell.

You probably stopped noticing it.

aiBreze. Editorial rules for prose that actually says something instead of just sounding like it. AI-assisted or not.

Spray the prose, not the author. It does not detect who wrote the sentence. It does not care. Bad prose is bad prose.

Not a humanizer

aiBreze does not determine whether a human or a model wrote something, and it does not try to fool AI detectors. It applies the same standard either way. If the prose smells, spray it.

A composable editorial system: core law, genre extras, a project overlay, then a smell audit and a claims pass.

Install · npm · GitHub · Why the name

Earn the word.

The problem is unearned language, not the dictionary. "Transformative" is fine if something transformed and you can say from what into what. "Inflection point" is fine if there was one. Overlay the terms that pass here. The heuristic is the rule; the list is not exhaustive.

Direct > clever. Clear > profound. Useful > insightful-sounding. No em dashes in publishable prose.

Before / after

Before. At its core, building software isn't just about writing code. It's about bridging the gap between imagination and execution, creating solutions that don't merely function but fundamentally transform the way we interact with technology.

After. Software turns an idea into something people can use. Good software does that reliably.

The package

Markdown you install and point an agent at. Shared core, additive genre files, a short project overlay. A smell audit. A claims review that checks substance before cologne.

pnpm add -D aibreze

The package lives on npm. This site is the public face. Install and agent setup →

Built by Catalyst Forge LLC. MIT.