Stop writing guidelines.
Start building systems.
Workshop Details
- 🇮🇱 Israel (IDT) — 4:00 PM
- 🇩🇪 Germany (CEST) — 3:00 PM
- 🇬🇧 UK (BST) — 2:00 PM
- 🇺🇸 US East Coast (EDT) — 9:00 AM
- 🇺🇸 US West Coast (PDT) — 6:00 AM
- A laptop and internet connection
- An active Claude Code license (required to participate)
- Your brand's voice & tone docs (or use our template)
Your content guidelines are great. Nobody uses them.
You spent weeks writing voice and tone docs. They sit in Notion. Designers still ask "what should this button say?" Your team keeps shipping inconsistent copy.
This workshop fixes that. In 2 hours, you'll set up Claude Code, create voice & tone guidelines that actually work, and build a real content platform your team can use the next day.
Not slides. Not theory. Working tools you build and keep.
Who you are before vs. after
"This approach shifts content design from writing individual strings to designing the rules that govern them." — Nathan Beddows, Content & UX Professional
Sound familiar?
📄 Docs nobody reads
Your style guide has 40 pages. Your team reads zero of them. Every new feature starts from scratch.
🔁 Same feedback on repeat
You've corrected "Click here" to "Get started" fifteen times this quarter. It keeps coming back.
⏳ No time to scale
You're one content designer covering 4 product teams. You can't review every string. Things slip through.
Your system has 4 parts. Here's what each one does.
By the end of the workshop you'll have built all four. Together they form a content system that runs without you in the room.
Claude.md — The Brain
A markdown file that holds your voice, tone rules, and brand standards. This is what the system thinks with. Every skill you build reads from it.
Skills — The Actions
Reusable commands built on top of the brain. Run /tone-checker on a piece of copy. Run /microcopy-gen to draft button labels. You design the skill once. It works forever.
Memory.md — The Learning Loop
A log file the system updates automatically. Every correction, every query, every edge case gets stored. Your system gets smarter the more your team uses it.
Web Interface — The Share Link
Deploy your tool as a live URL. Your team opens it in a browser — no terminal, no setup on their end. You can also connect it to Slack so it runs where they already work.
How the 2 hours work
You follow along and build it live. Each step produces something real. By the end, all four parts exist on your machine.
Set up Claude Code + build the architecture
Install Claude Code, then use plan mode to scaffold the project — folders, base files, the initial Claude.md skeleton. If you can copy and paste, you can do this step.
Train The Brain
Load your existing style guide into Claude.md. Got a PDF? A Notion doc? A web page? We pull it in and structure it into voice rules, tone principles, and microcopy standards the system can enforce.
Build your first Skill + set up the Learning Loop
Design a /tone-checker command that reviews copy against your brain. Then set up Memory.md so the system logs every correction and gets smarter over time. This is where the tool stops being a demo and starts being yours.
Deploy and share
Connect to GitHub for backup, then push to Vercel. Your tool gets a live URL. Share it in Monday's standup. Your team uses it the same day — no install, no terminal, just a link.
What you leave with
Claude Code — fully set up
- Installed, configured, and ready to use
- You'll know how to talk to it and what it's good at
- A workflow you can repeat for any project
Voice & tone system
- Not a Google Doc — a system that checks copy automatically
- Built on your actual brand guidelines
- Gives feedback in seconds, not days
A content platform you built
- A working tool — deployed and shareable
- Your team can use it the same day
- Tone checker, microcopy generator, or something custom
Full recording
- Missed something? Rewatch anytime
- Step-by-step setup guide included
- Voice & tone template to customize
What people are saying after watching Yuval work
"What struck me most is that this approach shifts content design from writing individual strings to designing the rules that govern them."
Yuval ran a short 30-minute session demonstrating how a content design system can be prototyped using Claude Code. Within minutes he had a working framework that included voice-and-tone references, UX microcopy rules, a content pipeline that evaluates requests against the system, and automated checks for consistency.
It doesn't replace content designers… but it does suggest a future where we spend less time policing rules and more time designing systems.
What they posted after
Unprompted. On LinkedIn. The day after the workshop.
"I talked with Yuval Keshtcher on the critical role of strategic UX research and why skipping it is like guessing directions in an unfamiliar city. We also dive into the importance of making organizations human-centered."
"Within minutes Yuval had a working framework that included voice-and-tone references, UX microcopy rules, a content pipeline, and automated checks for consistency. This shifts content design from writing individual strings to designing the rules that govern them."
"Huge thanks to Yuval for being incredibly thorough, detail-oriented, and genuinely responsive. The level of care made a complex topic feel grounded and actionable. Highly recommend to anyone at the intersection of UX writing, content design systems, and AI."
"I left genuinely blown away by Claude AI's capabilities. Instead of just talking about possibilities, Yuval showed how AI can actually be structured into systems that support real content design work. I'm leaving with a different perspective on how content designers can build smarter systems with AI."
"Yuval built a working content tool with Claude Code that used his voice & tone guidelines and related content standards. Seeing it in action in real time was powerful. I recommend looking into his workshop if you're a UX writer, content designer, or content strategist ready to create something similar for your team."
⚠️ The field is splitting — right now
Content designers are dividing into two groups: those who write strings, and those who build systems. The system builders are shipping 3x faster, covering more product teams, and becoming harder to replace.
The tools exist today. The workshops are happening. Your peers are building. The question is whether you walk into your next review with the same workflow — or with something your team can't stop using.
Who this is for
You don't need to know how to code. You need to know what your team needs.
✏️ UX content designers
You write microcopy and manage content guidelines. You want to turn those guidelines into tools that work without you in the room.
🏗️ Design system leads
You manage design systems and need content tokens, voice checkers, and copy tools that scale across products.
📋 Content strategists
You set the rules. Now you want to make those rules run automatically — so your team doesn't need to memorize a 40-page doc.
Workshop Instructor
Yuval Keshtcher
Yuval runs the UX Writing Hub, trained 1,000+ content designers through the UX Writing Academy, and hosts the Writers in Tech podcast. He builds content systems with Claude Code for real product teams every day. This workshop is how he actually works.
What's included
Three things most workshops don't give you
Free setup session
Before the workshop, we run a group setup session so you show up ready to build — not troubleshooting. Claude Code installed, project scaffold ready, style guide prepared.
Free follow-up implementation session
Two weeks after the workshop, we meet again as a group. Stuck on deployment? Want to add a second skill? Need to adapt your system for a new product? We work through it live.
Alumni community access
Join the group of content designers who've built these systems. Share what you shipped. Ask questions. See what others are building. The people in this group are the ones doing it, not just talking about it.