Hey friends,
Claude updates have been coming FAST lately.
Claude Cowork, Claude Code, Skills, Remotion, CLAUDE.md, Claude Design, Dispatch, Scheduled Tasks, Computer Use..
It’s a lot.
And when tools move this quickly, it’s easy to feel behind before you’ve even tried anything properly.
So instead of throwing five more features at you, I want to show you the order I’d actually set them up in if I was starting from scratch.
Because the point isn’t to know every Claude feature. The point is to make Claude useful for real work, the stuff that saves time, helps you create faster, supports your business, and moves your career or client work forward.
So here’s the Claude setup path I’d follow first.
And if Claude Cowork is the part you want to finally understand properly, I’m building Learn Claude Cowork in Cowork for non technical operators who want the setup, not just the theory.
It’s been an overwhelming response and I don’t want you to miss out! Sign up to the waitlist here.
📌 1. Give Claude Context First
One big mistake I see people make is starting from zero every time.
New chat, same audience, same tone, same project, same “please don’t make this sound like a LinkedIn robot” speech.
CLAUDE.md and Claude Design are useful for the same reason: Claude gets better when you stop making it guess.
CLAUDE.md gives Claude written context before it starts working: your audience, tone, rules, project details, and what “done properly” looks like.
Claude Design works the same way visually. Ask for “a modern landing page” and you’ll probably get something polished but generic. Give it your brand, website, screenshots, tone, examples, and design rules, and it starts to feel like yours.
For a creator, founder, or professional, this means Claude can understand your content style, brand, client context, standards, and what a useful finished output should look like before the work starts.
Try this first: create one simple context file with who you help, what you’re building, your tone, what good output looks like, what Claude should avoid, and which tools or folders it should use.
Pro tip: Keep it short. A useful one-page context file beats a giant messy one every time.
✨ 2. Turn Repeated Work Into Skills
Once Claude has context, ask: what do you keep doing over and over?
That’s where Skills become useful. I used this for my Instagram Carousel Skill and the Remotion Skill, but the same idea applies to any repeated workflow.
A Skill is basically a reusable playbook Claude can follow.
Instead of explaining your carousel format, launch video style, export settings, structure, or workflow every time, you make the process repeatable once.
A prompt helps once. A Skill helps every time.
Skills aren’t just “better prompts.” They’re how you turn your messy repeatable work into a system.
For creators, founders, and professionals, that could mean faster carousels, launch videos, client reports, research briefs, newsletters, or weekly summaries that follow your process every time.
Try this: pick one workflow you repeat often, like turning notes into posts, drafting newsletters, repurposing long form content, or formatting research.
Then ask Claude:
Turn this workflow into a reusable SKILL.md file.
Include:
- When this skill should trigger
- What inputs it needs
- The step-by-step process
- My style and formatting rules
- What the final output should include
- What to avoid
Pro tip: Start with a workflow you already understand. Skills work best when you’re teaching Claude a process you’ve already done manually.
⚡️ 3. Let Claude Handle The Work Around The Work
Claude Cowork is where this starts feeling less like “AI chat” and more like something that can actually help you get through the day. I wrote more about the core features here, but the short version is:
Dispatch lets you text Claude from your phone, Scheduled Tasks run recurring work, Projects give Claude a real folder as context, and Computer Use lets Claude control your Mac with permission.
These are useful because most people don’t need AI to write one fancy paragraph. They need help with the annoying work around the work.
Finding the right file, checking notes, preparing drafts, pulling context together, running the same weekly task, turning scattered ideas into something usable, and starting work before you’re back at your laptop.
That’s where the time saving part gets real. It’s not always one massive automation. Sometimes it’s 20 tiny handoffs you no longer have to babysit.
Here are the kinds of workflows I think non-technical people should actually care about:
✅ Weekly content prep
✅ Client or work summaries
✅ Launch prep
✅ Research clean up
That’s the kind of thing that saves real time because it removes the little bits of friction that slow everything down.
🛠 The Setup I’d Try This Week
If you’re catching up and don’t know where to start, here’s the order I’d follow:
- Make one context file: Start with CLAUDE.md
- Connect one real work folder: Content, clients, research, or projects
- One repeated workflow: Pick something you do weekly
- Schedule one recurring task: Automate something annoying
- Use Claude Design with brand context: Give it your website, screenshots, colours, and examples before asking for assets.
That’s enough.
You don’t need to master every Claude feature this week. Just pick one workflow that currently costs you time, energy, or money, and make Claude better at that.
That’s the exact kind of workflow I’ll be breaking down inside Learn Claude Cowork in Cowork, taught from inside Cowork itself. Sign up to the waitlist here!
🫡 Final Thoughts
The more I use Claude, the more I care about the setup around it: the context, files, folders, Skills, recurring tasks, and design rules.
Pick one setup from this email and try it this week.
Not five. One.
Make a context file, build a Skill, schedule a task, or give Claude Design your brand system before your next prompt.
To AI that actually helps you finish the work,
Nahid
