How We Do AI - Two Professionals. One Mindset.
Tom and Paco showcase their newly upgraded membership platform built with Claude Code and the new Claude Design tool, demonstrating how AI is deeply embedded in their daily business operations. They walk through the redesigned iCore learning platform featuring structured lesson navigation, downloadable resources, and an AI community manager. The episode also touches on Opus 4.7 improvements, Claude Design's slide deck and UI prototyping capabilities, and a broader philosophy about AI as a productivity partner rather than a replacement.
Summary
Tom and Paco open the session by announcing major changes to their 'my iCore' membership platform, which they built entirely using Claude Code starting in June of the previous year. They quickly pivot to discussing the newly released Claude Design tool and Anthropic's Opus 4.7 model, sharing their real-world experiences using both in their business.
Tom demonstrates Claude Design live, explaining how it functions as a separate web application tied to a Claude subscription. He walks through how he fed in their GitHub repository and brand guidelines to create a design system, then used it to generate UI components like a new commenting system, course navigation layouts, and a slide deck — all matching their existing branding automatically. He highlights the 'handoff to Claude Code' feature, which generates a command that Claude Code uses to access the design files directly within the actual codebase, eliminating the need to manually link design assets.
The platform overhaul is shown in detail: the new iCore Journey view presents lesson quality scores horizontally across all courses, allowing members to spot weak areas at a glance and jump directly to relevant lessons. Each lesson now has a structured layout with a magic slide, TLDR, cheat sheet, full 30,000-word guide broken into sections, and downloadable ZIP files for workshop-style courses. Tom contrasts this with typical platforms like Circle and Mighty Networks, which he says cannot handle the volume and asset variety their content requires.
Paco describes using Claude Design to prepare a presentation for his company's annual convention, noting how Claude's accumulated context — stored conversations, notes, images, and thoughts gathered throughout the year — can now be combined with design preferences to generate polished slide decks without needing a professional designer. Both hosts emphasize that this reduces dependency on external collaborators and removes friction from the creative process.
The hosts address two community questions: one about Andrej Karpathy's LLM wiki approach to PKM, which Tom argues lacks a defined methodology compared to their iCore system, and one about an AI context file, which Tom redirects to the iCore MCP server — a tool members can connect to Claude Desktop that gives the AI access to their full iCore framework, tool stack, learning resources, and journey progress.
They discuss their AI team structure, which includes named agents like 'Checks' (a community manager agent) and 'Felix' (a front-end developer agent), orchestrated through a system Tom uses daily inside his iCore setup. They note that Checks responds to community questions based on knowledge from all courses and past coaching sessions, and can cite specific timestamps from recorded sessions.
Paco closes with a personal reflection on how a well-configured AI system eliminates the professional solitude that entrepreneurs and executives often feel, arguing that a deeply contextualized AI acts as a genuine thinking partner that improves decision-making. Both hosts confirm the platform has reached 4,000 members, with nearly 1,000 joining in the current month.
Key Insights
- Tom argues that Claude Design's 'handoff to Claude Code' feature is a breakthrough because it allows Claude Code to access design files directly within the actual codebase via a single command, eliminating the manual linking of design assets and producing much better context-aware code changes out of the box.
- Tom claims that Opus 4.7 represents a dramatic improvement over previous weeks, where token limits were hit quickly and output quality was poor during coding sessions — stating he now runs it on 'high effort' mode for extensive code changes without hitting token issues.
- Paco argues that a well-configured AI system eliminates the professional solitude felt by entrepreneurs and CEOs, claiming his own decision-making has measurably improved because the AI acts as a partner that knows his full context — effectively functioning as an extension of himself.
- Tom contends that standard membership platforms like Circle and Mighty Networks structurally fail when content volume and asset variety are high, and that building a custom Claude Code application gave them the flexibility to create lesson layouts that those platforms cannot support.
- Tom responds to Andrej Karpathy's LLM wiki approach by arguing it lacks a defined methodology or system, and that simply creating index folders connected to Obsidian does not constitute a meaningful advancement over what anyone can already do — contrasting it with their iCore MCP server which provides the AI with structured access to a member's full learning journey and tool stack.
Topics
Full transcript available for MurmurCast members
Sign Up to Access