WEBVTT 00:00:00.000 --> 00:00:02.279 You build a dashboard in the morning. By lunch, 00:00:02.359 --> 00:00:05.940 it is already lying to you. Static data is dead 00:00:05.940 --> 00:00:09.220 data. Geet. Welcome to this deep dive. Thanks 00:00:09.220 --> 00:00:11.000 for having me. I'm excited to get into this. 00:00:11.160 --> 00:00:14.480 Our mission today is unpacking live Claude artifacts. 00:00:14.779 --> 00:00:17.800 We are going to tear down the old workflow completely. 00:00:17.899 --> 00:00:20.500 We really have to. You waste precious tokens 00:00:20.500 --> 00:00:23.579 waiting for static page rebuilds. Right. Today 00:00:23.579 --> 00:00:25.920 we figure out how to wire up live data pipes. 00:00:26.320 --> 00:00:28.359 We connect these directly to your local machine. 00:00:28.570 --> 00:00:31.329 We cover everything from basic pumps to scaling 00:00:31.329 --> 00:00:34.509 thousands of apps. It is a massive shift. We 00:00:34.509 --> 00:00:37.710 are moving from static web pages to living applications. 00:00:37.990 --> 00:00:39.990 To understand how to build this, we first need 00:00:39.990 --> 00:00:43.490 to understand that shift to sex silence. That 00:00:43.490 --> 00:00:46.130 fundamental shift completely alters our daily 00:00:46.130 --> 00:00:48.109 relationship with computing. Think about the 00:00:48.109 --> 00:00:50.070 legacy way of doing heavy knowledge work. You 00:00:50.070 --> 00:00:52.609 mean constantly resetting. Exactly. Every time 00:00:52.609 --> 00:00:54.990 you want fresh data, you must reset completely. 00:00:55.130 --> 00:00:57.270 You go back to the underlying chat interface. 00:00:57.570 --> 00:00:59.950 You write a brand new, highly detailed prompt. 00:00:59.969 --> 00:01:01.990 And then you sit there. You sit and watch it 00:01:01.990 --> 00:01:04.409 rebuild everything from scratch. That constant 00:01:04.409 --> 00:01:07.349 repetition fractures your deep focused work state 00:01:07.349 --> 00:01:10.650 entirely. The cognitive load of context switching 00:01:10.650 --> 00:01:13.629 destroys your momentum. Yeah, you lose your underlying 00:01:13.629 --> 00:01:15.989 train of thought almost immediately. It creates 00:01:15.989 --> 00:01:18.069 immense psychological friction for the user. 00:01:18.370 --> 00:01:21.269 Live cloud artifacts fix this frustrating problem 00:01:21.269 --> 00:01:24.109 at the absolute root. You do not get a frozen 00:01:24.109 --> 00:01:27.390 dead HTML file anymore. No, you get a small, 00:01:27.629 --> 00:01:29.969 highly persistent app on your personal machine. 00:01:30.409 --> 00:01:32.909 It constantly pulls fresh data from your connected 00:01:32.909 --> 00:01:35.349 tools. We are talking about your actual live 00:01:35.349 --> 00:01:38.000 Gmail and Google Calendar. You open the interface, 00:01:38.379 --> 00:01:40.540 and the numbers are currently accurate. You avoid 00:01:40.540 --> 00:01:42.879 that frustrating rebuild waiting period entirely. 00:01:43.239 --> 00:01:45.599 A static dashboard is like a painted picture 00:01:45.599 --> 00:01:48.579 of a river. A live artifact is a water wheel 00:01:48.579 --> 00:01:50.620 actually spinning in the current. I love that. 00:01:50.760 --> 00:01:52.579 You capture the kinetic energy perfectly with 00:01:52.579 --> 00:01:54.459 that thought. If you use a Claude Paid plan, 00:01:54.579 --> 00:01:57.040 you need to pay attention. Right. Pro, Max, Team, 00:01:57.180 --> 00:01:59.840 or Enterprise. Exactly. They all feature this 00:01:59.840 --> 00:02:02.620 amazing capability right now. Most people simply 00:02:02.620 --> 00:02:05.950 do not know this technology exists yet. The AI 00:02:05.950 --> 00:02:08.789 model only has to think deeply one initial time. 00:02:09.110 --> 00:02:11.610 And after that initial thought, the dashboard 00:02:11.610 --> 00:02:14.530 fetches its data completely independently. Oh 00:02:14.530 --> 00:02:16.530 wait, does it really fetch this data without 00:02:16.530 --> 00:02:19.069 pausing to ask permission? Yes, unlike a normal 00:02:19.069 --> 00:02:21.550 chat, it executes silently the moment you open 00:02:21.550 --> 00:02:23.629 it. So it ones completely automatically upon 00:02:23.629 --> 00:02:27.099 opening? It does. But we must move from what 00:02:27.099 --> 00:02:30.439 it is to where it actually lives. You absolutely 00:02:30.439 --> 00:02:33.099 cannot build this system in a standard web browser. 00:02:33.340 --> 00:02:36.099 That is a crucial point. It really is. The live 00:02:36.099 --> 00:02:38.500 features only exist in the desktop application 00:02:38.500 --> 00:02:41.789 environment. This represents a massive philosophical 00:02:41.789 --> 00:02:44.310 shift in how language models operate. We are 00:02:44.310 --> 00:02:46.909 moving from stateless internet chat to local 00:02:46.909 --> 00:02:49.110 state persistence. Right. The AI is actually 00:02:49.110 --> 00:02:51.090 living on your physical hardware now. If this 00:02:51.090 --> 00:02:53.509 thing silently pulls my private company emails 00:02:53.509 --> 00:02:56.189 all day, it obviously cannot live in a standard 00:02:56.189 --> 00:02:59.270 internet browser window. Exactly. Every random 00:02:59.270 --> 00:03:02.110 browser extension could potentially access that 00:03:02.110 --> 00:03:05.030 sensitive data. You hit on the exact reason for 00:03:05.030 --> 00:03:08.159 the secure local architecture. You need the Claw 00:03:08.159 --> 00:03:10.360 desktop application installed in your personal 00:03:10.360 --> 00:03:12.780 computer. It works securely on Mac, Windows, 00:03:13.080 --> 00:03:16.060 or modern Linux systems. Yeah. Once the desktop 00:03:16.060 --> 00:03:18.699 application is open, look at the left sidebar. 00:03:18.900 --> 00:03:21.460 You'll see a small checklist icon right over 00:03:21.460 --> 00:03:23.879 there. That is the dedicated co -work button 00:03:23.879 --> 00:03:26.680 you absolutely must click today. You must click 00:03:26.680 --> 00:03:29.340 it to enter the new live computing environment. 00:03:29.639 --> 00:03:32.319 The entire visual layout shifts dramatically 00:03:32.319 --> 00:03:34.180 when you click that button. If you skip this 00:03:34.180 --> 00:03:36.710 critical step, you stay in normal chat. Right, 00:03:36.810 --> 00:03:39.590 you will not see any of these powerful live features 00:03:39.590 --> 00:03:42.250 available. After clicking Cowork, you must pick 00:03:42.250 --> 00:03:45.449 a permanent working folder. Cowork needs a permanent 00:03:45.449 --> 00:03:48.789 secure home on your physical machine, but I have 00:03:48.789 --> 00:03:51.189 to push back on this specific folder requirement. 00:03:51.830 --> 00:03:54.289 Creating a dedicated folder feels pretty trivial 00:03:54.289 --> 00:03:57.530 at first glance today. Why is it such a massive 00:03:57.530 --> 00:04:00.289 structural deal for the AI? Well, it acts like 00:04:00.289 --> 00:04:02.250 pouring a concrete foundation for your house. 00:04:02.599 --> 00:04:05.580 If you get it wrong, the entire digital house 00:04:05.580 --> 00:04:07.639 slowly sinks. That makes sense. You really had 00:04:07.639 --> 00:04:10.080 to pick one permanent folder and stick with it. 00:04:10.240 --> 00:04:12.599 Switching active folders later causes some truly 00:04:12.599 --> 00:04:15.180 massive software connection headaches. Especially 00:04:15.180 --> 00:04:17.680 when you have 10 different operational dashboards 00:04:17.680 --> 00:04:20.500 currently running. You want all your complex 00:04:20.500 --> 00:04:24.019 project files in one highly secure place. Naming 00:04:24.019 --> 00:04:26.600 it something specific like Daily Work OS makes 00:04:26.600 --> 00:04:30.389 perfect sense. All your live artifacts will live 00:04:30.389 --> 00:04:33.189 inside this exact folder securely. Why does it 00:04:33.189 --> 00:04:35.290 strictly require the desktop app instead of the 00:04:35.290 --> 00:04:38.670 browser? Browsers sandbox your data, right? Whereas 00:04:38.670 --> 00:04:41.250 the desktop app allows secure access to local 00:04:41.250 --> 00:04:44.029 files. Browser environments lack the necessary 00:04:44.029 --> 00:04:47.250 local file access. Beat. We have a solid concrete 00:04:47.250 --> 00:04:49.529 data foundation poured and completely ready. 00:04:50.069 --> 00:04:52.230 But a modern digital house still needs good plumbing 00:04:52.230 --> 00:04:54.790 to function. We need to actively connect the 00:04:54.790 --> 00:04:57.500 daily data to our foundation. Without Live Connectors, 00:04:57.579 --> 00:04:59.680 your artifact is just a pretty digital shell. 00:04:59.800 --> 00:05:02.139 Yeah, it pulls valuable information from absolutely 00:05:02.139 --> 00:05:04.759 nowhere right now. With Active Connectors, it 00:05:04.759 --> 00:05:07.000 becomes a powerful, living, working tool. It 00:05:07.000 --> 00:05:09.420 knows exactly what is inside your personal inbox 00:05:09.420 --> 00:05:11.899 right now. It can view your daily calendar and 00:05:11.899 --> 00:05:14.060 read your local files. To start this process, 00:05:14.220 --> 00:05:17.540 you navigate to Customize in the sidebar. Then 00:05:17.540 --> 00:05:20.079 you click on Connectors and carefully select 00:05:20.079 --> 00:05:22.720 Browse Connectors. You will see the native approved 00:05:22.720 --> 00:05:25.300 application list right there immediately. This 00:05:25.300 --> 00:05:28.040 list currently includes Gmail, Google Drive, 00:05:28.420 --> 00:05:30.839 and the Linear app. A critical permissions window 00:05:30.839 --> 00:05:33.639 pops up when you select an application. Read 00:05:33.639 --> 00:05:36.079 this specific window very carefully before you 00:05:36.079 --> 00:05:39.000 click confirm. People often go way too fast during 00:05:39.000 --> 00:05:42.319 this highly critical step. They really do. Claude 00:05:42.319 --> 00:05:45.199 divides permissions into two very distinct operational 00:05:45.199 --> 00:05:48.300 groups. You have read -only tools and write -delete 00:05:48.300 --> 00:05:50.180 tools currently available. This feels like a 00:05:50.180 --> 00:05:53.160 massive psychological trust hurdle to cross today. 00:05:53.699 --> 00:05:56.040 Granting always allow permissions to my private 00:05:56.040 --> 00:05:59.319 company email inbox daily. It is intense. I am 00:05:59.319 --> 00:06:01.920 essentially handing a black box AI the permanent 00:06:01.920 --> 00:06:04.079 house keys. It sounds totally terrifying when 00:06:04.079 --> 00:06:06.259 you frame it exactly that way, but that is exactly 00:06:06.259 --> 00:06:09.339 why the secure sandbox desktop environment matters. 00:06:09.459 --> 00:06:12.449 If you only want to read emails, Read -only access 00:06:12.449 --> 00:06:15.029 is enough. Right. If you want to create draft 00:06:15.029 --> 00:06:17.750 replies, you need full write access. You must 00:06:17.750 --> 00:06:20.649 set system permissions to Always Allow for true 00:06:20.649 --> 00:06:24.089 automation. Granting Always Allow is like giving 00:06:24.089 --> 00:06:27.209 permanent keys to an assistant. You start with 00:06:27.209 --> 00:06:30.029 read -only access to be completely safe at first. 00:06:30.389 --> 00:06:32.310 That is like letting them look quietly through 00:06:32.310 --> 00:06:35.269 the front window. Exactly. Later, you trust them 00:06:35.269 --> 00:06:37.769 to rearrange the physical furniture inside safely. 00:06:37.980 --> 00:06:39.839 But you have to grant that permission to make 00:06:39.839 --> 00:06:42.779 it work. Right. And selecting needs approval 00:06:42.779 --> 00:06:46.319 ruins the intended automation completely. Always 00:06:46.319 --> 00:06:48.339 test the specific data connection first before 00:06:48.339 --> 00:06:50.819 you start building. Go to a normal desktop chat 00:06:50.819 --> 00:06:53.980 window and run a test. Ask the AI language model 00:06:53.980 --> 00:06:57.139 to pull your last five emails. If real email 00:06:57.139 --> 00:06:59.680 subject lines come back, you are completely ready. 00:06:59.899 --> 00:07:02.399 If you see a system error, check the specific 00:07:02.399 --> 00:07:05.319 connector network status. Fix any expired access 00:07:05.319 --> 00:07:07.480 tokens or missing permission scopes immediately 00:07:07.480 --> 00:07:09.750 today. Running a quick data test takes about 00:07:09.750 --> 00:07:12.170 30 seconds total time. It saves you from dressing 00:07:12.170 --> 00:07:14.990 up a completely broken visual dashboard. Definitely. 00:07:15.189 --> 00:07:17.689 What exactly happens if someone safely clicks 00:07:17.689 --> 00:07:20.490 needs approval? The dashboard basically freezes 00:07:20.490 --> 00:07:22.430 and waits for you to manually click and approve 00:07:22.430 --> 00:07:24.970 the data pull every single time. The dashboard 00:07:24.970 --> 00:07:27.430 freezes until you manually click to approve. 00:07:28.350 --> 00:07:30.829 Beat. The live data pipes are finally flowing 00:07:30.829 --> 00:07:33.490 nicely for us today, but the flowing digital 00:07:33.490 --> 00:07:36.439 water still needs a clear, defined shape. We 00:07:36.439 --> 00:07:38.819 have to instruct the underlying AI language model 00:07:38.819 --> 00:07:41.680 properly now. The entire visual dashboard is 00:07:41.680 --> 00:07:44.300 only as strong as your initial prompt. Vague 00:07:44.300 --> 00:07:47.339 user prompts always result in generic, completely 00:07:47.339 --> 00:07:50.920 boring software tools. The AI simply fills the 00:07:50.920 --> 00:07:54.019 conceptual gaps with basic, boring defaults. 00:07:54.079 --> 00:07:56.660 And those assumed defaults rarely match what 00:07:56.660 --> 00:07:59.819 you actually want it built. Never. Every highly 00:07:59.819 --> 00:08:02.860 strong prompt requires four absolutely necessary 00:08:02.860 --> 00:08:04.680 structural parts today. Walk us through them. 00:08:04.920 --> 00:08:06.939 First, specify what specific kind of dashboard 00:08:06.939 --> 00:08:09.199 you want built initially. Second, list exactly 00:08:09.199 --> 00:08:11.220 which connected data sources to pull from daily. 00:08:11.399 --> 00:08:13.660 Third, describe the visual layout sections or 00:08:13.660 --> 00:08:16.160 specific interface panels desired. And fourth, 00:08:16.399 --> 00:08:19.120 tell the actual highly specific real -world use 00:08:19.120 --> 00:08:22.050 case. I firmly think the use case matters much 00:08:22.050 --> 00:08:24.550 more than people realize. Explaining the daily 00:08:24.550 --> 00:08:27.329 use case completely changes the 8i layout choices. 00:08:27.810 --> 00:08:29.670 A morning dashboard for planning your upcoming 00:08:29.670 --> 00:08:32.730 week looks very specific. It looks completely 00:08:32.730 --> 00:08:34.809 different from one designed for putting out fires. 00:08:35.009 --> 00:08:37.250 They might both pull daily data from the exact 00:08:37.250 --> 00:08:40.470 same sources, but the visual information hierarchy 00:08:40.470 --> 00:08:43.309 changes entirely based on your context. Leaving 00:08:43.309 --> 00:08:46.190 out the specific use case is a massive structural 00:08:46.190 --> 00:08:49.470 mistake. It is like hiring a master chef without 00:08:49.470 --> 00:08:52.529 naming the meal. They will guess blindly and 00:08:52.529 --> 00:08:55.669 you might get cold soup for breakfast. I still 00:08:55.669 --> 00:08:58.909 wrestle with prompt drift myself to sex silence. 00:08:59.529 --> 00:09:01.710 We all struggle with getting the initial text 00:09:01.710 --> 00:09:04.769 prompt perfectly right. Let us look at a practical 00:09:04.769 --> 00:09:07.429 starter prompt example together now. Build me 00:09:07.429 --> 00:09:10.070 a daily morning dashboard pulling Gmail and Google 00:09:10.070 --> 00:09:12.889 Calendar. Show critical emails needing replies 00:09:12.889 --> 00:09:15.509 today alongside upcoming daily scheduled meetings. 00:09:15.710 --> 00:09:18.590 Add a short editable list of three priority tasks 00:09:18.590 --> 00:09:20.809 to tackle. You also state clearly that you open 00:09:20.809 --> 00:09:23.409 this every single morning. Every single visual 00:09:23.409 --> 00:09:25.990 dashboard element is clearly and explicitly named. 00:09:26.309 --> 00:09:28.490 The AI language model knows exactly what to build 00:09:28.490 --> 00:09:30.710 and why. You can also easily build an amazing 00:09:30.710 --> 00:09:33.710 inbox email triage dashboard. Sort your messy 00:09:33.710 --> 00:09:36.929 daily messages into four very distinct visual 00:09:36.929 --> 00:09:39.409 buckets. Needs reply today, needs reply this 00:09:39.409 --> 00:09:42.429 week, incoming newsletters, and spam. For the 00:09:42.429 --> 00:09:45.230 first two priority buckets, Ask for draft AI 00:09:45.230 --> 00:09:47.970 replies. It writes a short two -line draft email 00:09:47.970 --> 00:09:50.309 reply you can edit. That absolutely protects 00:09:50.309 --> 00:09:52.769 your fragile daily attention from endless background 00:09:52.769 --> 00:09:55.549 noise. Read your initial written prompts out 00:09:55.549 --> 00:09:58.370 loud to catch any vagueness. Small language edits 00:09:58.370 --> 00:10:01.110 at this early foundational stage cost you nothing. 00:10:01.649 --> 00:10:04.830 Rebuilds later on will cost you actual real system 00:10:04.830 --> 00:10:07.940 token usage. How much time do those AI draft 00:10:07.940 --> 00:10:10.740 replies actually save in a real inbox triage? 00:10:10.980 --> 00:10:13.240 Easily 15 to 20 minutes on heavy outreach days, 00:10:13.519 --> 00:10:15.179 plus it protects your attention from background 00:10:15.179 --> 00:10:17.779 noise. About 15 to 20 minutes on heavy outreach 00:10:17.779 --> 00:10:21.320 days. Mm. Mm. Mid -roll sponsor, Read Instruction. 00:10:23.299 --> 00:10:25.539 Welcome back to our deep dive into live clot 00:10:25.539 --> 00:10:27.899 artifacts today. What if you need fresh data 00:10:27.899 --> 00:10:30.240 from a completely outside source? a data source 00:10:30.240 --> 00:10:32.399 not natively connected to the main internal lines. 00:10:32.600 --> 00:10:35.399 That is exactly where the incredible MCP framework 00:10:35.399 --> 00:10:38.100 comes into play. MCP is a universal plug letting 00:10:38.100 --> 00:10:41.440 AI talk to outside apps. It functions exactly 00:10:41.440 --> 00:10:44.360 like a universal power adapter for external data. 00:10:44.649 --> 00:10:47.450 That is a highly perfect way to conceptualize 00:10:47.450 --> 00:10:50.710 the integration technology. Zapier MCP is the 00:10:50.710 --> 00:10:53.549 absolute easiest integration path for most users. 00:10:53.950 --> 00:10:56.929 Zapier MCP instantly unlocks direct access to 00:10:56.929 --> 00:11:00.809 over 9 ,000 apps. It seamlessly connects external 00:11:00.809 --> 00:11:03.870 things like your LinkedIn, Airtable or Calendly. 00:11:03.980 --> 00:11:06.059 The technical setup process is actually quite 00:11:06.059 --> 00:11:08.559 simple to follow manually. You choose a Zapier 00:11:08.559 --> 00:11:10.580 server and strictly set the client to cowork. 00:11:10.840 --> 00:11:13.440 Then you carefully customize the specific external 00:11:13.440 --> 00:11:16.480 data tools you actually need. You firmly decide 00:11:16.480 --> 00:11:19.379 if Claude can just read data or create it. Then 00:11:19.379 --> 00:11:22.320 you select Add to Claude and verify the final 00:11:22.320 --> 00:11:25.600 software connection. Let us examine a wild, highly 00:11:25.600 --> 00:11:28.100 concrete scenario to understand this fully. You 00:11:28.100 --> 00:11:30.580 have a massive business partnership call scheduled 00:11:30.580 --> 00:11:33.539 for this afternoon. Imagine a custom artifact 00:11:33.539 --> 00:11:36.259 that cross -references your daily calendar meetings 00:11:36.259 --> 00:11:38.419 automatically. It looks at the specific LinkedIn 00:11:38.419 --> 00:11:40.700 profiles of the meeting attendees. It reads their 00:11:40.700 --> 00:11:42.919 last three published posts on the social network. 00:11:43.120 --> 00:11:45.500 It generates a highly comprehensive briefing 00:11:45.500 --> 00:11:48.720 dossier right on your computer desktop. It does 00:11:48.720 --> 00:11:51.220 all of this exactly 10 minutes before the scheduled 00:11:51.220 --> 00:11:54.129 call. That is an incredible mind -bending insight 00:11:54.129 --> 00:11:57.029 into the true system potential. You can also 00:11:57.029 --> 00:12:00.450 pull broad LinkedIn post -performance data. Completely 00:12:00.450 --> 00:12:03.049 automatically. You can easily show post impressions, 00:12:03.289 --> 00:12:06.009 user reactions, and specific comments automatically. 00:12:06.190 --> 00:12:08.570 Sort everything incredibly smoothly by the overall 00:12:08.570 --> 00:12:11.289 human user engagement rate automatically. Then 00:12:11.289 --> 00:12:13.309 you can do something really incredibly clever 00:12:13.309 --> 00:12:16.529 with that data. Have the visual dashboard flag 00:12:16.529 --> 00:12:19.789 specific high -value user comments automatically 00:12:19.789 --> 00:12:22.090 for you. Look for new comments containing the 00:12:22.090 --> 00:12:24.789 specific word sponsor or collab immediately. 00:12:25.250 --> 00:12:27.610 It lets you reply incredibly fast to very warm 00:12:27.610 --> 00:12:31.100 business leads. this highly specific business 00:12:31.100 --> 00:12:33.940 dashboard simply does not exist anywhere. With 00:12:33.940 --> 00:12:36.779 MCP, it takes one clear prompt and a few short 00:12:36.779 --> 00:12:39.879 minutes. Whoa, imagine scaling to a billion queries. 00:12:40.179 --> 00:12:42.759 The true potential for massive scaling is truly 00:12:42.759 --> 00:12:45.500 staggering to consider deeply. Are there hidden 00:12:45.500 --> 00:12:48.039 financial traps when hooking up thousands of 00:12:48.039 --> 00:12:50.460 apps this way? A free account works to start, 00:12:50.460 --> 00:12:53.179 but high -volume automated data pulling will 00:12:53.179 --> 00:12:55.720 definitely require a paid upgrade. High -volume 00:12:55.720 --> 00:12:59.080 usage requires a paid Zapier upgrade. to sex 00:12:59.080 --> 00:13:02.000 silence. We truly need to talk about aesthetics 00:13:02.000 --> 00:13:04.799 and hidden system pitfalls now. Daily function 00:13:04.799 --> 00:13:07.740 is highly important, but visual look and feel 00:13:07.740 --> 00:13:10.240 really matter. Making it visually beautiful means 00:13:10.240 --> 00:13:13.320 you will actually use it every day. Human -computer 00:13:13.320 --> 00:13:15.840 interaction aesthetics play a massive, highly 00:13:15.840 --> 00:13:18.659 critical psychological role here. A beautiful 00:13:18.659 --> 00:13:21.000 software dashboard genuinely makes you want to 00:13:21.000 --> 00:13:23.519 work deeply today. If the visual software design 00:13:23.519 --> 00:13:26.559 is highly boring, you abandon it entirely. Never 00:13:26.559 --> 00:13:29.240 let the Claude AI model guess the visual interface 00:13:29.240 --> 00:13:31.740 style. It will just quickly use a very generic, 00:13:31.779 --> 00:13:34.299 basic visual design language. You must strictly 00:13:34.299 --> 00:13:36.539 instruct it clearly in your very first text prompt. 00:13:37.000 --> 00:13:39.059 Tell the model you want a clean, dark mode visual 00:13:39.059 --> 00:13:41.840 layout. Ask for bright white text with highly 00:13:41.840 --> 00:13:44.419 sharp orange visual interface accents. You can 00:13:44.419 --> 00:13:46.759 visually iterate carefully after the first successful 00:13:46.759 --> 00:13:49.200 working system build. Once the correct underlying 00:13:49.200 --> 00:13:52.000 data flows, ask for visual layout interface changes. 00:13:52.240 --> 00:13:54.580 Move the daily calendar to the right side of 00:13:54.580 --> 00:13:57.379 the computer screen. Add a small digital clock 00:13:57.379 --> 00:14:00.240 clearly showing the current USA local time. Make 00:14:00.240 --> 00:14:03.279 the daily priority task list a little bit physically 00:14:03.279 --> 00:14:06.799 much larger. Let us discuss very common user 00:14:06.799 --> 00:14:10.120 mistakes that break the entire machine. Connecting 00:14:10.120 --> 00:14:13.340 way too many data sources at once is a huge trap. 00:14:13.700 --> 00:14:16.200 Connecting six data sources on day one is like 00:14:16.200 --> 00:14:18.799 trying to juggle six chainsaws. Right. When it 00:14:18.799 --> 00:14:21.539 drops, you won't know which one cut you. Start 00:14:21.539 --> 00:14:24.139 with just two basic data connectors to be totally 00:14:24.139 --> 00:14:26.840 safe. Get those working entirely perfectly before 00:14:26.840 --> 00:14:29.259 you add anything more highly complex. Another 00:14:29.259 --> 00:14:31.759 highly common pitfall is not naming your live 00:14:31.759 --> 00:14:35.120 visual artifacts properly. Ten visually unique 00:14:35.120 --> 00:14:38.019 working dashboards called Untitled is absolute 00:14:38.019 --> 00:14:41.200 daily workflow madness. This creates a massive 00:14:41.200 --> 00:14:43.259 organizational problem for your future working 00:14:43.259 --> 00:14:45.759 self. Forgetting they act completely silently 00:14:45.759 --> 00:14:48.820 is also a very major operational risk. A connected 00:14:48.820 --> 00:14:51.360 dashboard with full write access executes its 00:14:51.360 --> 00:14:54.120 defined actions immediately. There is absolutely 00:14:54.120 --> 00:14:57.600 no confirmation window and absolutely no human 00:14:57.600 --> 00:15:00.679 safety pause. Test everything carefully with 00:15:00.679 --> 00:15:03.980 read -only access first to stay completely digitally 00:15:03.980 --> 00:15:06.860 safe. If I ask the AI to completely rearrange 00:15:06.860 --> 00:15:09.320 the layout, does it break the data pipes? Not 00:15:09.320 --> 00:15:11.179 at all. Visual tweaks keep the data connection 00:15:11.179 --> 00:15:13.679 totally intact. Visual tweaks keep the data pipes 00:15:13.679 --> 00:15:16.710 fully intact. Beat. Let us deliberately slow 00:15:16.710 --> 00:15:20.289 down and carefully recap the big core idea to 00:15:20.289 --> 00:15:23.070 sex silence. Static web dashboards steal your 00:15:23.070 --> 00:15:25.509 highly expensive tokens and your precious time. 00:15:25.690 --> 00:15:27.870 Live clawed artifacts quickly give you back 20 00:15:27.870 --> 00:15:30.889 to 30 minutes daily. The entire working technology 00:15:30.889 --> 00:15:33.269 stack is actually elegantly highly simple to 00:15:33.269 --> 00:15:35.590 build. You just absolutely need the desktop application 00:15:35.590 --> 00:15:38.169 and co -work mode actively enabled. Set up a 00:15:38.169 --> 00:15:40.269 highly dedicated working folder on your local 00:15:40.269 --> 00:15:42.590 physical machine. Wire up your native authorized 00:15:42.590 --> 00:15:44.929 connectors for the initial internal data flow. 00:15:45.230 --> 00:15:47.990 Use the MCP Zapier Universal Adapter for everything 00:15:47.990 --> 00:15:50.529 else you might need. And carefully write one 00:15:50.529 --> 00:15:54.070 highly clear, highly specific structural instruction 00:15:54.070 --> 00:15:57.100 text prompt. Start building your completely new 00:15:57.100 --> 00:15:59.600 automated daily morning system literally right 00:15:59.600 --> 00:16:02.480 today. Use the highly simple starter prompt we 00:16:02.480 --> 00:16:05.059 clearly discussed earlier in the episode. Build 00:16:05.059 --> 00:16:07.740 a daily focused dashboard, constantly pulling 00:16:07.740 --> 00:16:10.399 live Gmail and Google Calendar. Show your highly 00:16:10.399 --> 00:16:13.480 urgent daily emails and your upcoming daily scheduled 00:16:13.480 --> 00:16:15.720 meetings. Add a simple functional to -do list 00:16:15.720 --> 00:16:18.480 you can easily edit visually directly. Get it 00:16:18.480 --> 00:16:20.620 running incredibly smoothly and use it daily 00:16:20.620 --> 00:16:23.110 for a full week. Only then should you carefully 00:16:23.110 --> 00:16:25.870 add your next highly complex data layer. The 00:16:25.870 --> 00:16:28.149 tools you are already paying for can do infinitely 00:16:28.149 --> 00:16:30.070 more than what you're asking of them right now. 00:16:30.649 --> 00:16:32.509 What other friction in your morning routine is 00:16:32.509 --> 00:16:34.629 secretly just waiting to be automated? Beat. 00:16:35.049 --> 00:16:35.470 Keep digging.