Master Implementers Workshop

Claude-Maxxing Cheat Sheet

Every Claude concept explained simply. Ordered by what matters most for your business. No jargon. No fluff.

Why Most People Get Generic AI Outputs

The difference between "meh" and "magic" is not skill. It is setup.

😶

Without Setup

Every conversation starts cold. Claude does not know your business, your voice, or your audience. You get generic, one-size-fits-all answers.

With Setup

Claude already knows who you are, how you talk, who you serve, and what you are working on. Every response feels tailored to you.

3 Versions of Claude

Claude comes in three flavors. You only need to care about the first two.

Version 1

Claude Chat

The web and mobile app at claude.ai. You type, Claude responds. Great for writing, brainstorming, research, and answering questions. This is where most people start and where you will set up your Master Prompt and Projects.

Best for: Quick conversations, writing, research
Version 2

Claude Cowork

The desktop app with superpowers. Can access files on your computer, connect to your apps (Gmail, Calendar, Drive), run tasks in the background, and work while you sleep. This is where Claude becomes your assistant, not just a chatbot.

Best for: Getting real work done automatically
Version 3

Claude Code

A command-line tool for software developers. It reads entire codebases and writes code across multiple files. If you are not a developer, you can completely skip this one.

Best for: Developers only

The 3 Levels of Claude Usage

Most people are stuck at Level 1. Your job is to move to Level 2 and then Level 3.

Level 1

Chat

Using Claude like a search engine. One-off questions, one-off answers. Every conversation starts from scratch.

You need: A free Claude account
Level 2

Context

Claude knows your business, your voice, your offers, and your audience. Every conversation starts warm, not cold.

You need: A Master Prompt + a Claude Project
Level 3

Operating

Claude runs workflows for you. Content, campaigns, follow-ups, briefings, client work. It does the work, not just answers questions.

You need: Projects + Skills + Connectors

Essential Concepts

These are the foundations. Set them up once and every conversation gets better.

Must Know
1

Projects

Chat + Cowork

Separate brains inside Claude. Each project has its own memory, instructions, and conversations. Create one for "My Business", one for "Content", one for "Personal". They keep everything organized so your business context does not bleed into your personal stuff.

Marc's Pro Tip: Create separate projects like "My Business," "My Life Coach," and "My Health." Each one gets 2-3 key documents uploaded (offer page, about page, or a doc describing the context). Keeps everything clean and separated.
2

Project Instructions

Chat + Cowork

A set of rules that tells Claude how to operate inside a specific project. It loads automatically at the start of every conversation. Claude already knows your rules, preferences, and context without you repeating yourself. In Cowork this is called the CLAUDE.md file. In Chat, it is just "Instructions" inside your project settings.

Marc's Pro Tip: Upload your documents into the project first, then inside the project chat, paste: "I want to create a set of project instructions so you produce quality outputs personalized to me moving forward. Ask me questions before you draft the instructions." Let Claude interview you. Then paste the result into Instructions.
3

Custom Instructions (Global)

Chat + Cowork

Your permanent identity across ALL of Claude. These apply everywhere, in every project, every conversation. Unlike project instructions (which only apply to one project), global instructions follow you into everything.

Marc's Pro Tip: Treat this like a lightweight version of project instructions — keep it short and focused on identity (who you are, how you want Claude to respond, your hard never-dos). Save the deep business context for project-level instructions where it belongs.
4

Memory

Chat + Cowork

How Claude remembers things about you over time. It picks up patterns from your conversations and stores important details. The more you use Claude, the better it gets. You can also tell it directly to remember something. Think of it as Claude building a profile of you conversation by conversation.

Marc's Pro Tip: Make this a weekly task. Every Friday, paste: "Look at my memory, my instructions, and my documents. What would you refine or make better so you create higher-quality output moving forward without so much back and forth?" Then clean up based on what it says. More details in the Save Usage section below.
5

Connectors

Cowork

Bridges between Claude and the apps you already use. Google Calendar, Gmail, Google Drive, Notion, Slack, Stripe, and 30+ more. Instead of copy-pasting information into Claude, it reaches into your tools directly and pulls what it needs, or takes action for you.

Marc's Pro Tip: Before assuming a tool does not connect, ask Claude directly: "Is there any MCP connector for [tool name]?" If there is no native connector, you can also use Zapier as a bridge — it covers a lot of apps Claude does not support directly yet.
6

Web Search

Chat + Cowork

Claude can search the internet for live, up-to-date information. Useful for research, competitor analysis, trending topics, and anything recent. Just ask and it searches automatically. No special setup needed.

Marc's Pro Tip: Web search tends to work best inside Claude Chat. For the deepest research, Claude Code is actually the strongest — but it uses more credits and takes longer. Pick your battles.
7

Artifacts

Chat + Cowork

Visual outputs that go beyond plain text. Claude can generate dashboards, slide decks, charts, interactive tools, and more. You can view them right inside Claude and open them in your browser. This is one of the things that makes Claude feel like magic.

Marc's Pro Tip: To publish an artifact online with zero setup, publish it directly from Claude Chat. For a real website, use Vercel with Claude Code — it is free, fast, and the quality is next level. This very cheat sheet you are reading? Built in Marc's workspace folder and deployed the same way. After your first deploy, say "Save this as a skill" so the next deployment takes seconds.
8

Workspace Folder

Cowork

A folder on your computer where all your Cowork files live. Every file Claude generates (documents, scripts, dashboards) is saved here. Think of it as Claude's filing cabinet. You can access it from Finder/Explorer at any time. (Fun fact: this entire cheat sheet was built inside Marc's workspace folder — which is, honestly, his biggest organizational weakness. Ironic.)

Marc's Pro Tip: Not a natural organizer? Same here. Ask Claude: "Analyze all the folders in my workspace and help me categorize everything properly." Also, create an /Archive folder — any file you think you do not need anymore, ask Claude to move it there. Review once a month and delete what you truly do not need. Way safer than deleting on the spot.
9

Files & Knowledge

Chat + Cowork

You can upload documents directly into a project as "knowledge." Your offer page, your client onboarding doc, your pricing breakdown, your best blog posts. Claude reads these and uses them as reference every time you chat inside that project. This is how Claude learns the specifics of YOUR business, not just what you tell it in instructions.

Marc's Pro Tip: Upload Markdown (.md) or plain text files when you can — they load instantly. PDFs and Docs work, but Claude sometimes has to re-fetch them, which is slower. Every so often, ask Claude: "Review my project, my chats, and my documents. What should I tighten up to get better output and save on usage?"
10

Styles

Chat

Built-in presets that change how Claude writes. You can choose from styles like "Formal", "Concise", or "Explanatory" — or create your own custom style by giving Claude examples of your writing. Custom styles are powerful because Claude matches your voice without you having to explain it every time.

Marc's Pro Tip: Honestly? Just stick with the default. If your project instructions are solid, you rarely need to touch this. Skip unless you have a specific writing voice you want to lock in.

Power Features

Once you have the essentials down, these features multiply your results.

Worth Learning
11

Skills

Cowork

Pre-built workflows that tell Claude HOW to do a specific task the way you want it done. Instead of explaining how you want something done every time, you teach Claude once and it follows that same process forever. One command triggers an entire workflow. Skills live in Cowork but you can also trigger them inside Claude Chat projects.

Marc's Pro Tip: After any task you know you will repeat, say "Turn this into a skill." Claude packages the whole process so next time it is one command. Bonus: ask friends to send you their skills — Marc is happy to share his too. Skills are meant to be passed around.
12

Plugins

Cowork

Bundles of skills packaged together for easy sharing and installation. Instead of creating 20 skills one by one, you install a plugin and get them all at once. Anthropic has built-in plugins for marketing, legal, design, and more. You can also create and share your own.

Marc's Pro Tip: Honestly, Marc does not build his own plugins. But they are a great way to RECEIVE other people's skills in one package. If someone shares a plugin with you, install it — you just inherited a whole workflow library for free.
13

Scheduled Tasks

Cowork

Automations that run without you. Daily briefings, weekly reports, content calendars. You tell Claude what to do and when, and it just runs on schedule. This is where Claude starts replacing tools like Zapier. For example: a daily community scan, or a weekly email performance report.

Marc's Pro Tip: Set it up once and it runs forever. Just remember: your computer needs to be ON and awake for it to trigger. You can also talk to Claude online or trigger tasks remotely to make him do things for you while you are out and about.
14

Slash Commands

Cowork

Trigger words that start a skill with a single command. Type /morning-briefing and the entire workflow runs. Type /carousel and it starts your carousel creation process. It is just a shortcut to trigger your skills faster.

Marc's Pro Tip: Type / in the Cowork chat to see every slash command available. Fastest way to remember which skills you have set up.
15

Claude in Chrome

Cowork

A Chrome browser extension that lets Claude interact with websites for you. It can fill out forms, click buttons, pull information from web pages, and navigate sites. Think of it as giving Claude hands inside your browser. Useful for apps that do not have a connector yet.

Marc's Pro Tip: Use this as the fallback when a tool has no native connector and no MCP. Install once, then ask Claude to pull info or fill forms directly in the browser.
16

Multimodal

Chat + Cowork

A fancy word for "Claude can see things." It can read images, screenshots, charts, PDFs, not just text. Upload a photo of your whiteboard notes and Claude can read them. Screenshot a competitor's landing page and ask Claude to analyze it.

Marc's Pro Tip: Screenshot competitor posts, sales pages, dashboards — anything visual — and ask "What can I learn from this?" Faster than describing what you are looking at.

Advanced Concepts

You do not need these on day one. But knowing they exist means you know where you are heading.

Good to Know
17

Context Window

Think of this as Claude's desk. Every conversation has a limited amount of space. Your instructions, memory, files, and conversation history all take up space on that desk. Currently Claude can handle about 1 million tokens (roughly 700,000 words). If your conversation gets very long, Claude may need to summarize older parts to keep working.

Marc's Pro Tip: When a chat gets long and you want to save usage, paste: "Help me compact our entire conversation with a focus on [topic X and Y] so I can paste this into a new chat." You choose what to focus on so nothing important gets lost, then start a fresh chat with the summary.
18

Extended Thinking

When you give Claude a complex problem, it can take extra time to think through it carefully before responding. Like asking someone to take their time. The answer takes longer but comes out better.

Marc's Pro Tip: Uses more credits than normal responses, so save it for the stuff that actually matters — strategy calls, big decisions, deep analysis. It is slow, but it gets sharper answers. Speed will improve over time.
19

Computer Use

Claude can actually use your computer, not just your browser. It can open apps, click through menus, and interact with desktop software. Still early stage and slower than connectors, but it handles edge cases where no connector or Chrome extension exists.

Marc's Pro Tip: Last resort. Use connectors first, Chrome extension second, computer use only when nothing else works.
20

Dispatch Mode

Control Claude on your desktop computer from your phone. If you are out and need Claude to grab a file, run a task, or check something, Dispatch lets you trigger it remotely. Like a remote control for your AI assistant.

Marc's Pro Tip: Your computer must be ON and awake for Dispatch to work. Close your laptop lid and it stops. Leave your desktop powered on before you head out if you plan to run tasks remotely.
21

Sub Agents

Parallel workers that handle complex tasks by splitting the work. Give Claude a big request and it breaks it into parts: one agent does research, another writes copy, another builds a dashboard. All at the same time. Claude usually triggers this automatically when a task is complex enough.

Marc's Pro Tip: If something feels slow or complex, you can nudge it: "Create sub agents so you can make this faster." Usually works — most of the time Claude already handles this on its own.
22

Bash Tool

How Claude runs code behind the scenes in Cowork. When you ask it to resize images, process a CSV, or generate a report, it writes and runs code automatically. You never see or touch the code.

Marc's Pro Tip: Honestly, ignore this one. You do not need to think about it — just ask Claude to do the thing and it handles the technical work on its own.

Best Practices

Tips that separate people who dabble with AI from people who run their business with it.

Prompting

1

Give context before tasks

Do not just say "write me a caption." Say "I am a business coach for consultants. I just ran a workshop on pricing. Write me an Instagram caption sharing one takeaway." The more context, the better the output.

2

Show examples of what "good" looks like

Paste 2-3 examples of posts, emails, or copy you love. Say "Write in this style." Claude mirrors patterns better than it follows abstract descriptions.

3

Iterate, do not restart

If the first response is 70% there, say what is wrong and ask Claude to fix it. "Make it punchier." "Remove the fluff." "Make the hook stronger." Do not start a new conversation. Build on what you have.

4

Use "respond as if" framing

"Respond as if you are a copywriter who has written 500 landing pages." "Respond as if you are my business coach." This shifts the quality of reasoning Claude applies.

Organization

5

One project per domain

Create separate projects for business, content, personal, and client work. Do not dump everything into one project. Your business voice should not mix with your personal journaling.

6

Keep project instructions under 1,500 words

Long instructions get diluted. Focus on: who you are, who you serve, your voice and tone, your rules, and what Claude should never do. Quality over quantity.

7

Review memory monthly

Claude builds memory over time but it can get stale. Once a month, check what it has stored. Remove anything outdated. Add anything important it missed.

Workflow

8

Build skills from things you repeat

If you do the same task more than 3 times (weekly emails, social posts, client onboarding), turn it into a skill. The time you invest once saves hours every week.

9

Start with connectors, not computer use

Connectors (Google Calendar, Gmail, Drive) are fast and reliable. Chrome extension is the backup. Computer use is the last resort. Work your way up, not down.

10

Schedule your highest-value tasks first

Your morning briefing. Your daily content scan. Your weekly report. Start with 1-2 scheduled tasks that save you the most time, then expand from there.

Claude Setup Audit

Run through this checklist to make sure your Claude is set up for maximum results.

Foundation Check

  • Do I have global instructions set up with my identity?
  • Do I have at least one project with clear instructions?
  • Are my project instructions specific (not vague)?
  • Has Claude stored accurate memories about me?

Context Quality

  • Does Claude know my audience?
  • Does Claude know my offer and pricing?
  • Does Claude know my voice and tone?
  • Have I uploaded key business documents?

Connections

  • Is my Google Calendar connected?
  • Is my Gmail or email connected?
  • Is Google Drive or cloud storage connected?
  • Are any other daily tools connected?

Automation

  • Do I have at least one skill I use regularly?
  • Do I have at least one scheduled task running?
  • Am I reusing skills instead of re-explaining tasks?
  • Am I reviewing Claude's outputs, not just accepting them?

Reduce Your Usage Cost

The one thing to understand: Claude does not count messages. It counts tokens. Every time you send a new message, Claude re-reads your ENTIRE conversation history before replying. Message 30 costs roughly 31x more tokens than message 1. Once you get that, everything below makes sense.

$

Edit instead of sending follow-ups

When Claude gets it wrong, do not send "no I meant THIS" as a new message. Click edit on your original message, fix it, and regenerate. The old exchange gets replaced, not stacked on top.

$

Start fresh every 15-20 messages

Before you do, ask Claude to summarize everything, copy the summary, open a new chat, and paste it as your first message. You keep the context without the token bloat.

$

Batch questions into one message

Three separate prompts means three full context reloads. One prompt with three tasks means one reload. The answers usually come out better too because Claude sees the full picture upfront.

$

Use Projects for recurring files

If you find yourself uploading the same documents into multiple chats, upload them once into a Project instead. Every new conversation inside that Project references them without burning tokens again.

$

Save your preferences in Memory

If you keep repeating the same setup — your role, your style, your preferences — save it once in Settings. Claude applies it automatically from that point on. Stop paying for re-introductions.

$

Use the right model for the task

Haiku for grammar checks, brainstorming, formatting, quick translations. Sonnet for real work. Opus for deep thinking. Matching the model to the task frees up 50-70% of your budget for the stuff that actually needs heavy lifting.

$

Spread usage across the day

Claude uses a rolling 5-hour window, not a midnight reset. If you use everything in one morning session, most of your daily capacity goes unused. Working in 2-3 blocks across the day gives you significantly more total usage.

$

Upload Markdown, not PDFs

PDFs and Word docs take more processing to read. Plain text or Markdown (.md, .txt) files are lean and load instantly. Before uploading a PDF, ask Claude to "Convert this to a clean Markdown file" and upload that version instead.

The Claude Usage Audit Prompt

Paste this into any Claude chat and it will audit how you use Claude, then give you a personalized action plan to stop hitting limits. Works standalone or inside a project.

You are a Claude Usage Auditor. Your job is to analyze how I use Claude and give me a specific, prioritized action plan to reduce my token consumption so I stop hitting usage limits. First, if we are inside a Project, review my Project Instructions and Knowledge Files and flag anything bloated, duplicated, or rarely used. Then interview me one or two questions at a time. Wait for my answers before moving on. Adapt based on what I tell you. Ask me about: 1. How many messages does a typical conversation go before I start a new one? 2. When you get something wrong, do I send a new message or edit the original and regenerate? 3. Do I ask one question per message, or batch multiple tasks into one? 4. Do I upload the same documents into multiple different chats? 5. Do I often re-introduce myself, my role, and my style at the start of chats? Or is it saved in Memory? 6. Do I switch between Haiku, Sonnet, and Opus based on task complexity, or use the same model for everything? 7. Do I have Web Search, Extended Thinking, or Connectors on by default? 8. Do I use Claude in one long session or spread it across the day? 9. How many Projects do I use for recurring work? 10. What is my biggest pain point around hitting limits? After gathering my answers, produce a report with: # Your Claude Usage Health Report ## Overall Score: X/100 ## Category Breakdown (score each /10) - Conversation Management - Prompt Efficiency - Project & File Setup - Memory & Preferences - Model Selection - Feature Management - Usage Timing ## Your Top 3 Quick Wins The 3 specific changes with the biggest immediate impact. Tell me exactly what to do, step by step. ## Detailed Recommendations For each category scored below 7: what is costing me tokens, exactly how to fix it, and rough percentage of tokens saved. ## Token Math A simple before/after estimate of my daily token burn using the quadratic formula: Total ≈ S × N(N+1) / 2, where S = avg tokens per exchange and N = message count. ## Your 7-Day Action Plan - Days 1-2: Quick wins under 5 minutes each - Days 3-4: Setup changes (Projects, Memory, file organization) - Days 5-7: Habit changes (batching, model switching, session timing) Key principles to use in your recommendations: - Token cost grows quadratically with conversation length - Rolling 5-hour window, not a midnight reset - Haiku/Sonnet/Opus cost dramatically different amounts - Project knowledge files are cached, individual chat uploads are not - Every active feature (Web Search, Extended Thinking, Connectors) adds tokens even when unused - Editing original messages beats sending follow-ups - Specific prompts beat vague prompts (better first responses mean fewer follow-ups) - Memory and saved preferences eliminate repeat setup Be direct and practical. No fluff. Explain everything as if talking to a smart person who is not technical. Use simple math and concrete examples.

The Master Prompt

Two copy-paste prompts. One for business. One for life. Do not overthink it.

What is a Master Prompt?

A Master Prompt is the document Claude reads FIRST every time you talk to it. It teaches Claude who you are, what you do, how you talk, and what you want help with — so you never have to re-explain yourself. You build one for your business and one for your life. Paste each into the Instructions of its own project. That is it.

How to use these: Create a project (one for business, one for life), paste the prompt below into the project chat, answer Claude's questions, then paste the final result into the project Instructions.

Business Master Prompt

Paste this into your "My Business" project chat. Claude will interview you, then hand you a finished Master Prompt to save as your project Instructions.

I want you to help me build a complete Business Master Prompt that I will use as my project instructions moving forward. Your job is to interview me one topic at a time, then at the end give me a clean, finished document I can copy and paste. Before you start, ask me to upload any documents I already have that could make your job easier — my offer page, my about page, old content, a pitch deck, anything. Use whatever I give you as context. Then ask me questions about each of these areas, one at a time, and wait for my answer before moving to the next: 1. Who I am (name, role, company, where I am based) 2. What I do (my one-liner, who I serve, my main offer) 3. My ideal client (who they are, how they feel, what they want, what they struggle with) 4. My offers and price points, and my enrollment path 5. My voice and tone (warm? punchy? casual? signature phrases I use?) 6. My hard rules (things you should NEVER do when writing for me — hype, cliches, fake stats, etc.) 7. Current season (what I am focused on this quarter, my bottlenecks, my priorities) 8. My credentials and proof points (weave in subtly, never braggy) After I have answered everything, compile it into a clean, well-structured Master Prompt document with clear headings. Then audit your own draft: review the final document and tell me what is still weak, unclear, or missing. Ask me follow-up questions to tighten anything that could be sharper. Only after that, give me the final version with instructions on exactly where to paste it.

Life Master Prompt

Paste this into your "My Life" project chat. Same flow — Claude asks, you answer, you get a finished document.

I want you to help me build a complete Life Master Prompt that I will use as my project instructions moving forward. Your job is to interview me one topic at a time, then at the end give me a clean, finished document I can copy and paste. Before you start, ask me to upload any documents I already have that could make your job easier — journal entries, life plans, health reports, financial snapshots, goal sheets, anything. Use whatever I give you as context. Then ask me questions about each of these areas, one at a time, and wait for my answer before moving to the next: 1. Who I am (name, age, where I live, current life season) 2. My family (partner, kids, parents — who is important and what matters about them) 3. My health (current state, goals, supplements or training I do, anything to watch out for) 4. My finances (rough picture, goals, how I like to think about money) 5. My values and non-negotiables (what I will never compromise on) 6. My routines (morning routine, weekly rhythms, how I recharge) 7. My goals for this year and this quarter 8. How I want you to coach me (challenging? gentle? direct? ask questions instead of giving advice?) After I have answered everything, compile it into a clean, well-structured Master Prompt with clear headings. Then audit your own draft: review the final document and tell me what is still weak, unclear, or missing. Ask me follow-up questions to tighten anything that could be sharper. Only after that, give me the final version with instructions on exactly where to paste it.

The gap between generic AI and AI that actually runs your business is not skill. It is setup. Set it up right, and Claude goes from a chatbot to a business partner.