A writing assistant thatkeeps the docs consistent
A technical writer's day is rough notes, half-labelled screenshots, and the same terminology drift creeping into every page. Khint sits behind one shortcut: it pulls UI text off the screen, rewrites messy notes into your house voice with a reusable AI action, and publishes the finished section to Confluence, without leaving the editor.
The writing is fast,
the consistency is the grind
Anyone can write a paragraph. The hard part is that page 40 has to sound like page 1, use the same term for the same feature, and describe a dialog exactly as it ships, while the engineers keep handing you Slack threads instead of prose. That means retyping UI labels, re-explaining your style to a chatbot every session, and pasting each result back by hand. Khint compresses that work with its three pillars, Agents, Capture, and Memory, wired together behind one palette, so the doc gets written where it already lives.
One page, notes to published
Writing the “v3.2 admin guide” section, from raw engineering notes to a Confluence page.
Open a session for the doc you're writing
Before you start the page, begin a Memory session: call it “v3.2 admin guide”. Every Action you run is logged to it, and Khint keeps a compact running summary. That summary rides along on each AI Action, so as you work down the outline the model already knows the feature you are documenting, the terms you have settled on, and the sections you have already written. How Memory works →
Pull labels and errors straight off the screen
Documenting a dialog, a settings pane, or an error state? Instead of retyping every field name, use the palette's Extract text capture row: draw a box around the UI and the exact strings land on your clipboard, ready to drop into the doc. No transcription typos, no guessing at the wording of an error message. How Capture works →
Rewrite rough notes into your house voice
Engineers hand you a Slack dump or a bullet list. In Agents, save an Action like “Apply the docs style guide”. Don't have a prompt? Type a description and press Generate: Khint drafts one that rewrites the notes into your voice, tense, and heading pattern. Or clone the Doc Polish starter pack for a working rewrite Action. Select the raw notes, hit Cmd+Shift+K, run it, and the polished prose is pasted back in place.
Keep every page saying the same thing
Consistency is the whole job. Because the same Action is reused on every paragraph, one page never calls it “workspace” while the next says “project”. Chain your capture-cleanup and style Actions into one Workflow so “rough note → publishable paragraph” becomes a single keystroke, and let Memory carry the glossary you have already established into every prompt automatically. Tidy an existing page instead →
Publish the finished section to Confluence
When a section is done, the palette's Confluence Create page row turns your text into a page in the right space, title from the first line, body from the rest, without leaving the editor. Connect Atlassian once and the same shortcut that rewrote the draft also ships it. How integrations work →
Why not just paste each note into a chatbot?
You can, and for a forty-page guide you'll restate your style rules every chat, re-teach the model your glossary, retype every screenshot by hand, and copy each result back into the doc. Khint removes the round-trips: the style Action is saved once and reused on every paragraph, Memorycarries the terminology you have already settled into every prompt, Capture lifts UI text off the screen so you never transcribe a label twice, and the Confluence integration publishes the finished section where readers will find it. Because Actions only see the text you select, plus the session summary you opted into, the unreleased feature you are documenting isn't sitting in a chat history.
Common questions
How does a technical writer actually use Khint?
You do the writing; Khint removes the friction around it. Select a paragraph of rough engineering notes, hit Cmd+Shift+K, and run a reusable AI Action that rewrites it into your house voice: same tense, same terminology, same structure every time. When you need a UI label, an error string, or a config value out of a screenshot, the Capture row extracts the text so you transcribe nothing by hand. When a section is ready, the Confluence Create page row publishes it. It all happens in whatever app the draft already lives in.
Does Khint replace my documentation tool?
No: it works alongside it. Khint is a menu-bar assistant, not a docs platform: you keep writing in Confluence, your static-site generator, your Markdown editor, or wherever your source lives. Khint acts on the text you have selected, wherever it is, and pushes finished sections into Confluence with the Create page row once you connect Atlassian with your email, API token, and cloud domain. It writes into your tools; it does not ask you to move into a new one.
Can it keep my terminology and style consistent?
That is what a saved Action is for. Write one 'Apply the docs style guide' Action once: your preferred voice, the product's canonical term for each feature, the heading pattern, and reuse it on every paragraph. Don't have the prompt written? Type a one-line description in the Action editor and press Generate; press Improve later to tighten it in place. Khint also ships a Doc Polish starter pack you can browse and clone from the Agents page, so you start from a working rewrite Action without writing anything.
Where does my draft text go?
An Action only ever sees the text you selected, plus the compacted summary of your active Memory session if you opted in. Memory sessions live in a local SQLite database on your Mac and are never synced to Khint's servers, and your Atlassian credentials stay in your OS keychain. Nothing about an unreleased feature you are documenting leaves your device silently.
Try it on your next doc
Free with 10 AI actions and 5 captures per day. No credit card. Save the style Action once, reuse it on every page.