WEBVTT 00:00:00.000 --> 00:00:02.580 Welcome to the Deep Dive. Today, we're looking 00:00:02.580 --> 00:00:05.040 at what feels like a foundational pivot in how 00:00:05.040 --> 00:00:07.139 software is actually getting built. It really 00:00:07.139 --> 00:00:10.740 is. Using old AI coding tools, you know, like 00:00:10.740 --> 00:00:13.949 standard ChatGPT or Clod. It's kind of like using 00:00:13.949 --> 00:00:15.929 a Ferrari to deliver pizza. Right. I mean, it 00:00:15.929 --> 00:00:18.410 works, sure. Yeah. But you're leaving about 95 00:00:18.410 --> 00:00:21.390 % of what that thing can do just sitting in the 00:00:21.390 --> 00:00:23.629 garage. Yeah. The future is. Yeah. Well, it's 00:00:23.629 --> 00:00:26.089 the agentic workspace. Exactly. So we're moving 00:00:26.089 --> 00:00:29.530 past those single -threaded AI chat assistants, 00:00:29.690 --> 00:00:32.250 the ones that just spit out code snippets, and 00:00:32.250 --> 00:00:33.990 we're stepping into what we're calling the conductor 00:00:33.990 --> 00:00:36.909 era. That's it. Yeah. And our mission today is 00:00:36.909 --> 00:00:39.590 to really unpack Google anti -gravity, which 00:00:39.590 --> 00:00:43.240 is this next -gen workspace. system that makes 00:00:43.240 --> 00:00:46.560 it all click. The RAPS framework. Yeah. Rules, 00:00:46.700 --> 00:00:48.759 armory, parallel agents, and serverless running. 00:00:48.880 --> 00:00:50.560 And the promise here is, you know, building production 00:00:50.560 --> 00:00:52.619 -ready apps in under half an hour. Okay. Let's 00:00:52.619 --> 00:00:54.960 slow down and define that. What is anti -gravity 00:00:54.960 --> 00:00:57.780 officially? So the official line is it's an agentic 00:00:57.780 --> 00:01:00.880 AI -first IDE, an integrated development environment 00:01:00.880 --> 00:01:04.579 powered by models like Gemini 3, Claude, and 00:01:04.579 --> 00:01:07.090 it's designed from the ground up. to build real 00:01:07.090 --> 00:01:11.489 software using specialized agents and deep tool 00:01:11.489 --> 00:01:13.689 integrations. So an easier way to think about 00:01:13.689 --> 00:01:17.469 it. Just imagine VS Code and ChatGPT had a kid. 00:01:17.590 --> 00:01:20.730 Okay. And that kid was raised by a team of specialist 00:01:20.730 --> 00:01:24.750 developers who never sleep, never complain, and 00:01:24.750 --> 00:01:27.629 never ask for an hourly rate. That's anti -gravity. 00:01:27.670 --> 00:01:29.709 And that's the critical distinction, right? Because 00:01:29.709 --> 00:01:32.469 the tools people use now, like Cursor or just 00:01:32.469 --> 00:01:35.730 a chatbot, they give you pieces of code. It's 00:01:35.730 --> 00:01:38.069 a single threaded back and forth conversation. 00:01:38.569 --> 00:01:40.950 The whole workflow changes. Yeah. Anti -gravity 00:01:40.950 --> 00:01:43.670 brings like three huge advantages to the table. 00:01:43.790 --> 00:01:46.349 First is long -term memory. It remembers. It 00:01:46.349 --> 00:01:48.629 remembers. It maintains context across your whole 00:01:48.629 --> 00:01:50.890 project. It knows what you built yesterday, which 00:01:50.890 --> 00:01:53.290 file you're in. It's a massive relief. And the 00:01:53.290 --> 00:01:55.290 second big piece is that you're not just chatting 00:01:55.290 --> 00:01:57.950 with one a**. AI. You're managing a small AI 00:01:57.950 --> 00:02:00.829 development team through these specialized agents. 00:02:01.109 --> 00:02:03.250 Right. And it uses what we're calling structured 00:02:03.250 --> 00:02:06.230 workflows. The system is building actual systems 00:02:06.230 --> 00:02:08.889 from your answers, not just giving you the answers 00:02:08.889 --> 00:02:10.930 themselves. Okay. And the third advantage, you 00:02:10.930 --> 00:02:12.729 said it connects to the real world. Yeah. The 00:02:12.729 --> 00:02:15.909 model context protocol or MCP. This is what lets 00:02:15.909 --> 00:02:18.669 the AI connect directly to databases, to scraping 00:02:18.669 --> 00:02:22.250 tools, to live documentation. It gives the AI 00:02:22.250 --> 00:02:25.500 eyes and hands. So if the core difference is 00:02:25.500 --> 00:02:28.500 managing a dev team, what is the architectural 00:02:28.500 --> 00:02:31.580 blueprint for that management? The RAPS framework. 00:02:31.780 --> 00:02:34.020 That is the blueprint. It defines the rules, 00:02:34.159 --> 00:02:36.719 the tools, the roles, and the deployment for 00:02:36.719 --> 00:02:38.639 orchestrating that team. Okay, so that brings 00:02:38.639 --> 00:02:41.620 us to the methodology itself. RAPS. Let's start 00:02:41.620 --> 00:02:44.259 with the R rules. Right. Think of rules as the 00:02:44.259 --> 00:02:46.840 track conditions for your Formula One car. Okay. 00:02:46.879 --> 00:02:49.139 You can have the fastest car, the best driver, 00:02:49.259 --> 00:02:51.620 your AI. But if it doesn't know the track, it's 00:02:51.620 --> 00:02:53.889 going to give you generic results. Rules set 00:02:53.889 --> 00:02:55.930 the personality and the technical standards for 00:02:55.930 --> 00:02:58.349 the race. So they're basically master instructions 00:02:58.349 --> 00:03:01.210 that ensure consistent code quality. Because 00:03:01.210 --> 00:03:03.689 without them, you get that chaos we've all seen. 00:03:03.870 --> 00:03:06.590 Oh, yeah. Inconsistent naming, three different 00:03:06.590 --> 00:03:10.430 CSS frameworks in one project. Just a mess. And 00:03:10.430 --> 00:03:12.270 you can set these rules at different levels, 00:03:12.430 --> 00:03:14.810 right? Three critical levels. You start with 00:03:14.810 --> 00:03:18.210 global rules. These apply to every single project 00:03:18.210 --> 00:03:20.550 you ever start. So this is like my personal default. 00:03:20.750 --> 00:03:23.419 Exactly. Your persona, senior product engineer 00:03:23.419 --> 00:03:26.500 at Stripe, and your go -to tech stack like Next 00:03:26.500 --> 00:03:29.199 .js 14 and Tailwind. Then you drill down into 00:03:29.199 --> 00:03:31.620 workspace rules. Yeah, these are project specific. 00:03:31.860 --> 00:03:34.699 For an app, we might build, say, subreddit pulse. 00:03:35.060 --> 00:03:38.060 We could mandate a specific color palette, a 00:03:38.060 --> 00:03:40.860 certain design aesthetic, maybe glass morphism. 00:03:41.080 --> 00:03:44.479 And finally, task rules. Super simple. One -off 00:03:44.479 --> 00:03:47.520 commands like build a login component, but use 00:03:47.520 --> 00:03:50.370 React hooks only. That's a task rule. You know, 00:03:50.389 --> 00:03:52.629 I still wrestle with prompt drift myself. Oh, 00:03:52.650 --> 00:03:54.349 me too. You start a conversation, it's going 00:03:54.349 --> 00:03:56.289 great, and then three prompts later, it's completely 00:03:56.289 --> 00:03:58.129 forgotten the style guide you gave it. That is 00:03:58.129 --> 00:04:01.370 the exact pain point this solves. Right. Rules 00:04:01.370 --> 00:04:03.629 let you hard code a definition of done. A definition 00:04:03.629 --> 00:04:06.430 of done. Yeah. So you can require the AI to, 00:04:06.469 --> 00:04:09.550 say, verify the UI, check for edge cases, and 00:04:09.550 --> 00:04:11.590 update the docs before it can mark a task as 00:04:11.590 --> 00:04:13.469 incomplete. It prevents it from giving you code 00:04:13.469 --> 00:04:15.860 that just breaks on compile. That's a huge shift. 00:04:15.960 --> 00:04:17.660 You're defining the goalposts, not just kicking 00:04:17.660 --> 00:04:20.259 the ball. Right. And if rules were about consistency, 00:04:20.639 --> 00:04:23.680 what external context do they need so they don't 00:04:23.680 --> 00:04:25.600 build something that's already outdated? They 00:04:25.600 --> 00:04:28.300 need eyes and ears. They need the armory. Exactly. 00:04:28.939 --> 00:04:31.839 So let's talk about A for Armory. This is where 00:04:31.839 --> 00:04:34.259 that MCP, the model context protocol, really 00:04:34.259 --> 00:04:36.860 comes into play. It solves that disconnection 00:04:36.860 --> 00:04:39.579 from reality that plagues so many AI models. 00:04:39.800 --> 00:04:42.399 For sure. And the specific tools are what's so 00:04:42.399 --> 00:04:44.439 fascinating. Let's take five essentials. First, 00:04:44.579 --> 00:04:46.699 context seven. Why is that one so important? 00:04:47.000 --> 00:04:51.620 Because AI training data is always stale. Always. 00:04:51.959 --> 00:04:54.959 Context 7 gives the AI live access to the latest 00:04:54.959 --> 00:04:58.420 API documentation. No more deprecated code errors. 00:04:58.639 --> 00:05:01.100 Okay, that's huge. What's next? Firecrawl. For 00:05:01.100 --> 00:05:03.379 an app that needs fresh data, like our subreddit 00:05:03.379 --> 00:05:06.000 Pulse example, Firecrawl can go scrape websites 00:05:06.000 --> 00:05:08.540 and just hand back clean, structured data. So 00:05:08.540 --> 00:05:11.019 it turns the web into a database for the app. 00:05:11.220 --> 00:05:13.579 Pretty much. And speaking of databases, you integrate 00:05:13.579 --> 00:05:17.019 Supabase. This lets the AI team manage schemas 00:05:17.019 --> 00:05:19.259 and query data with just plain English. You don't 00:05:19.259 --> 00:05:21.459 write any SQL. The builder agent just handles 00:05:21.459 --> 00:05:24.339 it. Then for Memre, you bring in Pinecone. This 00:05:24.339 --> 00:05:27.000 is for RAG, right? Retrieval Augmented Generation. 00:05:27.399 --> 00:05:30.220 Exactly. RAG is just a fancy way of saying the 00:05:30.220 --> 00:05:32.560 AI can look things up in an external knowledge 00:05:32.560 --> 00:05:35.680 base. Pinecone stores your old project data, 00:05:35.920 --> 00:05:40.160 docs, design patterns. It gives the AI perfect 00:05:40.160 --> 00:05:42.459 long -term memory. And the last one. Notion. 00:05:42.779 --> 00:05:45.779 Just for organization. The AI can create project 00:05:45.779 --> 00:05:47.980 pages and docs automatically to keep the human 00:05:47.980 --> 00:05:50.800 team in the loop. It sounds complex to set up. 00:05:50.879 --> 00:05:53.120 It's surprisingly not. It's just a JSON config 00:05:53.120 --> 00:05:56.120 file where you paste your API keys. But here's 00:05:56.120 --> 00:05:59.000 the tip. Start small. Okay. Pick five to ten 00:05:59.000 --> 00:06:01.939 essential tools. Don't go crazy and add 50, because 00:06:01.939 --> 00:06:03.860 too many tools will actually slow things down 00:06:03.860 --> 00:06:06.699 and shrink the AI's useful context. So how do 00:06:06.699 --> 00:06:09.339 specialized tools like Context 7 address that 00:06:09.339 --> 00:06:11.480 fundamental issue of AI training data getting 00:06:11.480 --> 00:06:14.459 stale so fast? Live documentation access prevents 00:06:14.459 --> 00:06:17.779 outdated API use and ensures the AI uses the 00:06:17.779 --> 00:06:19.639 newest technical patterns. Got it. Okay, now 00:06:19.639 --> 00:06:21.540 we're at the heart of it. P for parallel agents. 00:06:21.680 --> 00:06:23.839 This is the conductor era in full effect. We 00:06:23.839 --> 00:06:26.439 said telling one generalist AI to do everything 00:06:26.439 --> 00:06:29.889 just gives you mediocre everything. So anti -gravity 00:06:29.889 --> 00:06:32.110 deploys specialized agents that work at the same 00:06:32.110 --> 00:06:34.769 time. And this is where you, the human, stop 00:06:34.769 --> 00:06:37.149 being the coder and become the architect. You 00:06:37.149 --> 00:06:39.350 set the vision and the agents handle the details. 00:06:39.550 --> 00:06:42.129 And we can define, say, four main archetypes. 00:06:42.230 --> 00:06:45.750 First up is the design lead. Yep. Its mission 00:06:45.750 --> 00:06:49.189 is purely visual. UI, UX, making things look 00:06:49.189 --> 00:06:51.509 amazing. Yeah. We tell it to use modern principles 00:06:51.509 --> 00:06:54.990 like glass morphism. And its lane is clear. It 00:06:54.990 --> 00:06:57.209 only owns the front -end folder. It can't touch 00:06:57.209 --> 00:06:59.009 anything else. Can't touch the back -end. That's 00:06:59.009 --> 00:07:01.290 for the builder. The builder's job is functionality, 00:07:01.649 --> 00:07:04.370 logic, API routes. It owns the back -end and 00:07:04.370 --> 00:07:07.209 API folders. Third is the nerd. I like that name. 00:07:07.389 --> 00:07:10.250 The nerd is your QA lead. Its job is to break 00:07:10.250 --> 00:07:12.769 things. It writes unit tests, audits the other 00:07:12.769 --> 00:07:14.970 agents' work, and lives inside the tests folder. 00:07:15.290 --> 00:07:18.009 It's your safety net. And the last one, the researcher. 00:07:18.329 --> 00:07:21.029 The researcher is read -only. It gathers intel. 00:07:21.269 --> 00:07:23.250 It might find the best libraries to use or the 00:07:23.250 --> 00:07:25.310 most efficient data structures, and it writes 00:07:25.310 --> 00:07:27.649 its findings into a planning document, like plan 00:07:27.649 --> 00:07:30.250 .md. So you, as the conductor, might tell the 00:07:30.250 --> 00:07:33.269 design lead, make this dashboard look like Linear's 00:07:33.269 --> 00:07:36.350 UI, while you're also telling the builder, implement 00:07:36.350 --> 00:07:39.189 the API for Firecrawl. Exactly. You orchestrate. 00:07:39.329 --> 00:07:41.069 Okay, but if the agents are working in parallel, 00:07:41.350 --> 00:07:44.149 what guarantees their changes won't conflict 00:07:44.149 --> 00:07:46.939 or just overwrite each other's work? Assigning 00:07:46.939 --> 00:07:50.220 those clear domain ownerships, those lanes, for 00:07:50.220 --> 00:07:52.540 each agent is what prevents the conflicting code 00:07:52.540 --> 00:07:56.060 changes. The system literally stops the builder 00:07:56.060 --> 00:07:58.100 from messing with the front -end folder. And 00:07:58.100 --> 00:08:00.240 that clarity is the whole game. It did everything. 00:08:00.579 --> 00:08:04.040 Which brings us to the final letter, S, for serverless 00:08:04.040 --> 00:08:06.540 running. The team built the app, but how does 00:08:06.540 --> 00:08:09.720 it run when your laptop is closed? S is for deployment. 00:08:09.980 --> 00:08:12.060 You deploy it straight to serverless platforms, 00:08:12.300 --> 00:08:16.319 modal. Vercel, AWS Lambda, whatever, using built 00:08:16.319 --> 00:08:18.579 -in tools. And the process is simple. It is. 00:08:18.699 --> 00:08:21.939 The agents naturally build modular code. So you 00:08:21.939 --> 00:08:23.879 just pick a platform. Modal is great for Python 00:08:23.879 --> 00:08:26.660 jobs, Vercel for React frontends. And then you 00:08:26.660 --> 00:08:28.759 deploy it with a natural language prompt. Something 00:08:28.759 --> 00:08:31.939 like, deploy this app to Modal. Run it every 00:08:31.939 --> 00:08:35.419 hour. Store results in Subabase. And anti -gravity 00:08:35.419 --> 00:08:37.019 just handles it. The packaging, the scheduling, 00:08:37.139 --> 00:08:38.940 all of it. It's really a set it and forget it 00:08:38.940 --> 00:08:40.940 system. Totally. Okay, let's walk through that 00:08:40.940 --> 00:08:42.840 subreddit pulse example again, step by step, 00:08:42.840 --> 00:08:46.440 using RAPS. Go. A dashboard scraping two subreddits, 00:08:46.440 --> 00:08:49.580 making LinkedIn content, updating hourly. So 00:08:49.580 --> 00:08:53.440 first we set our global rules. Next .js, TypeScript, 00:08:53.720 --> 00:08:56.460 Senior Engineer Persona. Then we create the initial 00:08:56.460 --> 00:09:00.110 design doc. And here's the pro tip. Feed the 00:09:00.110 --> 00:09:04.370 AI -specific design screenshots. Yes. Don't just 00:09:04.370 --> 00:09:06.610 describe it. Show it examples from Linear or 00:09:06.610 --> 00:09:09.129 Vercel. It gets the look and feel instantly way 00:09:09.129 --> 00:09:11.210 better than text alone. Then the agents get to 00:09:11.210 --> 00:09:13.269 work. Yep. The app design lead adds those cool 00:09:13.269 --> 00:09:15.690 glassmorphism effects. The app builder hooks 00:09:15.690 --> 00:09:18.110 up the firecrawl logic. And the app nerd runs 00:09:18.110 --> 00:09:20.190 audits to make sure the hourly job won't crash. 00:09:20.370 --> 00:09:22.850 And the final deployment step. We use the Supabase 00:09:22.850 --> 00:09:24.769 integration to create the database tables with 00:09:24.769 --> 00:09:27.309 a prompt. And then the final command. Deploy 00:09:27.309 --> 00:09:30.450 the scraper to modal. Run hourly. Save to Supabase. 00:09:30.590 --> 00:09:35.289 Done. Whoa. Just imagine scaling that. A system 00:09:35.289 --> 00:09:38.490 that tracks a thousand sources with hourly updates 00:09:38.490 --> 00:09:41.690 all maintained by an AI team. Superhuman speed. 00:09:41.909 --> 00:09:44.669 Yeah. And zero human burnout. That's the moment 00:09:44.669 --> 00:09:47.070 of wonder right there. It is. So anti -gravity 00:09:47.070 --> 00:09:49.330 shines where speed and structure matter. Rapid 00:09:49.330 --> 00:09:52.370 prototypes, MVPs, internal dashboards, automation 00:09:52.370 --> 00:09:54.850 jobs. It's a cheat code for common development 00:09:54.850 --> 00:09:57.149 patterns. But we have to talk about the boundaries. 00:09:57.470 --> 00:09:59.830 When should you absolutely not use this? Absolutely. 00:10:00.029 --> 00:10:02.309 Avoid it for production -critical systems. Anything 00:10:02.309 --> 00:10:04.429 in banking, healthcare, core infrastructure. 00:10:04.769 --> 00:10:07.149 Why is that? The higher the risk, the more you 00:10:07.149 --> 00:10:09.470 need manual control. Same goes for really niche 00:10:09.470 --> 00:10:11.909 domains like embedded systems. Or if you're working 00:10:11.909 --> 00:10:14.470 with a super custom, outdated tech stack, the 00:10:14.470 --> 00:10:17.870 AI is best at modern, standard workflows. So 00:10:17.870 --> 00:10:19.870 for a first -time user building that subreddit 00:10:19.870 --> 00:10:21.570 pulse app, what's the most important takeaway 00:10:21.570 --> 00:10:24.370 from that example? Feeding the AI design screenshots 00:10:24.370 --> 00:10:27.409 or rules guides the results far better than relying 00:10:27.409 --> 00:10:30.610 solely on text prompts. So what does this all 00:10:30.610 --> 00:10:33.429 mean for the future of development? It feels 00:10:33.429 --> 00:10:36.590 like the era of the lone coder writing every 00:10:36.590 --> 00:10:41.330 single line of CSS is, well, it's ending. It 00:10:41.330 --> 00:10:43.629 is. We're seeing reports that developers using 00:10:43.629 --> 00:10:46.730 these agentic tools can work up to 55 % faster. 00:10:47.389 --> 00:10:49.769 It's a massive leap. The role itself is shifting 00:10:49.769 --> 00:10:52.490 then. Completely. You go from being the implementer, 00:10:52.509 --> 00:10:54.470 the person worried about every semicolon, to 00:10:54.470 --> 00:10:56.909 being the architect, the strategist. You define 00:10:56.909 --> 00:11:00.090 the vision. The RAPS agents implement, debug, 00:11:00.409 --> 00:11:02.720 and deploy. The advantage isn't just writing 00:11:02.720 --> 00:11:05.340 code faster. It's designing a system that builds 00:11:05.340 --> 00:11:07.679 itself. That's the real unlock. The tools are 00:11:07.679 --> 00:11:10.080 getting there so fast. So here's a final challenge 00:11:10.080 --> 00:11:12.500 for you, the listener. Pick one small project 00:11:12.500 --> 00:11:14.399 you've been putting off. Spend a weekend building 00:11:14.399 --> 00:11:17.240 it with an agentic IDE and this RAPS framework. 00:11:17.559 --> 00:11:19.259 By Monday morning, you'll probably have a working 00:11:19.259 --> 00:11:21.399 prototype. And it will likely change how you 00:11:21.399 --> 00:11:23.379 think about building software forever. Until 00:11:23.379 --> 00:11:23.759 that's time.