Claude Code Secrets for PMs: The Operating System, Skills, and Data Viz

Claude Code Secrets for PMs: The Operating System, Skills, and Data Viz

Claude Code: The Fastest B2B Software Ramp

Overview of Claude Code's Success

  • Claude Code has achieved $2.5 billion in annualized revenue within just 9 months, marking it as the fastest ramp for a B2B software product in history.
  • Despite its success, many users still treat Claude Code primarily as a chatbot rather than leveraging its full capabilities.

Context Engineering vs. Prompt Engineering

  • The focus has shifted from prompt engineering to context engineering, emphasizing the importance of managing context effectively.
  • Users often express distrust in AI due to uncertainties about data origins and calculations.

Innovations by Carl Vatti

  • Carl Vatti has transformed Claude Code into an operating system that incorporates native skills and data visualization.
  • A notable feature is the ability to create sub-agents that operate independently, enhancing productivity without adding new abilities to Claude Code itself.

Understanding Claude Code's Functionality

User Interaction with Claude Code

  • Most users interact with Claude Code by typing prompts and receiving outputs; however, Vatti’s approach emphasizes understanding how the tool operates collaboratively.

Subscription and Resources

  • Viewers are encouraged to subscribe on YouTube and follow on podcast platforms for access to valuable AI tools through a newsletter bundle.

The Future of AI Tools: OpenAI and OpenClaw

Recent Developments in AI Tools

  • OpenAI's acquisition of OpenClaw raises questions about the relevance of Claude Code amidst emerging tools like co-work.

Comparison Between Tools

  • While co-work simplifies user interaction with cloud code, it ultimately constrains features available in Claude Code, which remains more powerful for advanced tasks.

Maximizing Efficiency with Cloud Code

Importance for Product Managers

  • For product managers who need direct control over their work processes, Cloud Code is still preferred over newer tools like OpenClaw.

Addressing Friction Areas

  • The discussion highlights four major friction areas encountered while using Cloud Code:
  • Context Management: Strategies to prevent context windows from filling up too quickly.
  • Utilizing Skills: Enhancing Cloud Code’s weaknesses (e.g., research or UI design).
  • Trusting Results: Building confidence in AI-generated outputs for critical documents.

Understanding Cloud Code and Context Management

Importance of High-Quality Work

  • The focus is on ensuring that the work produced using cloud code is high quality and trustworthy, emphasizing reproducibility in results.
  • A cohesive system for utilizing cloud code is essential to prevent disorganization, allowing users to effectively manage their files.

Enhancing Cloud Code Usage

  • Introduction of a method to improve context handling within cloud code, highlighting customization options available in the Cloud Code UI.
  • The use of the cloud code CLI alongside the UI setup is discussed as a streamlined approach for managing tasks.

Setting Up a Status Line

  • Users can customize a status line to monitor context usage throughout conversations, providing insights into how much context has been consumed.
  • The status line can display various elements such as the current model being used and the folder location, enhancing user awareness during operations.

Visualizing Context Usage

  • A visual representation of context usage through color coding (green for ample context, orange for medium, red for nearing limit) helps users manage their prompts effectively.
  • Demonstration of setting up a custom status line shows immediate feedback on context consumption levels.

Managing Context Effectively

  • Emphasis on why managing context is crucial; hitting limits leads to delays due to auto-compaction processes which disrupt workflow.
  • Discussion on how excessive task complexity can quickly consume available context, leading to inefficiencies in using cloud code tools.

The Concept of Context Engineering

  • Transition from prompt engineering to context engineering highlights its significance in maximizing AI tool effectiveness by limiting unnecessary information.
  • Quality improvement occurs when only relevant information is provided while maintaining necessary details for task completion.

Addressing Context Degradation

  • Recognition of "context rot," where conversation quality diminishes over time as more messages are exchanged within limited contexts.

Prototyping with Bolt

  • Introduction of Bolt's prototyping capabilities allows developers to create real front-end code that integrates seamlessly with existing systems rather than creating disposable mockups.

Introduction to Bolt and Amplitude

Overview of Bolt

  • The speaker shares their personal experience with Bolt, stating they use it daily for hosting and enjoy using it late into the night, indicating its engaging nature.
  • A recommendation is made to check out Bolt at bolt.new/aos, emphasizing its user-friendly design.

Introduction to Amplitude

  • The episode is sponsored by Amplitude, highlighting the importance of mobile user engagement in product development.
  • Many session replay tools are criticized for not capturing a complete picture of user interactions due to limitations like choppy replays or missing key moments.

Understanding Context Management in Cloud Code

Managing Context Effectively

  • The speaker discusses the significance of context management in cloud code, mentioning that users can clear sessions to start fresh.
  • They introduce the command slashcontext as a tool for checking how much context is being utilized during operations.

Analyzing Context Usage

  • Initial context usage is reported at 16%, with breakdown details provided on what consumes this context (e.g., system prompts and enabled tools).
  • Users are encouraged to disable unnecessary tools to optimize context usage effectively.

Utilizing Sub Agents for Improved Efficiency

Task Execution with Sub Agents

  • The speaker demonstrates how sub agents can be employed to handle tasks without consuming main session context.
  • By running a command through a sub agent instead of directly in the main session, users can save significant amounts of context space.

Benefits of Using Sub Agents

  • Utilizing sub agents allows Claude (the AI tool being discussed) to perform tasks independently while returning only summarized results back to the main session.
  • This method prevents excessive consumption of context resources during routine tasks like web searches.

Conclusion on Context Management Techniques

Summary of Findings

  • The discussion emphasizes that using sub agents can significantly reduce context usage from 25% down to just 16.5% during typical operations.
  • It highlights that both on-the-fly task creation and predefined sub agents are effective strategies for managing workload efficiently within cloud code environments.

Understanding Claude's Sub-Agent Functionality

Overview of Tool Usage and Token Management

  • The session utilized 10 tool uses, consuming nearly 30,000 tokens, indicating a significant amount of information retained from the main session through the use of a sub-agent.
  • Understanding how cloud code operates is crucial; it should dynamically create agents when necessary, although it often fails to do so even when beneficial.

Effective Use of Main Session vs. Sub-Agents

  • Users can guide Claude on its operational methods, enhancing collaboration rather than merely prompting it. This understanding elevates user interaction with Claude.
  • A specific skill called "spin up" can be employed to encourage Claude to utilize sub-agents effectively during lengthy tasks.

Skill Configuration and Context Management

  • By appending "spin up" to prompts, users can instruct Claude to run tasks in parallel using dedicated sub-agents instead of relying solely on the main session.
  • Demonstration of stopping commands in the UI involves pressing escape twice, which also allows users to roll back context if previous questions were incorrect or unhelpful.

Editing Skills for Improved Performance

  • The discussion transitions into fixing the spin-up skill by deleting existing configurations that are not optimal for user needs.
  • Users are encouraged to create new skills tailored for specific tasks like managing context windows effectively between main sessions and sub-agents.

Caution Regarding External Skills and Marketplaces

  • A warning is issued against downloading skills from untrusted marketplaces due to potential malware risks; it's safer to develop personal skills or obtain them from trusted sources.
  • Emphasis is placed on creating personalized skills based on repetitive workflows for maximum efficiency and relevance in project management.

How to Effectively Use Cloud Code Features

Skill Invocation and Context Management

  • The last episode discussed issues with triggering skills; using a slash command or context guard skill in prompts can mitigate these problems.
  • A context card was applied for a web research task, allowing multiple searches and page reads while preserving the main session.
  • It's unnecessary to see all web search results; only the final output is needed for effective task completion.

Background Processing with Sub Agents

  • Using Control+B allows sub agents to run in the background, enabling continued conversation without waiting for results.
  • Users can navigate to view what the local agent is doing while maintaining their main chat flow.

Utilizing Cloud Code's Ask User Questions Tool

  • The "ask user questions" tool is highlighted as a favorite feature of Cloud Code, enhancing interaction by generating relevant questions based on user input.
  • This tool helps gather requirements efficiently by asking targeted questions about potential cloud code implementations.

Dynamic Interaction and Custom UI

  • Claude generates a custom UI that presents options for implementing cloud code scripts, streamlining decision-making processes.
  • Users can select desired scripts through an intuitive interface, which then retains this information for future reference.

Enhancing Clarity Through Questioning

  • The ask user questions tool addresses assumptions and gaps in understanding by prompting users with clarifying inquiries.
  • Strong prompts encourage extensive questioning from Claude, leading to comprehensive discussions that refine project specifications.

Cloud Code Skills and AI Design

Enhancing AI Output with Clarifying Questions

  • The importance of using the "ask user questions" tool is emphasized for gaining context, which can lead to better outputs from AI during project initiation.
  • Encouragement to ask clarifying questions whenever necessary to improve understanding and results.

Identifying Opportunities for Skill Creation

  • Recognizing repetitive tasks in workflows as prime opportunities for creating new skills that enhance efficiency.
  • Suggestion to explore areas where Cloud Code may be lacking, prompting the development of skills or prompts that address these weaknesses.

Notable Plugins and Skills in Cloud Code

  • Introduction of the Cloud Code marketplace via the command /plugins, highlighting official plugins as reliable options.
  • Mention of Claude's 56 official plugins, particularly a front-end design skill aimed at improving UI quality beyond generic designs.

Real-world Application of Front-end Design Skill

  • A personal example shared about creating a landing page using AI, showcasing its capabilities in generating effective web pages.
  • Comparison between initial output and improved design through the use of front-end design skills, illustrating how specific skills can enhance creativity and personality in web design.

The Power of Effective Prompts

  • Discussion on how some skills do not require complex coding but rather rely on well-crafted prompts that guide AI behavior effectively.
  • Emphasis on crafting clear rules within prompts to direct AI towards desired outcomes without introducing new technical abilities.

Conclusion: Skills vs. Tools

  • Acknowledgment that while powerful skills can exist without tools, integrating tools enhances their effectiveness significantly.

AI Product Management Course Overview

Course Recommendations and Collaborations

  • The speaker highly recommends the AI Product Management (AIPM) course, emphasizing its collaborative nature with experts in AI product strategy.
  • Pavle Hearn, a frequent collaborator and Build Labs leader, will provide feedback during the live build of an AI product for participants in the AIPM certificate program.
  • Participants are encouraged to use a specific code and link for a special discount on the course.

Enhancing Skills with Claude

Utilizing Skills for Improved Research

  • There are two primary methods to enhance skills: creating a skill that instructs Claude to utilize official tools or conducting general web searches.
  • The speaker critiques Claude's web search capabilities, noting that results can be unreliable as they often pull from top Google links without quality assurance.

Tools for Better Research Outcomes

  • The speaker argues that providing better tools can improve Claude's research reliability, countering common criticisms about its performance.
  • One tool mentioned is Tavi, which offers higher quality search results compared to traditional web searches.

Advanced Tools: Firecrawl and CLIs

Introduction to Firecrawl

  • Firecrawl is introduced as a tool that scrapes URLs to extract clean markdown content, eliminating unnecessary HTML and JavaScript clutter.

Command Line Interfaces (CLIs)

  • The discussion shifts towards Command Line Interfaces (CLIs), highlighting their resurgence due to AI's proficiency in using them effectively.
  • CLIs allow tools to operate directly from the user's machine without consuming context space within Claude’s environment.

The Future of Tool Integration

Preference for CLIs Over MCPs

  • The speaker suggests that CLIs may become preferred over Managed Cloud Providers (MCP), citing ease of use and reliability as key factors.

Practical Applications of CLIs

  • Examples include GitHub CLI and Versell CLI; both are deemed essential for developers working with these platforms due to their powerful functionalities.

Key Takeaways on Tool Usage

Recommendations for Developers

  • A strong recommendation is made against using MCP systems in favor of leveraging available CLIs for enhanced productivity and efficiency.

Web Research and AI Tools

Enhancing Web Search with AI

  • The speaker discusses using tools like Tavly for web research and Firecrawl for scraping pages, emphasizing that while web search alone may not be effective for AI, combining it with these tools significantly enhances its capabilities.

Creating Visual Content with Claude

  • The speaker notes that Claude performs better with web page content but struggles with graphic design tasks such as creating slides, often resulting in poorly aligned or inadequately filled layouts.

Iterative Improvement in Slide Creation

  • To improve slide quality, users are encouraged to ask Claude to create a slide in HTML format and then provide feedback on specific issues, promoting an iterative process of refinement.

Self-Validation Techniques for AI Design

  • A key strategy discussed is enabling Claude to check its own work. This self-validation can lead to significant improvements in visual design outputs by integrating code-based tools into the skill set.

Advanced Skill Development: Make Slides

  • The "Make Slides" skill incorporates advanced features allowing Claude to read dimensions and layouts while utilizing Puppeteer—a front-end development tool—to take accurate screenshots of rendered HTML pages.

Improving Quality Through Repetition

Importance of Iteration in Design Tasks

  • The speaker emphasizes the value of requiring multiple iterations (e.g., three rounds of improvement) before presenting final designs, which leads to higher quality outcomes from AI-generated content.

Leveraging Redundancy for Better Results

  • Citing recent research, the speaker mentions that repeating prompts can enhance output quality. They have successfully implemented this technique across various skills by prompting Claude to double-check its work after initial execution.

Builder Validator Pattern Explained

  • The discussion introduces the "builder validator pattern," where running a prompt twice allows AI to reflect on its adherence to rules, thus improving overall output quality through self-assessment.

Auto Invoking Skills: A New Frontier

Exploring Auto Invocation Capabilities

  • The conversation shifts towards auto-invoking skills within the system. This feature aims at enhancing user experience by automating certain processes based on user commands or context cues.

Cloud Code and AI Skills Integration

Challenges with Auto Invocation of Skills

  • The auto invocation of skills in cloud code is finicky, leading to challenges when trying to create presentations or slides based on user prompts.
  • A simple method to manage AI skills is through Claude MD, but it requires constant updates which can consume unnecessary context.

Utilizing Hooks for Enhanced Functionality

  • Hooks are mechanisms that allow actions to occur at various points in the cloud code workflow, such as before or after message compaction.
  • An example use case for hooks includes ensuring new markdown files have specific formatting upon creation.

Implementing User Prompt Submit Hook

  • A user prompt submit hook triggers a script every time a message is sent, checking if any words match existing skill keywords.
  • This approach allows the LLM (Language Learning Model) to decide when it's appropriate to utilize certain skills based on keyword matches.

Trusting AI Outputs in Data Analysis

  • Product managers often express concerns about trusting AI outputs, especially regarding data analysis accuracy and reliability.
  • There’s a significant need for transparency in how AI generates results, particularly when presenting data findings to stakeholders.

Enhancing Visibility with Jupyter Notebooks

  • Jupyter notebooks serve as an effective tool for analysts by providing visibility into queries and results generated by cloud code.
  • These notebooks can visualize data analysis processes directly within tools like Cursor or VS Code, enhancing usability without switching contexts.

Practical Example: Analyzing Survey Responses

  • The discussion includes analyzing survey responses from users of a fictional company using cloud code within a Jupyter notebook environment.
  • This practical example illustrates how cloud code can simplify data handling and visualization compared to traditional CSV formats.

Understanding Jupyter Notebooks and Their Applications

Introduction to Jupyter Notebooks

  • A new file is created in a Jupyter notebook, showcasing simple code execution in Python.
  • The notebook facilitates live debugging and presents data columns, addressing the need for traceable analysis in data science.

Features of Jupyter Notebooks

  • The notebook displays overall data shape, including rows and columns, along with example outputs.
  • Users can perform sophisticated analyses independently without waiting for analyst availability, enhancing exploration capabilities.

Visualizing Data

  • Transitioning from raw data to visual representation, users can create charts like bar graphs to illustrate distributions.
  • Cloud code aims to replicate roles within organizations (e.g., analysts), making complex tasks more accessible through simplified tools.

Advanced Analysis Techniques

  • Users can request advanced analyses such as correlation heat maps to identify patterns among numeric columns.
  • Collaboration with AI allows users to derive insights from data while formulating effective prompts for deeper analysis.

Practical Applications of Insights

  • Creating sub-agent structures within cloud code helps streamline analytical processes by outsourcing thinking tasks.
  • Correlation analysis reveals significant relationships between variables (e.g., enterprise interest in security vs. pricing flexibility), providing actionable insights that would typically require extensive time from human analysts.

Understanding Regression Testing and Cloud Code Management

The Importance of Regression Testing

  • Regression testing encompasses various types that enhance confidence in data accuracy, allowing analysts and managers to verify the source of AI-generated results.
  • Effective execution of regression tests requires understanding their components, which can significantly improve transparency in AI processes.

Building an Effective Cloud Code System

  • A major challenge is integrating different features into a cohesive system for cloud code management, including context management skills and sub-agents.
  • Identifying where to place context layers and information types within the overall system is crucial for effective organization.

Structuring Knowledge Folders

  • Establishing a knowledge folder with essential references helps streamline communication during meetings by providing relevant background information about colleagues or projects.
  • Investing time in organizing context can drastically improve output quality, avoiding generic responses often labeled as "AI slop."

Utilizing Project Folders for Efficiency

  • Creating project-specific folders allows for organized documentation of tasks, making it easier to track progress and gather necessary materials for future reference.
  • This method facilitates seamless transitions between projects or team members by consolidating all related research and notes into one accessible location.

Project Management and Cloud Code Integration

Organizing Projects with Cloud Code

  • The projects folder serves as a centralized location for all project-related artifacts, making it easy to access previous work when needed.
  • A suggestion is made for a one-time download process to build out project folders quickly by pulling in essential documents like PRDs and feature write-ups.

Utilizing Standup Commands

  • Introduction of a "start standup" command that aggregates information from various sources such as GitHub, tasks, and calendars.
  • This command simplifies the process of gathering necessary data without needing to check multiple platforms individually.

Enhancing Workflow Efficiency

  • Emphasis on the importance of having all relevant information accessible within cloud code, reducing the need to switch between different applications.
  • The ability to ask complex questions about website traffic in relation to social media posts highlights the analytical power of integrated systems.

Structuring Data and Tasks

  • Discussion on maintaining organized files for ongoing tasks and ideas that may not be immediately actionable but are worth noting.
  • Connecting cloud code with task management tools like Apple Reminders or Todoist can enhance productivity by streamlining task tracking.

Tools and Meeting Preparation

  • A dedicated tools folder is recommended for storing scripts that automate processes like meeting preparation or analytics gathering.
  • Pre-built scripts allow users to efficiently pull metrics or prepare for meetings without starting from scratch each time.

Maintaining Contextual Awareness

  • The overall cloud file plays a crucial role in providing context during interactions with cloud code, ensuring relevant information is always available.
  • Including personal details about how one prefers to work helps tailor responses from the system, enhancing user experience through personalized interaction.

Cloud Code Insights and Resources

Importance of Cloud MD Files

  • Emphasizes the value of continuously updating your cloud MD file, suggesting that it should be revised every week or month as issues arise with cloud code.
  • Highlights that maintaining an updated CloudMD file can provide significant insights and improvements over time.

Learning Resources from Carl

  • Introduces CC for PMS, a free course on cloud code tailored for product managers, available at cc4pms.com.
  • Mentions another version, CC for everyone.com, which offers a more general approach to the same content.

Course Structure and Engagement

  • Describes the unique teaching method where lessons are delivered through cloud code itself, allowing users to interactively learn by starting lessons directly in the platform.
  • Encourages audience engagement by inviting them to subscribe and comment on whether they would like to see Carl return for future discussions.

Closing Remarks and Call to Action

  • Expresses gratitude towards Carl for his participation in the show and encourages viewers to engage with the content through likes and comments.
  • Urges listeners to follow on various platforms (Apple Podcasts, Spotify, YouTube), emphasizing how this support helps improve show quality and reach.

Turn any video into a summary like this

YouTube links, meetings, lectures. With transcripts, search, and chat.

Video description

Carl Vellotti returns for his 3rd episode. His first two crossed over 1M views. Today he shows how to turn Claude Code into a full PM operating system with context management, sub-agents, self-checking skills, and Jupyter notebooks. Full Writeup: https://www.news.aakashg.com/p/carl-vellotti-3 Transcript: https://www.aakashg.com/carl-vellotti-podcast-3/ --- Timestamps: 0:00 - Intro 1:40 - Does Claude Code still matter vs Cowork and OpenClaw 6:51 - Setting up the context status line 10:41 - Ads 12:03 - Sub-agents for context preservation 17:49 - Creating skills live 23:58 - The ask user questions tool 31:13 - Ads 33:33 - Tool-powered skills with Tavily and Firecrawl 36:57 - CLI vs MCP vs API hierarchy 39:30 - Make slides skill with Puppeteer 43:32 - Auto-invoking skills with hooks 46:49 - Jupyter notebooks for data trust 55:09 - The operating system file structure 1:05:58 - Outro --- 🏆 Thanks to our sponsors: 1. Bolt: Ship AI-powered products 10x faster - https://bolt.new/solutions/product-manager?utm_source=Promoted&utm_medium=email&utm_campaign=aakash-product-growth 2. Amplitude: The market-leader in product analytics - https://amplitude.com/session-replay?utm_campaign=session-replay-launch-2025&utm_source=linkedin&utm_medium=organic-social&utm_content=productgrowthpodcast 3. Pendo: The #1 software experience management platform - http://www.pendo.io/aakash 4. NayaOne: Airgapped cloud-agnostic sandbox - https://nayaone.com/aakash/ 5. Product Faculty: Get $550 off their #1 AI PM Certification with my link - https://maven.com/product-faculty/ai-product-management-certification?promoCode=AAKASH550C7 --- Key Takeaways: 1. Context management is the real skill - A single web search eats 10% of your context. Run /context to see what is consuming it. System prompt and MCPs take 10-16% before you type one message. 2. Sub-agents save 20x context - Delegate research to a sub-agent. Same task costs 0.5% instead of 10%. Your main session only gets the summary. 3. Replace MCPs with CLIs - MCPs eat context by existing. CLIs have zero overhead. GitHub CLI, Vercel CLI, Google Workspace CLI are all dramatically more efficient. 4. Powerful skills need zero code - Anthropic's front-end design plugin is just a good prompt. No APIs or tooling. Just rules that tell Claude "do not look like AI." 5. Give Claude self-checking tools - The make slides skill uses Puppeteer to screenshot output, measure overflow, and fix issues before you see them. 6. Repeat prompts for better quality - A Google paper showed pasting a prompt twice helps. Tell Claude to double-check against skill instructions after the first pass. 7. Use hooks to auto-invoke skills - A user_prompt_submit hook matches your words against skill keywords instantly. Zero context cost. 8. Jupyter notebooks solve data trust - Every analysis shows exact code, inputs, and outputs. Traceable and reproducible. 9. Build an operating system - Knowledge folder for people context. Projects folder for task isolation. Tools folder for scripts. CLAUDE.md for identity. 10. The people folder compounds - Connect meeting transcription. After every meeting, update each person's dossier. Every prompt gets more specific over time. --- 👨‍💻 Where to find Carl Vellotti: LinkedIn: https://www.linkedin.com/in/carlvellotti/ Twitter/X: https://x.com/carlvellotti Newsletter: The Full-Stack PM 👨‍💻 Where to find Aakash: Twitter: https://www.x.com/aakashg0 LinkedIn: https://www.linkedin.com/in/aakashgupta/ Newsletter: https://www.news.aakashg.com #claudecode #aipm --- 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications to get more videos like this.