<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AP Squared</title>
    <description>The latest articles on DEV Community by AP Squared (@apsquared).</description>
    <link>https://dev.to/apsquared</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2990269%2Fba021743-a238-4784-a4b8-e7fdb9aa8c56.png</url>
      <title>DEV Community: AP Squared</title>
      <link>https://dev.to/apsquared</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/apsquared"/>
    <language>en</language>
    <item>
      <title>How to Turn a Real MCP Session Into a Demo Video Without Screen Recording</title>
      <dc:creator>AP Squared</dc:creator>
      <pubDate>Sat, 07 Nov 2026 21:44:48 +0000</pubDate>
      <link>https://dev.to/apsquared/how-to-turn-a-real-mcp-session-into-a-demo-video-without-screen-recording-1937</link>
      <guid>https://dev.to/apsquared/how-to-turn-a-real-mcp-session-into-a-demo-video-without-screen-recording-1937</guid>
      <description>&lt;p&gt;&lt;strong&gt;Why AI Chat Demos Are So Hard to Record Well&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You built an MCP server, a ChatGPT app, or an agent skill. Someone can ask a question, your tool runs, and something useful appears.&lt;/p&gt;

&lt;p&gt;Now you need a video that shows it.&lt;/p&gt;

&lt;p&gt;You open a screen recorder, start a fresh conversation, and type your prompt. The assistant thinks. Your tool starts. A spinner turns. Eventually, the answer arrives.&lt;/p&gt;

&lt;p&gt;The workflow worked. The video is mostly waiting.&lt;/p&gt;

&lt;p&gt;That’s the awkward part of demonstrating products that live inside AI chats: a successful session and a good demo video have very different pacing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The useful moment needs context&lt;/strong&gt;&lt;br&gt;
With a conventional app, you can often start a recording on the screen that matters. A dashboard already contains the chart. A search page already contains the results.&lt;/p&gt;

&lt;p&gt;In a chat, the result makes sense because of what happened before it.&lt;/p&gt;

&lt;p&gt;The viewer needs to see the request, understand that the assistant called your tool, and connect the response to the original question. Skip too much and the result seems disconnected. Include everything and the demo drags.&lt;/p&gt;

&lt;p&gt;A screenshot loses that sequence entirely. It can show a useful answer, but it rarely explains how your product helped produce it.&lt;br&gt;
Waiting is part of the product, but it dominates the recording&lt;br&gt;
A real session includes several kinds of delay:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The assistant deciding what to do.&lt;/li&gt;
&lt;li&gt;A tool fetching or processing data.&lt;/li&gt;
&lt;li&gt;Another tool running afterward.&lt;/li&gt;
&lt;li&gt;The assistant composing the final response.
Those pauses might be reasonable while you’re using the product. You asked for something and expect to wait.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A viewer scrolling through a feed hasn’t made that investment. They’re waiting to discover whether the result is interesting.&lt;/p&gt;

&lt;p&gt;You can trim the pauses in a video editor, but cuts can make the conversation jump. Speeding up the whole recording makes cursor movement frantic and text difficult to read.&lt;/p&gt;

&lt;p&gt;The hard part is compressing the wait while preserving a clear sequence.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Re-recording changes the thing you’re recording&lt;/strong&gt;&lt;br&gt;
Fixing a conventional software demo is often straightforward: reset the app and repeat the clicks.&lt;/p&gt;

&lt;p&gt;Repeating an AI conversation can produce a different session.&lt;/p&gt;

&lt;p&gt;The assistant might write a longer introduction, choose a different tool sequence, or format the result differently. A request that worked during rehearsal might hit a timeout during recording.&lt;/p&gt;

&lt;p&gt;Now a small correction—perhaps a typo in the prompt—requires another run with a different answer.&lt;/p&gt;

&lt;p&gt;This makes recording surprisingly expensive. You’re trying to capture a useful interaction while also depending on that interaction to repeat.&lt;br&gt;
Chat interfaces contain a lot you didn’t intend to show&lt;br&gt;
The conversation is only one part of the screen.&lt;/p&gt;

&lt;p&gt;There may also be account details, project names, previous chats, file paths, or notifications. Tool responses can contain information that was useful during development but inappropriate for a public demo.&lt;/p&gt;

&lt;p&gt;Using a demo account and fictional data helps. You still need to inspect the entire frame, including expanded tool cards and anything revealed during scrolling.&lt;/p&gt;

&lt;p&gt;A recording can be technically successful and still require another take because of something in the sidebar.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The result doesn’t always fit on screen&lt;/strong&gt;&lt;br&gt;
Chat responses grow downward. A useful answer may push the original request out of view. An expanded tool call can move the result below the fold.&lt;/p&gt;

&lt;p&gt;That leaves you making presentation decisions while recording:&lt;/p&gt;

&lt;p&gt;When should you scroll? Should the tool details stay open? How long does the viewer need to read the table? Which part deserves a closer look?&lt;/p&gt;

&lt;p&gt;Those choices determine whether someone understands the demo. They’re difficult to make smoothly while also operating the product.&lt;br&gt;
Editing needs to preserve what actually happened&lt;br&gt;
Removing dead time is reasonable. Changing the outcome creates a different problem.&lt;/p&gt;

&lt;p&gt;If you shorten a prompt, it should retain the original intent. If you compress a wait, viewers should understand that the video is edited. A tool result should reflect what the tool actually returned.&lt;/p&gt;

&lt;p&gt;This matters especially when recreating a chat visually. A polished replay can resemble a live recording, so its relationship to the source session needs to be clear.&lt;/p&gt;

&lt;p&gt;The editing process should make the real interaction easier to follow.&lt;br&gt;
Why we built chat-replay&lt;br&gt;
We built chat-replay around that distinction.&lt;/p&gt;

&lt;p&gt;It takes a transcript from a real session and renders an edited replay using HyperFrames. Typing, tool calls, replies, scrolling, captions, and zooms run on a fixed timeline.&lt;/p&gt;

&lt;p&gt;Each beat references its source transcript turns. Before rendering, the skill produces a script explaining what was shortened, cut, or merged for review.&lt;/p&gt;

&lt;p&gt;The default disclosure reads “Recreated from a real session.” Waits can be compressed while retaining the original duration in labels such as “Thought for 9s.”&lt;/p&gt;

&lt;p&gt;That gives us a repeatable way to present an interaction without running it again for every edit.&lt;/p&gt;

&lt;p&gt;The current version has limits: Claude-style and Codex-style light layouts, 16:9 output, image-based widgets, and no built-in narration or music.&lt;/p&gt;

&lt;p&gt;It’s free, open source, and available independently of the rest of promotion-agent:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;npx skills add apsquared/promotion-agent --skill chat-replay&lt;br&gt;
&lt;/code&gt;&lt;br&gt;
You’ll need Node.js, an internet connection, and FFmpeg for the final render.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.apsquared.co/posts/chat-replay-mcp-demo-videos" rel="noopener noreferrer"&gt;See the sample video and full walkthrough on APSquared.&lt;br&gt;
&lt;/a&gt;&lt;br&gt;
If you’ve recorded a demo of a chat-based product, which part took the most work: getting a good session, keeping private information out of frame, or editing the pacing?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>mcp</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Using Vibe Coding + AI Agents to Build a pSEO site</title>
      <dc:creator>AP Squared</dc:creator>
      <pubDate>Sat, 29 Mar 2025 15:22:35 +0000</pubDate>
      <link>https://dev.to/apsquared/using-vibe-coding-ai-agents-to-build-a-pseo-site-40en</link>
      <guid>https://dev.to/apsquared/using-vibe-coding-ai-agents-to-build-a-pseo-site-40en</guid>
      <description>&lt;h2&gt;
  
  
  How I Built Legally Vibing Using Vibe Coding and AI Agents
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;Discover how curiosity about legal THC turned into a fully automated cannabis discovery engine — powered by Cursor, CrewAI, and a lot of good vibes.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhg6llpve18zz0qzzw1e8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhg6llpve18zz0qzzw1e8.png" alt="LegallyVibing.com Screenshot" width="800" height="512"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  🌿 Why I Built Legally Vibing
&lt;/h2&gt;

&lt;p&gt;A while back, I stumbled into the strange and fascinating world of &lt;strong&gt;legal THC products&lt;/strong&gt; — things like hemp-derived Delta-9 seltzers and edibles that are federally compliant under the 2018 Farm Bill.&lt;/p&gt;

&lt;p&gt;They’re totally legal to buy online, but its sometimes hard to understand which products are best.  There was no "Amazon" for THC products.&lt;/p&gt;

&lt;p&gt;Each brand had its own site, product names were confusing, and information was scattered across Reddit threads and obscure blog posts. There was no central, trustworthy hub for this new wave of cannabis products.&lt;/p&gt;

&lt;p&gt;That’s when the idea hit: &lt;strong&gt;what if I built the Leafly of legal THC?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
But focused &lt;em&gt;only&lt;/em&gt; on compliant, online-available products like gummies and seltzers?&lt;/p&gt;

&lt;p&gt;That became &lt;a href="https://www.legallyvibing.com" rel="noopener noreferrer"&gt;&lt;strong&gt;LegallyVibing.com&lt;/strong&gt;&lt;/a&gt;:&lt;br&gt;&lt;br&gt;
&lt;em&gt;Your trusted guide to legal THC products across the web.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fv300i50r39wf30j0px5z.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fv300i50r39wf30j0px5z.png" alt="LegallyVibing.com Screenshot" width="800" height="486"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  ⚒️ Building the Site with Vibe Coding
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is “Vibe Coding”?
&lt;/h3&gt;

&lt;p&gt;Vibe coding is what I call my favorite dev flow:&lt;br&gt;&lt;br&gt;
A blend of AI pair programming, rapid prototyping, and not overthinking anything.&lt;/p&gt;

&lt;p&gt;For this project, I used &lt;a href="https://www.cursor.com" rel="noopener noreferrer"&gt;&lt;strong&gt;Cursor&lt;/strong&gt;&lt;/a&gt; — an AI-powered code editor that makes it faster to develop.&lt;br&gt;&lt;br&gt;
As an experienced developer I was hesitant to give up control of my code but after a few days of 'vibing' it was clear how much more productive I was.&lt;br&gt;
Vibe coding isn't without its headaches and I'll talk more about lessons learned below.&lt;/p&gt;

&lt;h3&gt;
  
  
  Best Practices for Vibe Coding
&lt;/h3&gt;

&lt;p&gt;After weeks of building with Cursor, I've developed some key practices that help me stay productive while "vibing":&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Be Specific in Your Prompts&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Describe exactly what you want, including edge cases&lt;/li&gt;
&lt;li&gt;Include context about your tech stack and dependencies&lt;/li&gt;
&lt;li&gt;Mention performance requirements or constraints upfront&lt;/li&gt;
&lt;li&gt;Example: Instead of "add auth", say "add Firebase email/password auth with error handling"&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Take Small, Testable Steps&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Break features into mini-milestones&lt;/li&gt;
&lt;li&gt;Let Cursor handle one component or function at a time&lt;/li&gt;
&lt;li&gt;Review and understand each suggestion before moving on&lt;/li&gt;
&lt;li&gt;Keep your git commits atomic and descriptive&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Stay in Control of the Code&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Don't blindly accept every suggestion&lt;/li&gt;
&lt;li&gt;If Cursor generates too much at once, start over with a smaller scope&lt;/li&gt;
&lt;li&gt;Run tests frequently to catch issues early&lt;/li&gt;
&lt;li&gt;Keep a clear mental model of your architecture&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Know When to Reset&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If you're going in circles with an AI suggestion, take a break&lt;/li&gt;
&lt;li&gt;Sometimes starting fresh with a new prompt is faster than debugging&lt;/li&gt;
&lt;li&gt;Don't be afraid to throw away generated code that isn't working&lt;/li&gt;
&lt;li&gt;Step back and rethink your approach if you're not making progress&lt;/li&gt;
&lt;li&gt;Consider switching to manual coding for complex logic or edge cases&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  🕵️ Using AI Agents to Curate the Products
&lt;/h2&gt;

&lt;p&gt;One of the most interesting parts of building Legally Vibing was creating an autonomous data pipeline using &lt;a href="https://www.crewai.com" rel="noopener noreferrer"&gt;CrewAI&lt;/a&gt;. I built a system of agents that work together to discover and catalog new THC products:&lt;/p&gt;

&lt;h3&gt;
  
  
  Company Discovery Agent
&lt;/h3&gt;

&lt;p&gt;The first agent acts as a research assistant, combining web search APIs with browser automation to find new THC companies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Uses Websearch tools to find potential vendors&lt;/li&gt;
&lt;li&gt;Leverages Browser Use for deeper investigation of promising leads&lt;/li&gt;
&lt;li&gt;Maintains a scoring system to prioritize legitimate businesses&lt;/li&gt;
&lt;li&gt;Automatically filters out non-compliant or suspicious vendors&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Product Mapping Agent
&lt;/h3&gt;

&lt;p&gt;Once we have a verified company, a specialized agent maps their product catalog:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generates and crawls complete website sitemaps&lt;/li&gt;
&lt;li&gt;Identifies product pages using URL patterns and content analysis&lt;/li&gt;
&lt;li&gt;Creates structured data about product locations&lt;/li&gt;
&lt;li&gt;Flags new products for detailed analysis&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Product Details Agent
&lt;/h3&gt;

&lt;p&gt;A third agent dives deep into each product:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Extracts key details using custom OpenGraph parsers&lt;/li&gt;
&lt;li&gt;Cross-references product claims with lab reports&lt;/li&gt;
&lt;li&gt;Standardizes data format for consistent storage&lt;/li&gt;
&lt;li&gt;Generates SEO-friendly product descriptions&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  💾 Database Integration Agent
&lt;/h3&gt;

&lt;p&gt;Finally, a database agent handles all the CRUD operations:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Validates data against our MongoDB schema&lt;/li&gt;
&lt;li&gt;Updates existing products or creates new entries&lt;/li&gt;
&lt;li&gt;Maintains relationship data between products&lt;/li&gt;
&lt;li&gt;Tracks changes for audit purposes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The agents communicate through a message queue, with each one passing validated data to the next stage. This autonomous pipeline runs daily, keeping our product database fresh and accurate with minimal human oversight.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo7lkhuj2u77n1stfvpc6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo7lkhuj2u77n1stfvpc6.png" alt="LegallyVibing.com Screenshot" width="800" height="531"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  🤯 Key Lessons from AI Automation
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;You &lt;em&gt;can’t&lt;/em&gt; fully trust the first result — each agent needs clear prompts + validation layers.&lt;/li&gt;
&lt;li&gt;Start slow and validate each step before moving forward — rushing leads to messy data.&lt;/li&gt;
&lt;li&gt;Triple-check everything: inputs, outputs, and the steps between.&lt;/li&gt;
&lt;li&gt;Build tools to catch and fix mistakes — they &lt;em&gt;will&lt;/em&gt; happen at scale.  For example we have a simple edit company / product capability to correct issues.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Current Challenges
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Keeping listings clean, legal, and up-to-date&lt;/li&gt;
&lt;li&gt;Boosting SEO in a space that’s still taboo many places&lt;/li&gt;
&lt;li&gt;Need more backlinks!&lt;/li&gt;
&lt;li&gt;Getting exposure in a community that I have little connections with&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Building &lt;a href="https://www.legallyvibing.com" rel="noopener noreferrer"&gt;&lt;strong&gt;Legally Vibing&lt;/strong&gt;&lt;/a&gt; has been part tech sprint, part mission.&lt;/p&gt;

&lt;p&gt;If you’re curious about what’s out there — or building in the legal cannabis space yourself — let’s talk.&lt;br&gt;&lt;br&gt;
The future of cannabis is compliant, data-driven, and built with love + AI.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>seo</category>
    </item>
  </channel>
</rss>
