# Start here

This folder is The Rabble Group's content engine, given away - the same prompts and files we run for our own site and our clients (rabblegroup.com). Take them, adapt them, no license.

## The fastest way to use these

You do not have to read everything first. Download the files, put them in a folder, open an AI assistant that can read that folder (Claude, ChatGPT, or similar), point it at the files, and say:

> Explain these files. Tell me whether they are relevant to my situation and project, what I need to know about them, and how we would start setting them up and adapting them for my use case.

Then work through it together. The assistant will tell you which pieces fit, help you fill in your voice profile and your profile config, and wire the output to wherever you publish. Skim them yourself too, so you know what the machine is doing - but the prompt above is the practical starting move. These files are meant to be *operated by* an AI assistant inside a project folder: they reference each other and your own context files, so handing them to your assistant and adapting together is exactly how they are built to be used.

## What's in here

- **voice-profile-template.md** - fill this in first. The scaffold for how your brand sounds; everything else reads from it.
- **content-anti-patterns.md** - the hard "never do this" gate that keeps AI-assisted writing from reading like slop. General rules, plus a few behavioral-health-specific ones you should swap for your own field.
- **radar.md** - the weekly scanner that decides what is worth writing.
- **blog-writer.md** - the drafter. It loads your voice, your profile, and your output target, so one file writes for any business.
- **newsletter-writer.md** + **newsletter-push.mjs** + **resend-config.example.json** - the newsletter writer, the script that turns its markdown into a Resend draft, and a config example. Nothing sends without a human.
- **voice-learner.md** + **site-sync.md** - the learning loop: they read what got published back off your site and propose improvements to your voice files over time.

## The order to adapt them

1. Work up `voice-profile-template.md` for your brand - the fast way is to hand your assistant a few samples of how you actually write, let it draft the profile from them, and correct what does not sound like you. You are the judge, not the typist.
2. Adapt `content-anti-patterns.md` - keep the general rules, swap the domain-specific ones for what would be careless in your field.
3. Point `radar.md` at your sources, then let `blog-writer.md` and `newsletter-writer.md` run off your voice and profile.
4. Add the learning loop (`voice-learner.md` + `site-sync.md`) once you have published a few pieces.

Full walkthrough: [How to build a content engine](https://rabblegroup.com/blog/how-to-build-a-content-engine-ours-in-full/).