>>

profile-backed feedback: every flag now has to explain itself

profile-backed feedback: every flag now has to explain itself

the editor had a gap.

it could mark a phrase. it could say the phrase sounded generic, too polished, too soft, too long, or too far away from the profile. but a user still had to trust the flag without seeing the evidence behind it.

that is not enough. if the product says a sentence does not sound like you, it should also say what it used to make that call.

what changed

profile-backed feedback adds a small evidence layer to the editor. not a new workflow. not another screen. the same highlighted text now explains whether the signal came from the profile, the samples, the selected format, a known ai pattern, or the user's own accept and dismiss history.

issue cards show source chipsa card can say ai pattern, sample rhythm, learned from you, profile match, or format fit.
tooltips explain the evidencewhen the user hovers or clicks a highlight, the tooltip says why that line was flagged.
good lines get evidence toogreen feedback can now show what is worth keeping, not only what needs fixing.

get started for $1 — create your account and scan your first draft in minutes.

get started for $1 →
works in the ai apps you already use
claudeclaude codechatgptcodexcursorwindsurfantigravityopencodecommand code
shashank
ai
shashank

writes about brand voice, ai writing patterns, and the craft of sounding like yourself. built hold your voice after watching his own voice flatten across six months of heavy ai drafts.

co-written with ai as sidekick. shashank drafted the observations; the ai pressure-tested the structural claims. if something reads too smooth, that's the ai's fault.