Cindy Zhu.
← all free guides
Getting started Claude Code

How to master Claude in one weekend: the 9-step playbook

Hey, it's Cindy ๐ŸŒฑ This is the full weekend playbook: 9 steps to go from "I only use Claude in a browser tab" to running it like a real system. No coding anywhere. Everything here is real and current, checked on 2026-07-14, with a source link for each tool.

A browser tab is Claude's front door. Claude Code is where the real leverage is: reusable skills, plugins, connectors to your actual apps, and tasks that run on a schedule while you sleep. Here is the whole ladder, in the order I would do it over a weekend.

the setup

Step 1: get Claude Code ๐ŸŠ

Same Claude, way more it can do. It runs in your terminal, but you never write code, you talk and it does the work. Install it from claude.com/claude-code (there are one-click desktop installers for Mac and Windows), or on Mac/Linux paste this one line into your terminal:

curl -fsSL https://claude.ai/install.sh | bash

pick your surface

Step 2: use the right surface ๐Ÿ’ป

There is no single "right mode," just the right surface for the job:

๐Ÿ’ฌ claude.ai (browser) and Projects quick questions and organised chat workspaces.
๐Ÿ–ฅ๏ธ Claude Cowork agentic knowledge work (docs, decks, spreadsheets, across your apps) on desktop, web, and mobile, no terminal needed.
โšก Claude Code the full system, skills, plugins, MCP connectors, and automations. This is where this playbook lives.

stop retyping

Step 3: save your prompts as one-word commands โŒจ๏ธ

If you type the same setup ten times a week, save it once. In Claude Code you can save a reusable prompt and trigger it by name, like /script or /email (these are now part of Skills, see step 5). On a Mac you can do the same thing anywhere with System Settings, then Keyboard, then Text Replacement: type a few letters and your full prompt appears.


on a schedule

Step 4: make it run without you ๐ŸŒ™

Set Claude up as a routine and it runs on a schedule on Anthropic's cloud, even with your laptop closed. Wake up to a morning brief with your content numbers and your to-dos, set once, runs on repeat.

๐ŸŒ™ set a routine
/schedule
# then describe the task and pick daily / weekly, e.g.
# "Every morning at 7am, summarise yesterday's post performance and my top 3 to-dos."
โฐ Routines are a newer preview feature and need a Pro, Max, Team, or Enterprise plan with Claude Code on the web. This is the "teammate that doesn't sleep" level.

teach it your way

Step 5: add your first skill ๐Ÿ—ฃ๏ธ

A skill is a tiny SKILL.md file that teaches Claude one thing your way: your writing voice, your carousel format, your onboarding. Claude loads it on its own when your request matches. Start with a brand-voice skill, it is what stops your AI from sounding like everyone else's.


less is more

Step 6: add one plugin, not fifty ๐Ÿ”Œ

Claude Code has a plugin marketplace (an official one curated by Anthropic, plus a community one). Install a plugin with /plugin. Pick the one that matches what you do every week. One you actually use beats fifty you don't.


the connectors

Step 7: connect your real tools with MCPs ๐Ÿงฉ

An MCP is a connector that lets Claude reach into the apps you already live in. Add one with a single command:

claude mcp add

Real, current connectors include Notion, Gmail, Slack, Stripe, Google Drive, and even GoHighLevel. Now you can say "pull last week's numbers and drop them in my wins channel" and it just happens, no copy-pasting between tabs.


the two files

Step 8: the two files that do the heavy lifting ๐Ÿ“„

Drop these into your Claude Code project and they do more than 50 one-off prompts:

  • ๐Ÿ‘ค CLAUDE.md: who you are, what you do, who you sell to, what matters this week. Claude reads it at the start of every session, so you never re-explain yourself.
  • ๐Ÿšซ A style file: the words you never want it to use (like "delve," "dive into," "elevate"). It follows them reliably (it is strong guidance, not a hard lock).

scale it out

Step 9: make Claude work for your whole team ๐Ÿค

Give each project, client, or teammate its own folder with its own CLAUDE.md. Share the folder through version control (git) and anyone who opens it loads the same rules and context you do, so a VA or teammate gets consistent results without re-training. (Same rules and context, not literally identical outputs, since models are not deterministic.)


the schedule

The weekend order ๐Ÿ—“๏ธ

  1. 1๏ธโƒฃ Saturday morning: steps 1 and 2 (get Claude Code, learn the surfaces).
  2. 2๏ธโƒฃ Saturday afternoon: steps 3 to 5 (a saved command, one routine, a brand-voice skill).
  3. 3๏ธโƒฃ Sunday: steps 6 to 9 (one plugin, connect a tool, write your two files, share a folder).

Every link in one place ๐Ÿ”—

Want more like this? Follow @cindiezhu for daily AI you can actually use.