This is exactly how I use Claude in all of my technical writing. I even wrote a skill for this.
Every claim has to be backed up by a reference. Every reference has to be double-checked. Primary sources are much preferred over secondary sources, and where no primary source can be found, that must be noted.
I also insist on simpler, more easy-to-understand writing, even if that makes the total output longer. Aiming at a general audience, of the same reading level as a standard newspaper.
Most of the rest of the skill is about ensuring the Chicago Manual of Style is properly followed, widow/orphan control and how that applies to callout boxes, tables, etc….
link? care to share? :) i often find myself starting with a tone guide.
Not yet. I want to publish my skill on GitHub and then let other people contribute ideas to it.
But as it stands today, there’s still too much personalization that is currently built into that skill.
I need to remove that personalization stuff and make it more general. Once I’ve done that, I am planning on publishing it.