06-reference

coreyganim cowork starter pack

Mon Mar 30 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·article ·source: x.com/@coreyganim ·by Corey Ganim
claude-coworksetup-guidecontext-filespluginsskillsworkflowsscheduled-tasksonboardingconsulting-reference

Claude Cowork: Ultimate Starter Pack for 2026

Corey Ganim (@coreyganim), published March 31, 2026. A condensed, opinionated onboarding sequence for Cowork — focused on the right order of operations. The central claim: most people set up Cowork backwards and get mediocre results. Fix the sequence, fix the results.

Ganim runs “Build With AI” (a community/course at skool.com/buildwithai) and uses this guide as the practical foundation for that program.

The Core Insight: Order of Operations

Most people install plugins first. That’s backwards.

Cowork doesn’t know who you are, what you do, or how you communicate. Without context, every plugin output is generic. The correct sequence is:

  1. Context files
  2. Meta-prompt (global instructions)
  3. One workflow
  4. Plugins
  5. Scheduled tasks
  6. Weekly review loop

Each step compounds on the previous. Skip the order, lose the compounding.

Step 1: Context Files Before Plugins

Create three markdown files in your workspace folder before installing anything:

Point Cowork at a folder containing these files. Now every response is personalized before you install a single plugin.

Time investment: 30 minutes. Payoff: every interaction from this point forward.

Step 2: The Meta-Prompt (Global Instructions)

Before running any task, prime Cowork with a global instruction that:

Ganim’s recommended language (paraphrased): confirm the working folder, review context files, propose a plan and wait for approval before taking action, default to [preferred format], never delete files without explicit confirmation.

Save this as a global instruction so you never type it again.

Step 3: One Workflow, Not Five

The most common failure mode: install Cowork, try to automate everything on day one (morning dashboard, meeting prep, content system, email summarizer — all the same afternoon). Two days later: abandoned all of them.

The fix: pick one recurring task that takes 20+ minutes and build that workflow first. Run it for a full week. Refine it. Then add the second one.

Ganim’s recommendation for first workflow: meeting prep.

A meeting prep workflow that runs automatically before every call — pulling calendar context, researching attendees, flagging prep needs — saves more time than any other single workflow. And it’s the one that makes you look prepared without doing any prep yourself.

Step 4: The Folder Structure That Scales

Flat folders break at scale. Ganim’s recommended structure:

Claude-Workspace/
├── context/              # about-me.md, brand-voice.md, current-projects.md
├── projects/
│   └── [project-name]/
├── successful-examples/  # ← most people miss this
└── outputs/

The successful-examples/ folder is the most underrated part of this setup. Drop your 5–10 best emails, highest-performing LinkedIn posts, best client proposals. Cowork reverse-engineers your wins and patterns instead of guessing your style. This is the file-based equivalent of few-shot prompting, but it persists across every session.

Step 5: Plugins in Priority Order

Now that context is set, plugins actually work. Install in this order:

  1. Productivity — task management, scheduling, workflow automation. Foundation layer. Install regardless of role.
  2. Your industry-specific plugin — Marketing, Sales, Data Analysis, or whatever matches your daily work.
  3. A custom plugin you build yourself — Tell Cowork: “I want to create a plugin for [your most repetitive task]. Interview me about the workflow, then build the plugin file.” Takes 15 minutes and saves hours.

Skip everything else until these three are running smoothly.

Step 6: Scheduled Tasks (The Unlock)

Plugins and workflows run when you tell them to. Scheduled tasks run whether you remember or not.

Start with one: a daily morning briefing that checks your calendar, flags important emails, and lists top priorities. Set it to run at 6am. By the time you sit down with coffee, your day is already organized — without opening Gmail or checking Slack.

This is where Cowork stops being a tool and starts being an employee.

Step 7: The Review Loop That Makes It Better

What separates people who use Cowork for a week from people who use it permanently: every Friday, spend 10 minutes reviewing what worked and what didn’t. Update context files. Tweak workflows. Add new examples to successful-examples/.

Cowork gets better the more it knows about you. It only learns if you feed it.

The Prompting Era Is Over

“The prompting era is over. We’re in the context era now.”

The difference between “Cowork is a toy” and “Cowork runs half my business” is 30 minutes of setup done in the right order. Context files first. Then the meta-prompt. Then one workflow. Then plugins. Then scheduled tasks. Stop installing plugins and hoping for the best.

Connections

Actionable for RDCO

The successful-examples/ folder is an immediately adoptable pattern — both for internal use and for client onboarding. Clients should drop 5–10 of their best deliverables into Cowork before their first real session. For RDCO, this maps to the 06-reference/ vault: the best articles and frameworks are already captured; pointing Cowork at them gives it style reference without extra setup.

The “one workflow, not five” principle is a useful constraint for client onboarding sessions — it prevents the enthusiasm trap (set up everything at once, abandon everything in a week). First engagement deliverable: one working, tested, refined workflow that runs weekly without their involvement.

Ganim’s guide is more accessible than Navtoor’s 17-practice framework for clients who aren’t power users — it’s a shorter read with a clear sequence. Use Ganim’s guide as the initial client handout, Navtoor’s as the deeper reference once they’re running.