CHAPTERS
Why advanced users live inside Claude Code (and what’s in this masterclass)
Aakash welcomes Carl back for an advanced masterclass, framing Claude Code as an all-day work environment for PMs—not just a chatbot. Carl previews the core themes: connecting Claude to external tools via MCP, using reusable Skills, and automating work through GitHub.
How Claude Code reached $1B ARR fast: depth over breadth
They unpack why Claude Code surged amid competition (Codex, Google’s tools). Carl argues Anthropic wins by going deep on work/coding workflows for power users, plus shipping first-mover standards like MCP and Skills that others copy.
Getting real productivity (workflow mindset vs. one-off prompting)
Carl explains what separates beginners from advanced users: building repeatable workflows and files/rules so Claude can run multi-step tasks in one shot. Aakash shares why Claude Code feels ‘limitless’ for long downloads/analysis compared with the web UI.
MCP foundations: connecting Claude to your work tools (setup + auth)
Carl demonstrates installing and authenticating an MCP server using Linear as the example. They explain MCP as the standard way LLMs connect to services, how tools appear inside Claude, and why toggling MCPs matters for context-window efficiency.
Essential MCP stack for PMs + MCP vs. API decision rule
They map common PM systems to MCP opportunities: docs, Slack, research platforms, analytics, support, CRM, etc. Carl contrasts MCPs (pre-defined tools, easy) with APIs (flexible but require scripts and documentation context).
End-to-end workflow kickoff: survey creation → Google Docs publishing
The live demo begins with a fictional product (Taskflow) building a calendar integration feature. Claude drafts a user research survey from local context files, saves a markdown copy locally, and publishes it into Google Docs via the Google Workspace MCP.
Survey responses ingestion and synthesis (and why Skills matter)
Carl pulls survey responses from Google Drive into Claude and attempts synthesis. This becomes a springboard to discuss Skills: auto-invoked task recipes that standardize outputs—though they note invocation can be unreliable, so explicit calls often work best.
Skills deep dive: sources, plugins marketplace, and security cautions
They show multiple ways to acquire Skills: copying from GitHub repos, trusted curations, and installing plugin bundles (e.g., Anthropic’s document skills). They also warn about prompt-injection risks when importing third-party Skills—especially in ‘dangerously skip permissions’ mode.
Image generation via Gemini API inside Claude Code (API workflow)
Carl demonstrates using a Gemini image-generation API key stored in a .env file and a custom script to generate visuals from within Claude Code. They highlight why doing this in-code helps: reusable brand guidelines, prompt automation, and parallel variations—plus the idea of making a dedicated image-prompting Skill.
From research to PRD to user journey diagram (Skill-assisted artifacts)
Claude generates a PRD from the synthesized research and publishes it to Google Docs. They add a user journey map/diagram to the PRD content, noting Skills may require explicit invocation but still enable rapid creation of structured artifacts.
Hooks feature: automations triggered during Claude’s lifecycle
Carl introduces Hooks—automated actions triggered at key moments (session start/end, before/after tool use, before compaction). A simple example aims to create Mac notifications when tasks complete, then they discuss more advanced possibilities like auto-running tests or exporting chats before compaction.
PRD → stakeholder deck generation (PowerPoint/Slides automation)
Using installed document/presentation Skills, Claude turns the PRD into a fully editable Google Slides-style deck. They emphasize this is not just images—elements are editable—and discuss future improvements like visual feedback loops using Playwright/Puppeteer for layout iteration.
Auto-creating engineering tickets in Linear (19 issues + priorities)
Claude converts the updated PRD into structured engineering tickets and creates them directly in Linear via MCP—complete with priorities, acceptance criteria, and technical notes. They note tickets can become even more detailed if Claude is connected to the actual codebase.
GitHub integration: syncing work and using Claude as a remote worker
They push the local repo to GitHub to make the workflow portable and collaborative. Then they add the Claude GitHub App and show how @claude can respond to issues—enabling “remote work” where Claude completes changes while you’re away, with a primer on Git basics for PMs.
Closing guidance: where Claude Code fits best for PMs
They wrap by recommending a mindset of experimentation and progressive workflow-building, acknowledging occasional demo friction. Aakash suggests using Claude Code for high-leverage, complex tasks (MCPs, heavy context, large downloads) while the UI still suits lighter work.
