In our battle against AI-written content, we launched UnitText as an alternative to use AI to review text, instead of writing it. I got the idea from this lovely book "Writing for Developers"[1] that recommended some quality prompts to use a LLM as what could be considered a copy editor.
I initially liked to call it "unit tests for text", which inspired a prototype,[2] a blog post,[3] and then this product.
We believe everyone is getting really fed up of reading content only to immediately understand it was written by a robot. At the same time, we don't think language models are completely to blame, they are just a tool, and it's on us to use them properly.
The idea of UnitText is that before one starts writing they define a goal and audience for their content. It could be a blog post, but also an email... at some point we'd like to offer different templates for various types of content.
The human is the one doing the writing, and they can then ask the AI to "review" (or, "test") the content, to see whether the goal was met, the explanation is clear, something can be added or cut...
[1]: https://www.manning.com/books/writing-for-developers
[2]: https://github.com/sealambda/unit-text
[3]: https://www.sealambda.com/blog/this-post-passed-unit-tests/
