Getting Started with Claude
A hands-on guide built for Mike Scherp — Sr. CPA, stock trader, fantasy football champion, future AI power user.
From your first prompt to building dashboards, websites, and automated workflows.
Built with care by your brother (and Claude) — April 2026
Use the tabs above (or click the section overviews below) to explore each section. Start with Overview →
Ch 1 — Overview
What Claude is and why it matters for a CPA who trades and loves sports
Ch 2 — Get Started
Subscribe, download the phone app, and start using Claude in 5 minutes
Ch 3 — First Prompts
Copy-paste prompts tailored to your world
Ch 4 — Projects to Build
Landing page, dashboards, portfolio tracker & more
Ch 5 — IDE & Code
VS Code, Cursor, Claude Code, GitHub basics, and folder structure
Ch 6 — Advanced
APIs, MCPs, webhooks — connect betting, stocks & clone GitHub repos
Ch 7 — Workflows
Daily routines: market briefs, email drafts, game prep & more
🔥 Scott's Hot Tips
Tap to expandHard-won lessons from daily use. Internalize these and you'll get 10x more out of Claude from day one. See the full page →
1. Start Fresh Chats Often — Context Is Everything
Every conversation has a "context window." The longer it goes, the more likely Claude loses track or hallucinates. Start a new chat whenever you switch topics. One focused chat per topic beats one massive thread every time.
2. Screenshots Are Your Best Friend
When following setup instructions, take a screenshot of what you see and paste it into the chat. Claude reads images and gives you precise next steps. Don't waste time clicking around — just screenshot → paste → ask "what do I click next?"
3. Use a "Second Opinion" Chat to Audit
When Claude builds something for you, open a separate chat, paste the output, and say "audit this — how can I make it better?" Fresh context catches things the first chat missed.
4. Frame Claude as an LLM, Not a Person
Don't say "act as a senior CPA." That constrains Claude to roleplay a human caricature. Do frame it as an LLM drawing on specific domain knowledge, give clear tasks, and ask it to clarify first.
5. Upload Files, Don't Explain Them
Drag CSVs, PDFs, images, Excel files right into the chat. Claude reads them directly — faster and more accurate than describing what's in them.
See all 10 tips →
✅ Week 1 Checklist
Tap to expandDo these in order. By next weekend, you'll wonder how you lived without this. Open full checklist →
- Redeem Claude Pro (use the gift link in Ch 2!)
- Download the Claude app on your phone
- Turn on Web Search, Code Execution, and Artifacts in Settings
- Set your User Preferences (tell Claude who you are)
- Set up Projects: Trading, Sports, and Client Work
- Send your first 5 prompts — try the examples from Ch 3
- Upload a CSV (trades, expenses, anything) and ask Claude to analyze it
- Ask for a morning market brief and a betting lines dashboard
- Get a personal laptop when you're ready for desktop power tools
- Tell your brother how it went so he can add more ideas to your guide
Claude is an AI assistant built by Anthropic. Think of it as an incredibly smart teammate who can write, analyze data, build websites, automate tasks, and explain complex topics — available 24/7.
Data Analysis on Demand
Drop a CSV of stock trades or client data and get instant summaries, charts, and insights — no Excel formulas needed.
Sports & Betting Intel
Pull live betting lines, build comparison dashboards, analyze fantasy matchups — Claude is your research analyst.
Build Things Without Code
Describe what you want in plain English and Claude writes the code. Websites, tools, dashboards — all from conversation.
Automate Your Routines
Morning market briefings, calendar management, client memo drafts, expense categorization — automate the boring stuff.
Claude isn't just a chatbot. It's a Swiss Army knife — a research analyst, web developer, copywriter, and data scientist rolled into one. The key skill you're learning isn't "coding." It's how to describe what you want clearly.
🌐 Where Claude Lives — And What Each One Can Do
Tap to exploreClaude isn't one app — it's available in four places, and each one unlocks different capabilities. Think of it like a car: the phone is a remote start, the browser is the rental car, the desktop app is your fully loaded daily driver, and the terminal is a race car.
| Platform | Best For | Level | Start? |
|---|---|---|---|
| 📱 Phone | Chat on the go, dictate prompts, dispatch tasks to desktop, quick research, review & approve work | Beginner | Companion |
| 🌐 Browser | Full chat, artifacts, file upload, web search — works on any computer | Beginner | Backup |
| 💻 Desktop | Everything above + Cowork, computer use, Chrome control, local files, scheduled tasks, extensions | Beginner | ★ Start |
| ⬛ Terminal | Full app building, code projects, GitHub, scripts, API integrations, automation pipelines | Intermediate | Phase 2 |
📱💻 Deep Dive: Phone vs Desktop — What Can Each Actually Do?
Tap to exploreSame brain, different bodies. Here's what each platform can and can't do:
📱 Phone — Your Command Center
Can do:
→ Full chat (same AI brain)
→ Web search, file uploads, artifacts
→ Voice dictation (up to 10 min)
→ Remote Control — send tasks to desktop
→ Dispatch to Cowork — assign a job from bed, it runs on your PC
Can't do:
→ No local file access
→ No computer use (can't control your screen)
→ No Cowork or Claude Code
→ No scheduled automations
💻 Desktop — Your War Room
Everything above, plus:
→ Cowork — reads, edits, creates files on your machine
→ Computer Use — controls your screen, opens apps, clicks, fills forms
→ Claude in Chrome — browses the web for you, scrapes data
→ Local file access — reads your actual folders and docs
→ Scheduled tasks — "pull a report every Friday"
→ Claude Code built in
→ Quick summon — Ctrl+Alt+Space
🌐 Browser & ⬛ Terminal
Browser — same as desktop chat minus the power tools. Use on someone else's machine.
Terminal (Claude Code) — the developer power tool. Writes files, runs commands, manages Git. Where serious automation happens.
🎲 Real Example: Betting Line Reports on Each Platform
Tap to exploreSame goal — "get me daily betting line reports" — very different capabilities on each platform:
📱 Phone: Manual but Fast — ★★★☆☆
Ask Claude each morning for lines. Web search only, one-time report. Clean and useful but manual every time.
🌐 Browser: Same as Phone, Bigger Screen — ★★★☆☆
Identical data, just easier to read on a full monitor. Still manual, no API access, no scheduling.
💻 Desktop: Semi-Automated — ★★★★☆
Claude in Chrome navigates actual sportsbook websites. Computer Use reads your screen. Cowork saves to CSV. Schedule it to run at 6:30 AM automatically — wake up to a finished report. No typing after setup.
⬛ Terminal + APIs: Fully Automated — ★★★★★
Python script calls The Odds API → structured data from 15+ sportsbooks → calculates implied probability → flags arbitrage → tracks line movement → texts you when lines shift → runs 365 days, hands-free. This is what the sharps use.
Phone/desktop manual prompts (this week) → Desktop Cowork + Chrome automation (week 2–3) → Full API pipeline with Claude Code (month 2). Each level builds on the last.
Desktop App for 2–4 weeks → learn prompting → build your consulting landing page → explore Claude Code + APIs → graduate to VS Code / Cursor when you're ready for bigger projects.
Yes — and this is the killer combo. Once you set up a Cowork task or Claude Code session on your desktop, you can dispatch it from your phone. So you're lying in bed Sunday morning, tap your phone, tell Claude "run my betting lines report," and it executes on your PC using all the desktop power tools. You get the results on your phone a few minutes later. The phone is the remote control. The desktop is the engine.
You don't need a new computer to start — but you'll want one soon. Here's the full setup.
🖥️ Get Your Own Machine
Tap to exploreThe phone app is powerful on its own, but the desktop unlocks the next level — Cowork, scheduled tasks, computer use, local file access, and Claude Code. For that you need a personal Windows machine (not your work laptop).
🎯 Top Pick: Dell XPS 14 (2026) — $2,199
32GB RAM / 1TB SSD / Intel Core Ultra X7 / 2.8K OLED display
The consensus best Windows laptop right now. Premium build, fast processor, gorgeous OLED, 12+ hours battery.
→ 32GB RAM — Claude Desktop, VS Code, terminal, 15 browser tabs, Python scripts — all at once.
→ 1TB SSD — plenty for projects, data, and repos.
→ 3× Thunderbolt 4 — plug into your monitor, future-proof for docks.
→ 2.8K OLED — dashboards and code look incredible.
→ 12+ hour battery — couch, coffee shop, flight.
Also Great: Lenovo ThinkPad X1 Carbon — ~$1,800
Best keyboard in the industry (CPAs who type all day love ThinkPads), 32GB RAM, HDMI built in, legendary durability.
Monitor setup & accessories
You already have one — the XPS 14 connects via USB-C/Thunderbolt or a USB-C to HDMI adapter (~$15). The ThinkPad has HDMI built in. Instant dual-screen: dashboards on the monitor, Claude on the laptop.
→ USB-C to HDMI adapter (~$15) — if your monitor only has HDMI
→ Logitech MX Keys + MX Master 3S (~$200 total) — gold standard keyboard + mouse
→ USB-C dock ($50–$150) — single-cable desk setup. CalDigit or Anker.
Download Claude Desktop at claude.ai/download. Sign in with the same account. Everything syncs across phone, browser, and desktop automatically.
First month's on me, big dawg.
Click the link below and make Claude a part of your everyday. Welcome to the future.
🎁 Redeem Your Free Month of Claude ProRedeem Claude Pro & Create Your Account
Tap the gift link above on your phone. Sign up with your personal email — you'll want this outside of work too. This gives you the most powerful model (Opus), more messages, web search, file uploads, Projects, and artifacts.
Download the Claude App on Your Phone
Search "Claude by Anthropic" in the App Store (iPhone) or Google Play (Android). Sign in with the same account you just created. You're live.
Enable Key Features
In the app, go to Settings and turn on Web Search, Code Execution, and Artifacts. These let Claude search the internet, run code, and build interactive mini-apps right in the chat.
Set Your Preferences
Go to Settings → User Preferences. Tell Claude who you are:
Set Up Your Projects (Folders)
Projects remember your context. Create these to start:
→ "Trading" — stock analysis, watchlists, market research
→ "Sports" — betting lines, fantasy football, matchup analysis
→ "Client Work" — memos, tax research, deliverable templates
Send Your First Message
The #1 skill with AI is prompting. The difference between a mediocre response and a great one usually comes down to how you frame the ask. Here's the blueprint the best prompts follow:
I am building [your project/process] and need to break the patterns of [bad habit or blind spot].
Your Tasks
- task 1
- task 2
- task 3
Ask me clarifying questions before completing your tasks.
Framing Claude as an "LLM that has absorbed information" leverages what it actually is — instead of constraining it to roleplay a human persona. Explicit tasks prevent drift. Asking for clarifying questions forces Claude to confirm understanding before charging ahead. See Scott's Hot Tips → #5 for the full philosophy.
I am building a weekly betting decision framework and need to break the patterns of chasing recent trends and betting on gut feel.
Your Tasks
- Search the web for today's NFL lines across major sportsbooks (DraftKings, FanDuel, BetMGM, Caesars)
- Identify games with reverse line movement (line moving against public betting %)
- Flag the 3 best value plays with reasoning grounded in historical data, not recency bias
- Build a clean dashboard artifact showing lines, implied probabilities, and your value picks
Ask me clarifying questions before completing your tasks.
I am building a data-driven start/sit process and need to break the patterns of starting players based on name recognition or last week's box score.
Your Tasks
- Review my roster and my opponent's roster (I'll share them)
- Analyze matchups using opponent defensive rankings, pace of play, and recent target/touch trends
- Identify "trap" players I'm tempted to start but shouldn't (and sleepers I'm overlooking)
- Give me a recommended starting lineup with a confidence score for each decision
Ask me clarifying questions before completing your tasks.
I am building a disciplined trading review process and need to break the patterns of confirmation bias and anchoring to my cost basis.
Your Tasks
- Review the CSV of my trades from the last 6 months (I'm uploading it)
- Calculate my realized P&L, win rate, and performance by sector
- Identify patterns between my holding period and returns
- Flag trades where my behavior contradicted my stated thesis
- Suggest rule changes grounded in risk management, not recent performance
Ask me clarifying questions before completing your tasks.
I am building a repeatable memo template for real estate tax consultations and need to break the pattern of burying recommendations in jargon.
Your Tasks
- Draft a memo using these details: purchase $450K in 2018, current value ~$680K, ~$95K depreciation claimed, considering a 1031 exchange
- Compare straight sale vs. 1031 with estimated tax liability for each
- Recommend next steps in plain English
- Keep it under 2 pages
Ask me clarifying questions before completing your tasks.
Not every prompt needs the full blueprint. For smaller asks, just be specific and give context:
For serious work, use the blueprint above — it leverages what Claude actually is (an LLM) and forces clarity before execution. For quick asks, just be specific about what you want and what format. And always iterate: "that's close, but change X" beats starting over.
Real things you can build inside Claude Desktop — most in a single conversation.
Project 1: Your CPA Consulting Landing Page
Tell Claude to build a professional website. Describe your services, target clients, and vibe — Claude generates a full HTML page you can deploy for free.
- Name: Mike Scherp, CPA
- Tagline: "Strategic financial guidance for businesses ready to scale"
- Services: Tax Strategy, M&A Advisory, Financial Planning, Audit Prep
- Style: Clean, modern, trustworthy — dark navy + gold accents
- Include: hero section, services grid, about section, contact form, testimonials
Make it a single HTML file I can deploy. Make it look premium.
To publish free: Drag the HTML file into Netlify (netlify.com) or Vercel (vercel.com) — literally drag and drop.
Project 2: Stock Portfolio Tracker
Upload your trade history CSV and have Claude build an interactive dashboard. It charts your performance, calculates risk metrics, and compares against benchmarks like S&P 500.
Project 3: Daily Betting Lines Report
Ask Claude to search for today's lines across NFL/NBA/MLB, compare odds across books, flag value plays, and deliver a clean dashboard. Ask for this every morning.
Project 4: Automated Client Briefs
Create a Claude Project for client work. Upload engagement details and have Claude generate standardized memos, tax summaries, and deliverable templates.
Project 5: Weekly Routine Optimizer
Describe your typical week and have Claude build a structured schedule, suggest automations, and create a weekly review template.
Hard-won lessons from real daily use. Internalize these and you'll get 10x more out of Claude from day one.
1. Start Fresh Chats Often — Context Is Everything
Every conversation has a "context window" — a limit on how much Claude can remember within a single chat. The longer a conversation goes, the more likely Claude starts to lose track of earlier details or — worse — hallucinate (confidently give you wrong info based on stale context).
The fix: Start a new chat whenever you switch topics or feel like Claude is getting confused. It's free and instant. Think of it like clearing your desk before starting a new task. One focused chat per topic beats one massive thread every time.
"Is this the same task I started with?" If not, open a new chat. Your future self will thank you.
2. Screenshots Are Your Best Friend
When Claude gives you setup instructions — installing an app, configuring settings, connecting services — take a screenshot of what you see and paste it right into the chat. Claude can read images and will give you precise next steps based on exactly what's on your screen.
Why this matters: Instead of spending 10 minutes clicking around menus trying to find the right button, just screenshot → paste → ask "what do I click next?" Claude sees your exact UI and tells you exactly what to do. This alone will cut your frustration in half.
On Windows: Win+Shift+S to select-screenshot, then Ctrl+V to paste into Claude. On Mac: Cmd+Shift+4, then Cmd+V. Muscle-memory this.
3. Use a "Second Opinion" Chat to Audit Your Work
Here's a power move: when Claude helps you build something — a plan, a workflow, a website — open a separate chat, paste the output in, and ask Claude to audit it. Fresh context, fresh eyes. It'll catch things the first chat missed.
4. Tell Claude What NOT to Do
Claude tends to be thorough — sometimes too thorough. If you want a concise answer, say so. If you don't want a history lesson before the advice, say that too. Negative constraints are just as powerful as positive ones.
5. Frame Claude as an LLM, Not a Person
The worst prompting advice floating around is "tell Claude to act as a senior [insert profession]." Don't do it. Claude isn't a person — it's an LLM that has absorbed an enormous amount of information across virtually every domain. When you tell it to "act as a senior tax attorney," you're actually constraining it to roleplay a human caricature instead of leveraging what it actually is.
❌ DO NOT: "Act as a senior CPA with 20 years of experience and advise me on..."
✅ DO INSTEAD: Frame it as an LLM drawing on specific domain knowledge, state your goal, list explicit tasks, and always ask for clarifying questions first.
I am building a weekly betting decision framework and need to break the patterns of chasing recent trends.
Your Tasks
- Search the web for today's NFL lines across major sportsbooks
- Flag 3 games with reverse line movement
- Identify value plays grounded in data, not recency bias
Ask me clarifying questions before completing your tasks."
6. Iterate — Don't Start Over
If Claude gives you something that's 70% right, don't re-prompt from scratch. Say "this is close, but change X and make Y shorter." Claude is built for iteration. Treat it like editing a draft with a colleague, not placing a new order at a restaurant.
7. Upload Files Instead of Explaining Them
Don't spend 10 minutes describing your spreadsheet layout. Just drag the CSV or Excel file into the chat and say "analyze this." Claude reads files directly — it's faster and more accurate than you typing out what's in them. Works with PDFs, images, Word docs, code files, and more.
8. Save Your Best Prompts
When you write a prompt that gets a great result — the morning market brief, the expense categorizer, the betting lines pull — save it somewhere (Notes app, a doc, a Claude Project). You'll reuse your best prompts dozens of times. Build a personal prompt library over time.
9. Use Projects for Recurring Work
Claude Projects let you pin instructions and reference files that apply to every conversation in that project. Set up a "Trading" project with your risk tolerance and watchlist, a "Client Work" project with your firm's memo templates, a "Fantasy" project with your league settings. Claude gets smarter about your context every time.
10. Verify Numbers — Trust but Check
Claude is excellent at analysis, but it can miscalculate or misinterpret data, especially in long conversations. For anything with financial or legal consequences — tax numbers, trade P&L, client-facing figures — spot-check the math. Ask Claude to "show your work" or "break this down step by step" so you can follow the logic.
Once you've built a few things in Claude Desktop, you'll want a proper workspace. Don't memorize this — just know it exists.
What's an IDE?
IDE = Integrated Development Environment. It's like Microsoft Word, but for code. The AI does most of the writing — you're the project manager telling it what to build.
VS Code
Microsoft's free code editor. Industry standard. Pair with GitHub Copilot or Claude extensions for AI-assisted coding.
Cursor
VS Code rebuilt with AI at the core. Claude built right in. Highlight code, describe what to change. Easiest path from "I don't code" to "I'm building things."
Claude Code
Claude in your terminal. Describe what you want and it writes files, runs commands, tests code — like pair-programming with a developer.
What's GitHub?
Tap to expandThink of GitHub as Google Drive for code. Stores project files in the cloud, tracks every change, lets you collaborate.
Repository
A project folder. Each site/app gets its own "repo."
Commit
A saved checkpoint with a note about what changed.
Push
Upload your changes to GitHub.
Branch
An experimental copy without breaking the main project.
Code Languages Cheat Sheet
Tap to expandYou don't need to learn these — Claude writes the code. But knowing what they are helps:
| Language | What It Does | You'll See It When... |
|---|---|---|
| HTML | Skeleton of web pages — structure and content | Building your consulting landing page |
| CSS | Styling — colors, fonts, layout, animations | Making your site look good |
| JavaScript | Logic — buttons, data updates, interactivity | Dashboards, calculators, interactive tools |
| Python | Swiss Army knife — data analysis, automation, APIs | Analyzing CSVs, pulling stock data |
| React | JavaScript framework for building interactive UIs | Complex dashboards and web apps |
📁 Folder Structure 101
Tap to expand├── index.html ← Your main webpage
├── style.css ← How it looks
├── script.js ← How it behaves
├── images/ ← Your photos & logos
│ ├── headshot.jpg
│ └── logo.png
└── README.md ← Project description
You don't need to learn to code. Claude writes the code. Your job is to describe what you want, review what it builds, and ask it to fix things. You're the architect — Claude is the construction crew.
This is where Claude goes from "helpful chatbot" to "automated system that works while you sleep." Don't let the jargon scare you — the concepts are simpler than they sound, and Claude does the hard part.
🔌 What's an API?
Tap to exploreAPI = Application Programming Interface. It's a way for two apps to talk to each other. When you check a stock price in your brokerage app, that app is calling an API behind the scenes to get the latest price from a data provider. APIs are the plumbing of the internet.
Think of it like this:
You're at a restaurant. You (the app) don't go into the kitchen yourself. You give your order to the waiter (the API), who brings back exactly what you asked for from the kitchen (the data source). APIs work the same way — you send a request, you get data back.
APIs That Matter for You
Sports Betting APIs
Services like The Odds API, OddsJam, and BetAnalytics let you pull real-time betting lines from dozens of sportsbooks — DraftKings, FanDuel, BetMGM, etc. — into a single feed. Instead of manually checking 5 apps every morning, a script calls the API once and gives you every line, spread, and over/under in a clean dashboard.
Stock & Market APIs
Alpha Vantage (free tier), Polygon.io, Yahoo Finance, and Alpaca let you pull real-time and historical stock data, run screeners, and even execute trades programmatically. You can build a script that checks your watchlist every hour and alerts you when a stock hits your target price.
Fantasy Sports APIs
ESPN Fantasy API, Sleeper API, and Yahoo Fantasy API let you pull your league data — rosters, scores, matchups, waiver wire — directly into Claude for analysis. No more manually comparing stats across tabs.
Most APIs require a free "API key" — it's like a password that identifies you. You sign up on their website, they give you a key (a long string of letters and numbers), and you paste it into your script. Claude will walk you through the entire process. Most have free tiers that are more than enough for personal use.
🔗 What's an MCP?
Tap to exploreMCP = Model Context Protocol. This is a newer concept and it's a game-changer. MCPs let Claude directly connect to external services — your Google Calendar, Gmail, Slack, databases, APIs — so Claude can read and act on real data without you copy-pasting anything.
API vs MCP — What's the Difference?
| Concept | How It Works | Example |
|---|---|---|
| API | You (or a script Claude writes) call an external service and get data back. Runs outside of Claude. | A Python script pulls betting lines every morning and saves a CSV. |
| MCP | Claude connects directly to a service and can read/write to it mid-conversation. Runs inside Claude. | You say "check my Google Calendar for this week" and Claude reads it live, right in the chat. |
MCPs You Can Set Up in Claude Desktop
These are already available or easy to configure. Claude Desktop supports MCP servers — you enable them in Settings or via a config file.
Google Calendar
Claude reads your schedule, creates events, checks conflicts. "What's my week look like?" just works.
Gmail
Claude searches your inbox, drafts replies, summarizes threads. "Find the email from my client about Q3 taxes."
Google Drive
Claude reads your docs and spreadsheets directly. Upload nothing — just tell it which file to look at.
Slack
Claude reads channels, summarizes conversations, drafts messages. Great for catching up after PTO.
Imagine saying: "Check my Google Calendar for this week, pull the latest NFL lines from The Odds API, cross-reference with my fantasy roster in Sleeper, and give me a game plan for Sunday — then draft a reminder email to my fantasy league group chat." MCPs + APIs make this a single conversation.
🔔 What's a Webhook?
Tap to exploreIf an API is "you asking for data," a webhook is "data coming to you automatically." It's a notification system — when something happens (a stock hits a price, a line moves, a new email arrives), the service sends a message to your app instantly.
Real Examples for You
Betting lines move: A webhook fires when a line shifts by more than 1.5 points → triggers a script that sends you a text alert with the new odds.
Stock hits target price: Your Alpaca webhook detects NVDA crossing $180 → sends you a Slack message with your pre-written trade thesis so you can decide fast.
Client email arrives: Gmail webhook detects an email from a specific client → triggers a Claude workflow that drafts a response and adds a follow-up to your calendar.
How They Connect Together
│ TRIGGER Line moves, stock alert, new email, cron job │
│ (webhook or scheduled script) │
│ ↓ │
│ FETCH DATA Call APIs (odds, prices, calendar, email) │
│ ↓ │
│ PROCESS Claude or a script analyzes the data │
│ ↓ │
│ ACT Send alert, update dashboard, draft email │
└─────────────────────────────────────────────────────┘
📦 Building Off Others' Work: GitHub Repos
Tap to exploreHere's a secret: you don't have to build everything from scratch. GitHub has millions of open-source projects that you can download, customize, and make your own. Someone has already built a sports betting tracker, a stock screener, a fantasy football analyzer — you just find it, clone it, and tell Claude to modify it for your needs.
How to Clone a Repo (Step by Step)
Find a Repo
Go to github.com and search for what you want — "sports betting odds tracker", "stock portfolio dashboard python", "fantasy football analyzer." Star it if you like it (like bookmarking).
Clone It to Your Computer
Click the green "Code" button → copy the URL. Open your terminal and type:git clone https://github.com/username/repo-name.git
This downloads the entire project to your computer.
Open It in Your IDE
Open VS Code or Cursor → File → Open Folder → select the cloned folder. You now have the full project with all its files.
Ask Claude to Explain It
Point Claude Code at the folder or paste key files into Claude Desktop:"Explain what this project does, how the files are organized, and how I can customize it for my needs."
Customize It
Tell Claude what to change: "Swap this API for The Odds API", "Add a column for implied probability", "Change the UI to dark mode", "Make it send me a text when a line moves." Claude modifies the code, you test it.
Repos Worth Bookmarking
Sports Betting & Odds
Search GitHub for: sports betting odds tracker, arbitrage betting calculator, odds-api python. Look for repos with 50+ stars and recent commits (means they're actively maintained).
Stock Trading & Analysis
Search for: stock screener python, portfolio tracker dashboard, alpaca trading bot. Many include built-in charts and technical indicators.
Fantasy Football
Search for: fantasy football analyzer, espn fantasy api python, sleeper fantasy dashboard. Some have full draft assistants you can run locally.
Every good repo has a README.md file — it's the instruction manual. Read it (or paste it into Claude and ask for a summary). It tells you what the project does, how to install it, and what API keys you need. If a repo has no README or hasn't been updated in 2+ years, skip it and find a better one.
⚡ Putting It All Together: Your Automation Stack
Tap to exploreHere's what a fully automated week could look like once you've built up to it. You don't need to do all of this — pick one and grow from there.
Morning (Automated Daily Brief)
6:30 AM — A scheduled Python script runs:
→ Calls Alpha Vantage API for your watchlist pre-market data
→ Calls The Odds API for today's betting lines
→ Checks your Google Calendar via MCP for meeting conflicts
→ Formats everything into a clean daily brief and emails it to you
You wake up, check your phone, and have a personalized market + sports + calendar briefing waiting.
During the Day (Real-Time Alerts)
Webhooks running in the background:
→ Line movement alert: a betting line shifts 2+ points → text notification
→ Stock watchlist: NVDA drops below your buy target → Slack alert with your trade thesis
→ Client email: key client sends a message → auto-draft a response for your review
Sunday (Game Day Workflow)
One Claude conversation:
→ Pull your Sleeper fantasy roster + opponent via API
→ Cross-reference with latest injury reports (web search)
→ Pull consensus projections and betting lines
→ Generate start/sit recommendations with confidence levels
→ Output a shareable game card you can send to your league group chat
You won't build all of this in week one. Start by asking Claude to write a single API script — like pulling today's odds. Run it. See the data. Then add the next piece. Each step builds on the last. Within a month, you'll have a system that saves you hours every week.
"I want to build an automated daily briefing that pulls NFL betting lines and my stock watchlist every morning. Walk me through the full setup — what APIs to sign up for, what tools I need installed, and write me the first script."
Real workflows you can set up today. Start with one or two and build from there.
Morning Market Brief
Every morning, open Claude and ask:
Email Drafting
Paste any email you need to reply to and tell Claude the tone and key points. It drafts the response in seconds.
Expense Categorization
Upload a CSV, have Claude categorize by tax category, flag items over a threshold, and total by category.
Sunday Game Prep
Pull the week's fantasy projections, compare your roster vs opponent, flag injury updates, suggest lineup moves.
Meeting Prep Briefs
Give Claude the meeting context and get a one-page prep doc with talking points and next steps.
Weekly Review
Every Friday: "Help me review my week. Ask what went well, what didn't, priorities for next week."
Research Anything
Search the web, summarize articles, compare products, explain tax law changes, research competitors.
Quick Data Viz
Upload any spreadsheet and ask for charts: "Show me revenue by quarter" or "Plot my win/loss record."
Claude has a "Projects" feature where you save instructions and files that persist across conversations. Create a project called "Trading" — Claude remembers your context every time.
Do these in order. By next weekend, you'll wonder how you lived without this. Tap to check off each item.
- Redeem Claude Pro (use the gift link in Ch 2!)
- Download the Claude app on your phone
- Turn on Web Search, Code Execution, and Artifacts in Settings
- Set your User Preferences (tell Claude who you are)
- Set up Projects: Trading, Sports, and Client Work
- Send your first 5 prompts — try the examples from Ch 3
- Upload a CSV (trades, expenses, anything) and ask Claude to analyze it
- Ask for a morning market brief and a betting lines dashboard
- Get a personal laptop when you're ready for desktop power tools
- Tell your brother how it went so he can add more ideas to your guide
There's no wrong way to use this. If something doesn't work, tell Claude "that's not what I wanted" and describe the change. The best prompt is the one you actually send.