Walkthrough Guide

The Vibe Working Setup

A complete walkthrough for setting up your AI working stack — from first account to deployed app. This is how you go from zero to building, shipping, and managing with AI doing 80% of the execution.

Based on a coaching session by James PoulterLast updated March 2026

What is Vibe Working?

Vibe Working is Level 4 in the 6 Levels of AI-Assisted Work — the current competitive frontier. AI handles roughly 80% of execution while you monitor, direct, and validate. Think of it as having a tireless junior colleague who can write, build, research, and organise — but still needs your judgment on what matters.

The key shift

You stop being the person who does the work. You become the person who directs, reviews, and decides. The same things you'd tell a human assistant — your preferences, your file structure, your clients — you tell Claude. Then it gets on with it.


Required Accounts

Three accounts form the backbone of the vibe working stack. Get these set up first — everything else plugs into them.

Setup order

Create your GitHub account first, then sign into Vercel using your GitHub credentials. This links them automatically — when you push code to GitHub, Vercel picks it up and deploys it.


Core Tools & IDEs

Beyond the three core accounts, these tools extend what you can do. Some are essential, others are for when you're ready to level up.
⌘

Cursor

cursor.com

The preferred IDE (Integrated Development Environment) for building with Claude Code. An IDE lets you see all your project files, make targeted one-word edits, and run the terminal alongside your code. Best for enhanced projects and fine-grained changes. Based on VS Code.

Recommended for builders
G

Anti-gravity (Project IDX)

idx.google.com

Google's free cloud IDE — no installation needed. Sign in with your Google account and start building. A solid free alternative to Cursor for running Claude Code in the browser without any local setup.

Free alternative
🎤

Wispr Flow

wisprflow.ai

Voice-to-text AI that works in any application. Speak your prompts instead of typing them — dramatically faster for longer instructions. Set it up on Mac with the Globe key, or assign a key combination like Control + Option for external keyboards.

Recommended
🧩

Claude Chrome Extension

Chrome Web Store → search "Claude"

Gives Claude the ability to see and interact with your browser. Enables Claude in Chrome for browsing tasks, and the Control Chrome connector for automation. Essential for Co-work sessions that need to read web content or fill in forms.

Required
21

21st.dev

21st.dev

A component library where you can browse pre-built UI elements — shimmering text, animated cards, interactive forms. Copy the code prompt for any component and paste it into Claude Code to instantly add it to your project. Like a design catalogue for vibe coders.

Optional — great for polish
💻

Claude Desktop App

claude.ai/download

The Mac/Windows desktop application for Claude. Includes Claude Code built in — for most projects, this is all you need. Also gives you Co-work mode with Excel and PowerPoint integration, Dispatch for remote monitoring, and project batching.

Required

Essential Connectors

Connectors let Claude see and interact with your existing tools. This is where the real power comes from — once Claude can read your email, calendar, files, and databases, prompts like "check my calendar, find the relevant emails, and draft a brief" actually work. Set these up in Claude under Settings → Customize → Connectors.
GitHubRead & write code
GmailDrafts only — can’t send
Google CalendarFull CRUD access
Google DriveRead-only access
NotionRead & write databases
VercelDeployments & logs
FigmaDesign files
Claude in ChromeBrowser control
HubSpotCRM — if used
AirtableStructured data
BoxFile storage
Apollo / PitchbookData enrichment
Core — set up first
Recommended
Optional

Plugins & Skills

Beyond connectors, enable Plugins (packages of skills) in Settings → Customize → Add Personal Plugins. Recommended: Brand Voice, Operations, Finance, Marketing, Productivity. Also enable Artifacts, AI Powered Artifacts, and Visualisations in your capabilities settings. Skills are pre-defined mega-prompts that handle complex workflows — like generating a brand voice guide or writing a full proposal — in a single command.

Gmail safety note

The Gmail connector can only draft emails — it cannot send them unless you explicitly grant permission each time. Calendar has full create/delete/update access. Google Drive is read-only — Claude can organise and annotate but not delete or create files in Drive directly.


Claude Settings & Preferences

Your personal preferences cascade across all sessions. Set them once and they apply everywhere — but can be overridden at the project, Co-work session, or Claude Code level.
1

Personal Preferences

Go to Settings → General → Personal Preferences. Write out how you like to work — your communication style, formatting preferences, things to avoid. This is your global instruction set for every conversation.

2

Enable Capabilities

Under capabilities, turn on Artifacts, AI Powered Artifacts, and Visualisations. These let Claude generate interactive previews, charts, and documents inline.

3

Install Plugins & Skills

Browse the plugin marketplace under Customize. Install Brand Voice, Operations, Finance, Marketing, and Productivity plugins. Each brings its own skills — specialised prompts for complex workflows.

4

Connect Your Services

Wire up your connectors one at a time. Start with GitHub and Gmail, then add Google Calendar, Drive, and Notion. Be cautious with permissions — you can always expand access later.


How to Learn This

Don't try to do everything at once. There's a natural progression — each stage builds confidence and capability for the next.
Start here

Chat

Simple tasks and conversations. Ask questions, draft emails, brainstorm ideas. Get comfortable with prompting and understand what Claude can do. No connectors needed — just you and the AI.

Then this

Co-work

Connect your knowledge stores and do real work. Claude reads your email, calendar, Notion, and Drive. Tasks like "check my schedule, find the relevant docs, and draft a brief" become one prompt. This is where productivity transforms.

Level up

Code

Build applications, landing pages, custom tools, and visual interfaces for your data. Start with the desktop app, graduate to an IDE for larger projects. Deploy via GitHub → Vercel pipeline.


The Reverse Prompting Method

The single most important technique for building anything substantial with Claude Code. Instead of trying to think of everything upfront, you prompt the model to prompt you.

How it works

When starting a new build in Claude Code, enable Plan Mode and switch to the Opus model for planning. Then, instead of writing a complete specification, describe what you want and end with one critical instruction — ask the AI to interview you before it starts building.

I want to build [description of your app or project]. Before you start writing any code, ask me questions about what you need to know to make this the best it can be. Don't proceed until I say so.

Claude will then ask you targeted questions about features, edge cases, design preferences, and technical requirements that you hadn't considered. Answer them, then let it build the plan. This produces dramatically better results than a single-shot prompt.

The vibe coding loop

Building with AI is iterative. Claude will do a lot of work but won't finish everything perfectly — much like a developer who needs regular check-ins. The process is: build → review → fix what it missed → ask what's still incomplete → repeat. Think of it like managing a fast but occasionally distracted junior developer.

Where to run Claude Code

Three options: the desktop app (easiest, best for most projects), an IDE like Cursor (see files, make targeted one-word edits, see the terminal), or the terminal directly (advanced). Start with the desktop app. Move to an IDE when you want to make fine-tuned edits or work on larger projects.


The Data Organisation Sequence

Before Claude can be truly effective, it needs to understand how your information is structured. This is the same onboarding you'd give a human assistant — but done methodically so Claude remembers permanently.

Clean your local files

Ask Claude Co-work to tackle your Desktop, Downloads, and Screenshots folders first. Get the chaos under control locally.

Organise Google Drive

Get Claude to review, reorganise, and structure your Google Drive. Create a logical folder hierarchy that makes sense for how you actually work.

Move local files to Drive

Take everything from your cleaned-up Desktop and Downloads and get it into the right Google Drive folders.

Write a Drive structure plan

Ask Claude to write out a plan of how your Google Drive is organised — what lives where and why.

Mirror in Notion

Take that structure plan and mirror it in Notion. Use Notion (or Obsidian) because they handle markdown — the language AI thinks in. Have Notion read, annotate, and catalogue your Drive contents.

Write it all into Claude’s instructions

Finally, write the complete organisational plan into your Claude instructions file. Now Claude knows where everything lives — and when it creates new things, it puts them back in the right place instead of making it up.

The EA test

Tell Claude the same things you'd tell a new Executive Assistant on day one — how your files are organised, who your key contacts are, how you like things done, what your clients need. The better the onboarding, the better the output.


Deploying to the Web

Once you've built something in Claude Code, here's how it gets from your machine to a live URL that anyone can visit.
1

Commit to GitHub

Save your code changes to your GitHub repository regularly. Each commit is a checkpoint you can roll back to if something breaks.

2

Connect repo to Vercel

Link your GitHub repository to a Vercel project. Once connected, every push to the main branch triggers an automatic deployment.

3

Get your live URL

Vercel gives you a URL immediately (e.g. yourproject.vercel.app). Buy a custom domain through Vercel or point an existing one.

4

Manage visibility

For private content, set the project to private or add password gating. Use a robots.txt file to prevent search engine indexing until you’re ready to go public.


Security Boundaries

AI is powerful — but it needs guardrails. These are the firewalls to keep in place as you give Claude access to your working life.

Safe to connect

  • Gmail (drafts only by default)
  • Google Calendar (full access)
  • Google Drive (read-only)
  • Notion (read & write)
  • GitHub (code repos)
  • Figma (design files)
  • Vercel (deployment logs)
  • Fresh/clean email accounts work best

Keep away from AI

  • Financial accounts & banking
  • Transaction capabilities
  • Password managers (1Password, etc.)
  • Account login credentials
  • Massive unprocessed data stores (burns tokens fast)
  • Anything where an error could cost real money

Token awareness

Processing large data stores — like 30,000 unread emails or an entire Google Drive — will consume significant tokens quickly. Get organised in other areas first before letting Claude loose on large data volumes. Start fresh where possible.


All Links at a Glance

Claude AI — Chat, Co-work & Codeclaude.ai →GitHub — Code storage & version controlgithub.com →Vercel — Hosting & deploymentvercel.com →Cursor — AI-native IDEcursor.com →Anti-gravity / Project IDX — Free cloud IDEidx.google.com →Wispr Flow — Voice dictationwisprflow.ai →Notion — Notes, databases & knowledge basenotion.so →Figma — Design & prototypingfigma.com →21st.dev — UI component library21st.dev →Next.js — React framework (by Vercel)nextjs.org →Claude Chrome Extensionchromewebstore.google.com/search/claude →