Day 1 catch-up

Get to the Day 2 starting line.

Use this after the live class, after the replay, or anytime the setup got tangled. The goal is one working baseline: Claude Desktop opens, Code is selected, the workspace folder is unzipped, /vault-setup has run, Obsidian points at the same folder, and ready-check.md exists.

Run the ready check Pick your stuck point

The baseline

You are caught up when these are true.

This is the starting point for the creative strategy work. Do this first. Save the advanced tools for later.

  • Claude Desktop opensOpen the installed desktop app. Click Code in the left sidebar. Stay in the desktop app for this setup.
  • The workspace is unzippedThe folder should be named something like claude-code-accelerator-workspace. If you only see a zip file, extract it first.
  • Claude points at that folderUse Select folder in Claude Code and choose the unzipped workspace folder, not Downloads by itself.
  • /vault-setup has runThis creates your starter files, updates the Script, installs the skill map, and gives the workspace a usable shape.
  • Obsidian opens the same folderChoose Open folder as vault, then select the same unzipped workspace folder Claude is using.
  • ready-check.md existsClaude created a real file and told you where it saved it. You can open that file outside Claude Code.

Ready check

Run this before you move on.

Paste this into Claude Code while it is open inside your workspace folder.

Read this workspace.
Tell me what folder you are in.
List the top-level files and folders you can see.
Then create ready-check.md with today's date and one sentence confirming you can read and write in this workspace.
Pass: Claude names real files from the workspace, creates ready-check.md, and tells you the path. If the file is missing, or Claude names files that do not exist, reopen Claude Code from the workspace folder and run the check again.

Stuck point

Find the exact snag.

Do the first fix. Then run the ready check again.

If this is happeningDo thisDone looks like
You are in Claude web Open the Claude desktop app. Click Code in the left sidebar. Use the folder picker from there. You see the Code screen inside the desktop app, with a selected local folder.
The workspace is still zipped Go to Downloads, right-click the workspace zip, and extract it. Then select the extracted folder in Claude Code. You can open the folder and see files like CLAUDE.md, README.md, and folders like skills/.
Claude opened the wrong folder Start a new Code session and choose the unzipped workspace folder. Do not select Downloads, Desktop, or your whole computer. The ready check lists the course workspace files.
/vault-setup does not appear Open the Skills & Tools page, download Vault Setup, attach the zip to Claude Code, and say: Install and run this skill. Claude asks a few setup questions and creates the workspace files.
Obsidian asks whether to create or open Choose Open folder as vault. Browse to the same unzipped workspace folder that Claude Code is using. Obsidian shows the workspace files. Open memory-map.md and skills/Skills.md.
Git, GitHub, or terminal sent you sideways Pause that path for now. Take a screenshot, paste it into Claude, and ask for plain-English instructions for your exact screen. You are back in Claude Desktop with the workspace selected. GitHub backup can wait until the baseline works.
You keep seeing permission prompts Allow the action when it matches the thing you asked Claude to do. If you turn on bypass permissions, treat it as a deliberate choice for this trusted workspace. Claude can create and edit files in the selected workspace without stopping every few seconds.

Replay path

If you are watching the replay a week later.

Use the replay as a walkthrough. The page below is the current setup path.

  1. Open the setup page first

    Start at Prework and setup. Download the workspace from the site, not from an old chat screenshot.

  2. Pause the replay at each install step

    Do not let the video outrun your machine. Pause when the workspace is downloaded, when the folder is selected, when /vault-setup runs, and when Obsidian opens.

  3. Run the ready check

    Run the prompt above. If it passes, you can move on to the creative strategy material. If it fails, fix the stuck point first.

Day 1 commands

Three commands people asked about.

Use these after the baseline works. They are for saving lessons and moving cleanly between sessions.

/remember-this

Save one rule mid-session.

Use it when you notice a preference, standard, client fact, or correction that should affect future work.

/reflect

Promote the lesson at the end.

Use it after a working session to decide what belongs in memory, what stays as a saved artifact, and what should be ignored.

/handoff

Restart without re-explaining.

Use it when a session gets long, context feels crowded, or you want a clean start with the useful state carried forward.

Skip for now

Ignore these until the ready check passes.

These are useful later. They are distractions while the baseline is still broken.

MCPs and API keysUseful for research and integrations after the workspace is stable.
Cursor or other IDEsNice optional views. Claude Desktop is the baseline for the workshop.
Dashboard buildsSave these for the dashboard and website sessions.
Advanced Script tuningRun it after Obsidian can see the same files Claude can edit.

Support packet

If you still need help, send this.

Exact information beats a vague "it is not working." Send this to max@maxpbernstein.com and add a screenshot.

Send to: max@maxpbernstein.com

I am on: [Mac / Windows]
I am using: [Claude Desktop / Claude web / terminal]
The exact step I am stuck on:
What I expected:
What happened:
Screenshot attached:
The folder I selected in Claude Code:

When in doubt, point Claude at the screenshot.

Take a screenshot of the exact screen, paste it into Claude, and ask it to talk to you in plain English for your operating system.

Open setup Open Skills & Tools
← Back to home base