Aakash GuptaI should be charging $999 for this Claude Code Tutorial
CHAPTERS
Claude Code’s breakout growth and what you’ll learn
Aakash introduces Claude Code’s rapid adoption and frames the episode as a beginner-to-hero tutorial. Carl Vellotti joins to show practical workflows, especially for product managers, and why the terminal-based interface changes how you work with LLMs.
Why PMs should care: escaping chatbot limitations with workflows
Carl explains why Claude Code matters even if you’re non-technical: it moves you from a chat box into a flexible file-system-driven workflow. The key theme is “context engineering”—feeding the model structured, reusable context so outputs are more useful and repeatable.
Claude Code vs Copilot/Cursor/other CLIs: where it wins
The conversation compares Claude Code to IDE-first assistants and other terminal/CLI agents (Gemini CLI, OpenAI Codex). Carl argues Claude Code is polished, strong at tool use and agent behavior, and especially strong for writing-heavy tasks PMs do daily.
Installation and first launch: one-command setup + basic commands
Carl walks through installing Claude Code from Anthropic’s quick start and launching it in the terminal. He demystifies the terminal, shows the basic chat-like interaction, and introduces the “clear” workflow to manage context.
Working in a project folder: file-based Q&A on customer interviews
Using a prepared demo repository (a fictional company wiki), Carl shows how Claude Code can automatically inspect directories and read files. He asks for counts and summaries of interview transcripts and compares insights across industries to demonstrate fast synthesis.
Web search + token visibility + image input inside the terminal
Carl demonstrates Claude Code’s web search and discusses how token counting makes usage/cost more tangible than typical chat apps. He also shows that despite being terminal-first, you can drag in images for analysis and feedback (useful for debugging or reviewing assets).
Running code + using GitHub repos: transcript extraction demo
Claude Code is shown running real code: Carl provides a GitHub repo for a YouTube transcript API and asks Claude to fetch a transcript and save it to a markdown file. The key moment is Claude generating a task checklist and executing step-by-step without manual engineering work.
Using Claude Code inside Cursor: viewing files and a cost-effective setup
Carl shifts into an IDE (Cursor) to visualize and edit generated files while continuing to run Claude Code in the integrated terminal. He explains a hybrid approach: use Claude Pro (Sonnet) for research/writing and Cursor for heavier coding models when needed.
Project initialization: `init` and the persistent CLAUDE file memory
Carl introduces `init`, which scans the repo and generates/updates a `CLAUDE` file describing structure and instructions. This file acts like persistent project memory: rules, style guides, and guardrails that Claude references every session, reducing repeated context setup.
PRDs with context engineering: combining business info, styles, and examples
Carl demonstrates a “super prompt” that pulls business context, writing-style guides, and example PRDs from folders, plus web research (e.g., GPT real-time). Claude generates a structured PRD and writes it to a file, showing how reusable context assets dramatically simplify PM writing.
Reusable slash commands: consistent meeting notes and internal messaging
Carl shows custom slash commands (saved prompts) to standardize outputs like meeting notes. He then combines meeting transcript context + writing tone files to draft a Slack follow-up message, illustrating how teams can avoid “generic AI voice” and keep outputs in a personal/company style.
Plan Mode for complex tasks: prompt/model testing harness
Carl introduces Plan Mode (Shift+Tab) to prevent premature file edits while designing an approach. He builds a workflow to generate multiple summarization prompts and run them across multiple LLM APIs, then iterates on the plan to control file structure before executing.
Agents and sub-agents: parallel work + role-based review personas
Carl demonstrates parallelization by spinning up multiple sub-agents to analyze separate interview files simultaneously. He then shows role-based agents (designer/engineer/executive) to review a PRD from different perspectives, and pulls new agents from online registries to expand capabilities fast.
MCPs and tool extensions: Reddit mining + PM-focused opportunities
The episode explains how MCPs extend Claude Code with specialized tools (e.g., Reddit access), enabling workflows that normal web search or scraping can’t reliably do. Carl highlights how PMs can use MCPs for continuous insight gathering (communities, competitors) and points out a gap: most shared agents/tools are still engineering-centric.
Where Claude Code is best + prototyping demo + avoiding ‘manifestation hell’
Carl summarizes Claude Code’s strengths for PMs (research, writing, synthesis, lightweight prototyping) and demonstrates building a simple workflow-builder UI from a spec. They discuss evals, safe use with engineering teams, and best practices like Plan Mode and staying in the loop to avoid unproductive loops.
Claude Code adoption, PM agent strategy, and Carl’s Instagram ‘agent’ stack
They reflect on why Claude Code grew fast (coding bet + strong writing + intent understanding) and how PMs should choose between tactical agents (Claude Code) vs recurring automations (n8n/Lindy). The conversation then pivots to Carl’s Instagram growth and his internal “Meme Mage” tool that uses LLMs/templates/personas to generate meme captions.
Outro: Carl’s Fullstack PM newsletter and next steps
Carl shares his transition from PM roles to building a community/newsletter for “builder PMs,” focusing on modern AI tooling. Aakash closes with where to find links/docs and a call to subscribe/follow/review.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome