When should you use it?
- AI drafts of posts, pages, images or videos come out polished but look like everyone else's
- You keep explaining the same style to Claude at the start of every project
- An agency or in-house team needs several distinct looks for different clients
Not for: One-off pieces where a couple of pasted examples are enough; Copying a competitor's work; examples are for studying what works, not cloning it; Teams with no time to grade examples, since the grading is where the value comes from
What do you need, and what do you get?
You need
- Claude with skills enabled and web search or a folder of candidate examples
- A clear description of the project and the content type
- An hour or so to mark each example as good or bad with a one-line reason
You get
- A scouting skill whose main file holds lessons that apply to every search
- A reference file for each style describing what makes strong examples work
- A project folder with notes for the current job
- A style catalog the scout reads before it searches again
How does it work, step by step?
- Scout widelyAsk the scouting skill for a large batch of examples for one project. Expect most of them to miss.
- Grade every oneMark each example good or bad and say why in a sentence. Your reasons are the training material.
- Save feedback at the right levelRules for every search belong in the core skill file, notes about one style go in that style's reference file, and notes about this job go in the project folder.
- Dissect the winnersOnce you have about a dozen strong examples, have Claude break each one down and write the lessons into the style's reference file, or start a new file for a new style.
- Read the catalog firstMake the scout check the style catalog before each search so it builds on known styles instead of finding the same ones again.
The prompt
Our own prompt, inspired by u/tjrobertson-seo on r/ClaudeAI and written to work in Claude, Claude Code and Claude Cowork. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are my example scout for {content_type} projects. First read the style catalog in {catalog_folder} so you do not rediscover styles we already have. Project: {project_brief}. Find {n_examples} examples that could inspire this project. List each with a link, a one-line description and your guess at which catalog style it fits, or 'new style'. Then wait. I will mark each one good or bad with a reason. When I have, sort my reasons into three places: rules for every future search (update your main skill file), notes about one style (update or create that style's reference file) and notes about this project only (save them in {project_folder}). Show me every file change before you save it. Never copy an example into a deliverable.
Inspired by u/tjrobertson-seo on r/ClaudeAI: Reddit post: how we stopped getting generic output from Claude. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Show only one sample and the draft often mirrors it too closely. Give several that differ from each other.
- Telling the model to avoid an AI look usually trades one habit for a different one. Show finished work instead.
- Reference files can grow stale. Prune notes that no longer match what you approve.
- Respect rights in the examples you collect. Use them to study structure and pacing, and never republish them.
Our take
Generic output is the most common complaint we hear about AI content, and this post gets at the root of it: without a target, a model drifts toward its usual habits. TJ Robertson's answer is not a cleverer instruction but a habit, and that is why we like it. The scout does the tedious part of finding candidates, while people do the part only they can, which is saying why something is good. The three storage levels are the smartest detail. Lessons that apply to every search, notes about one style and notes about one project each live in their own place, so the skill gets sharper without filling up with one client's quirks. Two cautions. Grading takes real time at the start, and the first few projects will feel slower than just prompting. And collected examples belong to their makers, so use them for study and never paste them into deliverables. In our dry run, the adapted prompt sorted twelve fictional example descriptions for a dental clinic video, explained four keepers and drafted a new style reference file from them.
Where the time goes back: After a few projects the skill already knows what each style means, so you stop rewriting briefs and redoing drafts that missed the look.
FAQ
How many examples are enough?
Does this only work for video?
When does it start paying off?
Source and credit
Inspired by u/tjrobertson-seo on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Reddit post: how we stopped getting generic output from Claude
- Creator
- u/tjrobertson-seo on r/ClaudeAI
- Published on
- Original date
- Nov 9, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Nov 10, 2026: passed. Dry-run tested by our AI test agent on sample input. Catalog checked first, four keepers explained, feedback stored at three levels, new style file drafted, nothing saved without approval.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 10, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.