Today kicked off something new for the Vibe Coders community: Daily Vibes. This was our very first one, and it set the tone for what these sessions are meant to be—casual, exploratory, and practical. Think of them as short, focused hangs where we test ideas, tools, and workflows in real time instead of over‑polishing presentations. Here’s how it’s going to work going forward: Daily Vibes will happen Monday through Thursday, usually around 10AM CST. They won’t be long—expect anywhere from 10 to 30 minutes depending on the topic and how deep we go. Some days we’ll be testing new tools. Other days we’ll be breaking down workflows, reviewing experiments, or just talking through how we’re actually using AI day‑to‑day as vibe coders. No slides. No sales pitch. Just real work, live. Today’s session was intentionally loose. It was about stress‑testing Claude Desktop's new 'Cowork' feature, poking at Obsidian workflows, and seeing what happens when you give AI real files and real constraints. That’s exactly the spirit of these Daily Vibes. If you caught it live—awesome. If you’re watching the replay, you’re still very much part of it. Show up when you can. Lurk when you want. Jump in when something clicks. This is about building momentum, together, one vibe at a time.

What a call today. If you’ve been feeling overwhelmed by the sheer number of “best” tools in vibe coding right now… you’re not alone. One of the biggest themes in this session was tool fatigue: there are so many options (Lovable, Replit, Bolt, Claude Code, AI Studio, etc.) that it’s hard to settle on a workflow long enough to actually ship. A few highlights from the conversation: 1) The new bottleneck isn’t coding — it’s merging work We talked about orchestration tools (Maestro/Beads/Conductor, Gastown, Graphite) and why “merge” is the next wall: multiple agents, multiple worktrees, multiple changes… but how do you reliably bring it back together without chaos? 2) Don’t build first. PRD first. Gary shared a super common experience: jumping straight into a builder (Bolt/Lovable) and getting something that looks “functional,” but then getting stuck trying to update it, improve it, or keep it current—while burning through tokens doing basic changes. The big unlock: start with a PRD. When you do the thinking up front, you massively reduce the “rebuild, redo, retokenize” loop later. 3) BMAD as an on-ramp (and multiplier) We demo’d a quick BMAD setup and talked through how it acts like an agile team in a box: analyst, architect, PM, dev, test, UX, etc. The point isn’t to worship any framework—the point is to force clarity before you start generating code. Once you have a PRD, you can drop it into: - Google AI Studio (fast + strong frontend) - Lovable/Replit (great for MVPs)…and you’ll get way closer to what you actually meant. 4) The “cheap loop” trick: big changes in builders, small changes locally A practical workflow that came up: 1. Generate the base app in Lovable (or AI Studio) 2. Push to GitHub 3. Pull locally and do the small tweaks with VS Code + Claude Code/Roo Code (pay-as-you-go) 4. Push back when you need a big feature → sync back into the builder This keeps you from hitting daily limits and wasting credits on tiny edits.

Just had a great conversation that covered the entire arc of software development — from legacy systems to modern AI-assisted shipping. Brad walked through how he shipped his first live web app running on Windows Server / IIS with a Microsoft SQL Server backend — largely guided by AI prompts, with real-world corrections applied using deep Windows experience. We then zoomed out into why vibe coding feels like a full-circle moment: after years in executive and business roles, AI agents make it possible to return to building without being blocked by today’s frameworks. What we covered - Shipping a live IIS + SQL Server app with AI-assisted deployment - Career arc: COBOL, punch cards, IBM System/360 → modern web apps - Why shipping something live (even basic) matters - Working through Corbin Brown’s Thumbio course - Using vibe coding to rapidly recreate complex apps Token limits & tooling reality We talked candidly about token limits and how heavy builders hit them fast. Several strategies came up: - OpenRouter for buying credits and routing across models - Using different models for different tasks (Gemini for frontend, Claude for coding) - Why open-source IDE agents move faster than locked tools Skills, MCP, and the future of agent workflows A big chunk of the conversation focused on Skills and why they matter. - Skills load metadata first, full instructions only when triggered - This enables progressive disclosure and smaller context windows - Skills act like a standardized “dotfile protocol” for AI tools - MCP handles tools; Skills handle instructions Product ideas sparked - Browser plugins that allow AI-driven changes within constraints (e.g. bulk calendar color rules) - Proposal & marketing document tools where users say: “Move the logo, add padding, center it” — no massive UI needed - Using Skills as customizable, client-specific branding & layout engines A powerful habit: prompts as source code One standout practice: - changes.md — what the AI changed in each session - prompts.md — every prompt used to get there