Launching today
TechWrit AI
AI agent that enforces your team's technical doc standards
2 followers
AI agent that enforces your team's technical doc standards
2 followers
Your engineers use Copilot and Cursor to write docs fast — but the output ignores your style rules, terminology, and glossary. TechWrit AI is the quality gate. Paste any draft and get it reviewed, rewritten, or generated against your team's standards automatically. 14 modes, 16 style rules, terminology enforcement, product glossary, readability scores, word-level diffs, and prompt templates. Export your config as JSON — your whole team writes consistently from day one. Free tier available.
Hey Product Hunt! I'm Patricia McPhee — a technical writer with 30 years in tech. I've documented APIs, SDKs, and developer platforms at Microsoft, Amazon, Facebook/Oculus, GE Healthcare, and more.
Here's the problem that made me build this: I work with engineers and developers who use AI tools — Microsoft Copilot, Cursor, GitHub Copilot — to generate documentation. The output is fast, but it ignores every style rule I've ever written. "Click" instead of "select." Future tense. Passive voice. Jargon without definitions. I've shared the rules in Confluence, pinned them in Slack, put them in the repo wiki. It doesn't matter. Most engineers don't know how to configure their AI tool to follow documentation standards, and the ones who try get inconsistent results.
I became the human linter for AI-generated content. Same feedback on every PR. Same corrections in every review. The docs were getting written faster, but I was spending more time fixing them than ever.
The core idea behind TechWrit AI: what if the documentation standards enforced themselves?
TechWrit AI lets you define your standards — style rules, terminology, product glossary — and then checks, rewrites, or generates technical content that follows them automatically. An engineer generates a first draft in Copilot, pastes it into TechWrit AI, and gets back content that actually meets the team's standards. It's not a grammar checker — it's a documentation quality gate.
A few things I'm particularly proud of:
1. The glossary isn't just a spell-checker. When you define "webhook" with a definition and synonyms like "callback URL," the AI actually uses that definition when writing. It doesn't just check spelling — it understands what your terms mean in context.
2. Prompt templates save real time. Select a built-in template (like Feature Requirements Doc or Release Notes), fill in the placeholders, and submit. The mode and doc type auto-set. You can create your own templates for any recurring document type.
3. Readability scores are real. Flesch Ease, Flesch-Kincaid Grade, and Gunning Fog update live as you type. In Rewrite mode, you get before/after comparison with word-level diffs — so you can show stakeholders exactly how much a rewrite improved an API guide.
4. It's transparent. You can see the full system prompt. No magic — just structured AI instructions built on the same technical writing principles I've used across a decade of documentation reviews.
The 16 default style rules aren't theoretical. They're the rules I enforced at every company: use active voice, write in present tense, address the reader as "you," define jargon on first use, eliminate redundancy. The rules that matter for technical documentation specifically.
The Free tier gives you 10 requests/month with all 14 modes. No credit card needed.
I'd love feedback, especially from technical writers, developer relations, and documentation leads. What rules does your team enforce that I should add as defaults?