A useful content project shouldn’t depend on the one person who remembers the whole chat. We’ll put stable rules in a short CLAUDE.md, keep campaign facts in separate notes and use Kabo for public references. The example is a ceramics launch, but the setup works for an agency, educator or small brand team.
Kabo, an AI agent for creator research, supplies public examples. Claude Code keeps those observations separate from the campaign facts and review instructions the next producer needs.
Prepare the materials for this Claude Code task
[ ] CLAUDE.md — Stable voice, evidence and review rules; keep it short. [ ] brief.md — Audience, campaign goal, deliverables and current constraints. [ ] verified-product-facts.md — Measurements and claims the maker has confirmed. [ ] approved-voice-examples.md — Real copy that sounds like the brand. [ ] research/ and drafts/ — Separate source notes from editable creative work.
Use the project brief for current goals and constraints. Keep source observations separate from creative proposals. Use verified-product-facts.md for our product claims. Put source links beside the claims they support. Do not invent measurements, customer stories or footage. Preserve the original draft and summarize substantive revisions.
2. Connect Kabo, then check the project context
Open the content project, install Kabo for Claude Code and complete sign-in. For a direct server connection, follow the setup guide.
3. Put stable rules where the project can reuse them
A small ceramics studio works with a freelance producer. Each product launch needs research, approved language and a filming brief that a second person can pick up without replaying the entire chat.
Create a concise project CLAUDE.md for lasting instructions, such as voice and evidence rules. Keep changing launch details in brief.md. Claude Code supports project instruction files, but those instructions do not supply missing product facts. Ask it to read the brief and repeat the scope before you let a promising creative angle become a factual claim.
Read CLAUDE.md, brief.md and verified-product-facts.md. Summarize the campaign and unresolved product questions. Propose a short plan naming the Kabo research question, review points and output files. Wait before drafting the campaign.
4. Plan one research pass before expanding the project
Ask for a short plan: the question Kabo will answer, the sources to inspect and the files to produce. Review whether the sample actually concerns studio ceramics rather than industrial product advertising. Once the scope is right, use ready public tools and retain dates and returned fields in the source index.
Keep “what is true about the mug” separate from “how we want to tell the story.” That makes a product correction a small edit instead of a debate about the whole campaign.
The Claude Code script workflow shows how a product correction can be traced through the opening, demo and recap.
Use Kabo to collect a small public reference set for [topic] within [dates]. Write research/source-index.md with URLs, dates and supported observations. Then draft one original product story in drafts/ with claim notes and a shot list. Use only verified-product-facts.md for our product claims. Add maker-review questions wherever a claim or shot remains unconfirmed.
5. Make the maker’s review a specific step
Ask Claude Code to draft one product story with claim notes and a shot list. Send the maker a document that identifies the statements needing approval, rather than a finished-looking script with uncertain facts hidden inside. Keep the research file and the creative proposal distinct so corrections do not erase the source record.
An example handoff another producer can understand
For a studio launch, one reviewed product story could become this production handoff:
- Campaign: Everyday mugs, explained through use
- Episode: Why this handle shape matters when you pick it up
- Owned proof: Film the actual mug and studio process.
- Research file: research/source-index.csv
- Approval needed: Maker checks product claims before filming.
- Draft: drafts/handle-story.md
6. Capture the revision as a project decision
After review, ask Claude Code to revise the affected passage and add a short decision note. Keep the reason, such as a handle claim being too broad or a kiln shot being unavailable. The next producer can then reuse the process while updating the campaign brief, rather than repeating every explanation in chat.
Replace “engineered for a perfect grip” with a description of the actual handle and a shot showing how the maker uses it. Keep any comfort claim pending maker review.
Hand over a project the next producer can reopen
Open the reviewed story in Google Docs for producer and maker feedback. Take the approved shot list to the studio, then use your normal editor for the footage. Project instructions help coordinate the work; they do not replace product review.
Leave the next producer one named open task: a research dossier, an idea decision or a campaign packet. Link the relevant file beside it.
Worked examples are illustrative. Product screenshots show existing Kabo web results, not a run of the example in this guide. Use your own materials and the evidence returned in your task.