In 2 hours you'll build a living content platform your team uses the next day. Not slides. Not theory. Real tools you keep.
Updated: March 22, 2026
This workshop is how I actually work. Every day.
"Don't use passive voice." Twenty-two times. One sprint. My own style guide was 40 pages. Nobody had read it.
Written over 3 weeks. Read by approximately zero people on the team.
"Click here" → "Get started." Every single feature. Every single quarter.
1 content designer. 4 product teams. Things always slip through.
They paste copy. Get feedback in 5 seconds. Based on your rules. No style guide. No asking you.
Real URL. Team opens it in any browser. No setup on their side.
Knows your voice rules. Gives feedback in your language.
Every review is logged. Run /learn weekly. System improves automatically.
We're building live tomorrow. If these aren't set up, you'll fall behind in the first 10 minutes.
Open your Terminal and run:npm install -g @anthropic-ai/claude-code
Then type claude to authenticate.
Full setup docs →
Go to github.com/signup
Free account. Use your work email.
This stores your project — every change tracked.
Go to vercel.com/signup
Click "Continue with GitHub."
Free. This deploys your tool to a live URL.
Accounts alone aren't enough. You need them talking to each other.
Don't wait until tomorrow. If anything isn't working, reach out now in our Slack channel and I'll help you get unstuck.
#cohort-5-march-23
Post your question there. I'll reply within hours.
Reply to the workshop email.
I'd rather spend 5 min now than lose workshop time fixing installs.
Open Claude Code. Type this:
The file Claude reads before every command. Your voice & tone doc, but active, not static.
That last section is the learning hook. We activate it in Layer 4.
Paste it in, even a paragraph. Claude Code extracts the rules.
Use the template in the starter kit. 6 example rules, customize in 5 minutes.
Something sounds off? That's a CLAUDE.md gap. Fix it in 30 seconds:
A markdown file that defines the review process step by step.
Obsidian is a free note-taking app that stores everything as simple text files on your computer. No accounts, no cloud lock-in. Claude Code reads these files directly — that's what makes it powerful.
Every review is saved as a log file inside your Obsidian vault. After 30 reviews, patterns emerge.
| Copy submitted | Verdict | Violation | Rewrite |
|---|---|---|---|
| "Click here to get started" | FAIL | Passive CTA | "Get started" |
| "Your file was unable to be saved" | FAIL | Passive + blame | "We couldn't save that. Try again." |
| "Start your free trial" | PASS | — | — |
After 30+ reviews, run /learn. Claude reads the log, extracts patterns, writes new rules to memory.md.
A web page. A text box. A button. That's all your team sees.
Claude Code writes the full file. You open it in a browser. Test it. If something's wrong, tell Claude in plain English. Done in 30 seconds.
They don't know Claude is behind it. They don't need to.
Open your index.html. Enter your Claude API key once. Paste something from your own product. something you know has a problem.
"I walked in with a Notion doc nobody reads. I walked out with a tone checker my entire team opened on Monday morning."
Sarah K., Senior Content DesignerShare your result in chat. What did it catch?
Everything you built lives locally. Time to make it live for your team.
This is the cycle forever. You never redeploy manually again.
Send this to your team right now:
"Before asking me about copy, try this:
your-content-system.vercel.app
Paste the copy. It'll tell you if it works and why."
No training. No onboarding doc. The tool explains itself.
After a week of team usage, run one command:
Your team wrote all of this through usage. You didn't write a single line manually.
| Layer | What you built | What it does |
|---|---|---|
| CLAUDE.md | Voice & tone rules | Claude knows your brand |
| Skill file | Tone review pipeline | Reviews run automatically |
| index.html | Team web interface | URL, no Claude Code needed |
| Obsidian vault | Your content system home | All files, logs, and rules in one place |
| memory.md | Learned patterns | Gets smarter with usage |
| GitHub + Vercel | Deployment pipeline | Push once → live for everyone |
"This approach shifts content design from writing individual strings to designing the rules that govern them."
Nathan Beddows, Content & UX Professional
One job this week:
Send the URL to one teammate.
Say: "Try this before asking me about copy."
When they use it → it logs the review.
When you run /learn → system gets smarter.
By month two, it knows your product better than your onboarding doc.
Everything you learned today applies to these, they're just more layers on the same system.
Writer → Editor → Reviewer in sequence. One command, three passes of review.
Auto-check copy before every PR. No manual step. Standards enforced at the code level.
What the system learns in one product teaches another. One memory.md, many tools.
Next workshop: Building multi-agent content pipelines with Claude Code.
Ask anything about what you built, what comes next, or how to extend this for your team.
In your inbox within 24 hours.
All files yours to keep and modify.
SETUP.md, 6 steps from zero to deployed URL.
Post your URL when you deploy. Let's see what you built.
Write about your new AI content agent. What it does. How you built it in 2 hours. Tag me — it would mean the world.
linkedin.com/in/yuvalkesh