The Megatrend 3 article is the first article where we used our own custom skills in Claude to run the editorial check.
On the "why bother" question: the main driver for building this originally was to remove a subscription. Specifically, Grammarly. The argument for me was simple. If you put the right rules and styles into a language model, can you can get to the same outcome - we proved that to be true. Now why keep paying for what has become a very expensive Grammarly subscription, especially when Grammarly's own AI integration has made the writing output feel worse, not better, and less authentic?
In previous articles, the approach was to load the relevant context and reference documents as project files inside a dedicated Claude project. That worked, up to a point.
The frustration was that Claude, being a language model, would sometimes just make things up, or worse, tell you it had referenced the files when it hadn't. You'd end up going round in a loop of AI frustration that didn't go anywhere productive.