WEBVTT 00:00:00.000 --> 00:00:02.359 We're witnessing a profound paradigm shift right 00:00:02.359 --> 00:00:06.339 now. We're moving away from treating AI as a 00:00:06.339 --> 00:00:09.779 simple chatbot. We're architecting autonomous 00:00:09.779 --> 00:00:12.560 five -person marketing agencies. Yeah. And we're 00:00:12.560 --> 00:00:17.739 doing it inside a single folder. Beat. Welcome 00:00:17.739 --> 00:00:21.579 to the Deep Dive. Today, we're exploring a radically 00:00:21.579 --> 00:00:24.760 different way to work. We're completely rethinking 00:00:24.760 --> 00:00:27.640 human -computer interaction here. I mean, it's 00:00:27.640 --> 00:00:29.519 not about writing one perfect prompt anymore. 00:00:29.620 --> 00:00:32.240 It's about building a structured digital ecosystem. 00:00:32.619 --> 00:00:34.140 If you're listening to this, you've probably 00:00:34.140 --> 00:00:38.340 spent hours wrangling a generic AI. Oh, yeah. 00:00:38.539 --> 00:00:40.539 You try to get it to write just one decent email, 00:00:40.640 --> 00:00:42.340 and it usually ends up sounding... Right, and 00:00:42.340 --> 00:00:44.500 then it starts with, you know, in today's fast 00:00:44.500 --> 00:00:46.700 -paced digital landscape. It drives people insane. 00:00:46.960 --> 00:00:49.000 It really does. Our mission today is highly specific. 00:00:49.469 --> 00:00:51.549 We're going to unpack exactly how to turn Claude 00:00:51.549 --> 00:00:54.530 Code into a repeatable marketing system. We'll 00:00:54.530 --> 00:00:56.390 use a test case of a travel brand. The brand 00:00:56.390 --> 00:00:58.710 is called Go Travel. We'll look at how this system 00:00:58.710 --> 00:01:02.729 builds an entire campaign autonomously. Beat. 00:01:02.829 --> 00:01:05.530 Okay, let's unpack this. I am incredibly ready 00:01:05.530 --> 00:01:08.030 for this. The framework we are looking at is... 00:01:08.219 --> 00:01:11.079 Brilliant. It completely solves the blank page 00:01:11.079 --> 00:01:13.180 problem. Before we can build the software environment, 00:01:13.359 --> 00:01:15.760 we have to conceptually define our employees. 00:01:15.920 --> 00:01:18.420 Right. We're building an AI agency. So we need 00:01:18.420 --> 00:01:20.200 to understand the fundamental difference between 00:01:20.200 --> 00:01:23.200 a skill and an agent. This is the core rule of 00:01:23.200 --> 00:01:25.519 the entire setup. You know, people try to automate 00:01:25.519 --> 00:01:27.560 their entire business on day one. Yeah. They 00:01:27.560 --> 00:01:30.719 end up with an AI that's like. aggressively replying 00:01:30.719 --> 00:01:33.200 to their mom's emails, you have to start with 00:01:33.200 --> 00:01:34.819 the foundational element. If we're setting up 00:01:34.819 --> 00:01:37.299 this system, we start with skills. Exactly. A 00:01:37.299 --> 00:01:39.859 skill is a repeatable workflow. It's a highly 00:01:39.859 --> 00:01:42.780 specific playbook. You don't just ask the AI 00:01:42.780 --> 00:01:45.900 to write a blog post. You create a custom blog 00:01:45.900 --> 00:01:48.180 writing skill. Walk me through what that actually 00:01:48.180 --> 00:01:51.620 looks like mechanically. It's a document containing 00:01:51.620 --> 00:01:55.079 specific SEO rules. It includes your exact brand 00:01:55.079 --> 00:01:58.439 voice guidelines. It has internal linking rules. 00:01:58.569 --> 00:02:01.549 It even has an editing checklist. Wow. The AI 00:02:01.549 --> 00:02:04.109 doesn't guess anymore. It reads that file and 00:02:04.109 --> 00:02:06.310 follows your predefined process. It's like a 00:02:06.310 --> 00:02:09.729 restaurant. The skills are the exact recipe cards. 00:02:09.810 --> 00:02:12.770 Yeah. And the agents are the specific chefs working 00:02:12.770 --> 00:02:14.409 the stations. That's a perfect way to visualize 00:02:14.409 --> 00:02:17.110 it. The agents are the specialized team members. 00:02:17.250 --> 00:02:19.689 They execute those specific recipes. You might 00:02:19.689 --> 00:02:21.830 have a market researcher. You might have a creative 00:02:21.830 --> 00:02:24.189 designer. They have entirely different cognitive 00:02:24.189 --> 00:02:26.509 jobs. Hovering above all of this is something 00:02:26.509 --> 00:02:31.699 called a clay .md file. Right. A .md or Markdown 00:02:31.699 --> 00:02:35.159 file is a basic text document that strips away 00:02:35.159 --> 00:02:38.919 messy formatting. Okay. This specific file acts 00:02:38.919 --> 00:02:41.039 as the general manager. It gives the overarching 00:02:41.039 --> 00:02:43.879 instructions. It tells the chefs which recipes 00:02:43.879 --> 00:02:46.819 to use. I have to push back here. Sure. Why do 00:02:46.819 --> 00:02:49.120 we need separate agents? Yeah. Why not just ask 00:02:49.120 --> 00:02:51.960 one super smart AI to do everything at once? 00:02:52.139 --> 00:02:55.199 Because mixing complex tasks leads to massive 00:02:55.199 --> 00:02:58.360 logic degradation. If one chat window tries to 00:02:58.479 --> 00:03:00.819 write content, analyze data, and build strategy 00:03:00.819 --> 00:03:04.539 simultaneously, it loses focus. Its attention 00:03:04.539 --> 00:03:06.919 mechanism gets scattered. I see. An agent must 00:03:06.919 --> 00:03:10.159 have one clear, isolated responsibility. So the 00:03:10.159 --> 00:03:13.020 market researcher only finds trends. They absolutely 00:03:13.020 --> 00:03:15.879 do not design the ad visuals. Right. And just 00:03:15.879 --> 00:03:18.919 like a real kitchen, if the fry cook tries to 00:03:18.919 --> 00:03:21.800 bake the souffle, it's a disaster. Yeah. The 00:03:21.800 --> 00:03:23.639 creative designer doesn't touch the campaign 00:03:23.639 --> 00:03:26.599 data. You keep the roles strictly separated. 00:03:27.159 --> 00:03:29.699 How do you actually focus the AI so it doesn't 00:03:29.699 --> 00:03:32.599 wander off task? Well, you define strict limitations 00:03:32.599 --> 00:03:35.400 clearly in its setup file. You tell it exactly 00:03:35.400 --> 00:03:37.300 what it should never do. So you're essentially 00:03:37.300 --> 00:03:39.719 building a highly controlled digital assembly 00:03:39.719 --> 00:03:43.300 line. You are. And it works beautifully. Now 00:03:43.300 --> 00:03:45.680 that we know our team's roles, where do these 00:03:45.680 --> 00:03:48.139 digital chefs actually work? Right. They need 00:03:48.139 --> 00:03:50.259 a highly organized kitchen. They need a permanent 00:03:50.259 --> 00:03:53.300 workspace. For this setup, the source heavily 00:03:53.300 --> 00:03:56.080 recommends using VS Code. That's Visual Studio 00:03:56.080 --> 00:03:58.750 Code. A popular app where developers write code 00:03:58.750 --> 00:04:01.750 and organize files. Exactly. Beat. But why use 00:04:01.750 --> 00:04:03.969 a coding app instead of a normal browser chat 00:04:03.969 --> 00:04:06.069 window? Because a chat window is basically a 00:04:06.069 --> 00:04:08.650 goldfish. It forgets everything. Then this code 00:04:08.650 --> 00:04:11.710 gives the AI spatial awareness. Cloud code can 00:04:11.710 --> 00:04:14.330 actually read your local folders. It can see 00:04:14.330 --> 00:04:17.910 your files, your skills, and your final outputs 00:04:17.910 --> 00:04:20.810 all in one place. If I understand the source 00:04:20.810 --> 00:04:23.329 correctly, we're dividing this digital workspace 00:04:23.329 --> 00:04:27.290 into two distinct folder types. System folders 00:04:27.290 --> 00:04:29.569 and working folder. That's the architectural 00:04:29.569 --> 00:04:32.910 secret. Think of system folders as the AI's long 00:04:32.910 --> 00:04:35.829 -term memory. What actually goes into those system 00:04:35.829 --> 00:04:38.290 folders to build that memory? This is where you 00:04:38.290 --> 00:04:41.430 put a context folder, an SOP folder, and a templates 00:04:41.430 --> 00:04:44.430 folder. This teaches the AI about your business. 00:04:44.730 --> 00:04:47.709 You drop in your brand voice guide. You add your 00:04:47.709 --> 00:04:50.250 ideal customer personas. You include your current 00:04:50.250 --> 00:04:53.069 marketing strategy. So GoTravel, our test brand. 00:04:53.439 --> 00:04:55.899 needs the AI to deeply understand its target 00:04:55.899 --> 00:04:58.259 demographic. Right. It needs to know the exact 00:04:58.259 --> 00:05:00.680 tone to use for adventurous millennials. Without 00:05:00.680 --> 00:05:03.879 that context folder, the AI just defaults to 00:05:03.879 --> 00:05:07.319 generic corporate speak. With it, the AI sounds 00:05:07.319 --> 00:05:09.819 like your best copywriter. I have to offer a 00:05:09.819 --> 00:05:12.660 vulnerable admission here. Oh. I still wrestle 00:05:12.660 --> 00:05:14.879 with prompt drift myself when staring at a blank 00:05:14.879 --> 00:05:17.660 chat window. It's incredibly frustrating. It 00:05:17.660 --> 00:05:19.720 happens to everyone. I mean, prompt drift is 00:05:19.720 --> 00:05:22.139 when the AI forgets original instructions over 00:05:22.139 --> 00:05:25.079 a long chat. By the 10th prompt, it's completely 00:05:25.079 --> 00:05:27.319 lost the plot. But if we're using the system 00:05:27.319 --> 00:05:30.079 folder structure, the context becomes permanent. 00:05:30.279 --> 00:05:34.420 Exactly. Because VS Code reads that claudeu .md 00:05:34.420 --> 00:05:37.259 file automatically in the background. It acts 00:05:37.259 --> 00:05:41.519 as a persistent system prompt. The AI physically 00:05:41.519 --> 00:05:44.860 cannot forget your brand. Those rules are injected 00:05:44.860 --> 00:05:47.779 into its memory every single time you hit enter. 00:05:47.920 --> 00:05:50.579 So if the system folders act as the AI's long 00:05:50.579 --> 00:05:53.540 -term memory, where does it put its actual daily 00:05:53.540 --> 00:05:56.189 work without cluttering up its brain? That's 00:05:56.189 --> 00:05:57.930 where the working folders come in. You create 00:05:57.930 --> 00:06:00.649 folders named ads, pages, reports, and social 00:06:00.649 --> 00:06:03.290 creatives. Okay. This is where Claude saves the 00:06:03.290 --> 00:06:05.569 polished outputs. And the ultimate routing manager 00:06:05.569 --> 00:06:07.889 for all these folders remains that manager file. 00:06:08.089 --> 00:06:10.069 Yeah. It tells the AI exactly what the project 00:06:10.069 --> 00:06:12.310 is about. It maps out how the folders are organized. 00:06:12.569 --> 00:06:14.709 Right. It tells the AI exactly where new files 00:06:14.709 --> 00:06:16.970 should be saved. How do you prevent context overload 00:06:16.970 --> 00:06:19.689 when the AI scans all these different folders? 00:06:20.139 --> 00:06:22.339 You configure the manager file to direct the 00:06:22.339 --> 00:06:25.100 AI only to specific context files when performing 00:06:25.100 --> 00:06:28.120 specific tasks. So the routing file acts as a 00:06:28.120 --> 00:06:30.079 protective cognitive filter. That's a great way 00:06:30.079 --> 00:06:32.420 to put it. The digital workspace is built. Before 00:06:32.420 --> 00:06:34.860 hiring the specific agents, we need to stock 00:06:34.860 --> 00:06:37.680 the shelves with our workflows. Yes. We need 00:06:37.680 --> 00:06:40.319 to craft the actual playbooks. The skills library. 00:06:40.600 --> 00:06:43.420 This is my favorite part. This is where you store 00:06:43.420 --> 00:06:45.860 your repeatable workflows so you never have to 00:06:45.860 --> 00:06:49.000 explain a task twice. The source strongly advises 00:06:49.000 --> 00:06:52.259 starting small here. Start with just three to 00:06:52.259 --> 00:06:54.980 five tasks you repeat weekly. People always try 00:06:54.980 --> 00:06:57.620 to build 50 skills on day one. It's a classic 00:06:57.620 --> 00:07:00.939 mistake. Build one skill, test it, refine it, 00:07:01.019 --> 00:07:02.939 make sure it works perfectly before moving on. 00:07:03.100 --> 00:07:05.300 Let's look at a specific playbook from the source 00:07:05.300 --> 00:07:08.579 material, the branded deck skill. This completely 00:07:08.579 --> 00:07:10.379 changes the game for creating presentations. 00:07:10.779 --> 00:07:13.240 Instead of getting a generic slide layout, you 00:07:13.240 --> 00:07:16.480 teach the AI your exact corporate style. How 00:07:16.480 --> 00:07:19.000 does an AI actually study a corporate style? 00:07:19.290 --> 00:07:21.709 Well, you drop a finished PowerPoint template 00:07:21.709 --> 00:07:25.589 into the templates folder. You ask Claude to 00:07:25.589 --> 00:07:28.470 analyze its underlying structure. Okay. It reads 00:07:28.470 --> 00:07:31.910 the XML code. It analyzes the specific hex colors. 00:07:32.149 --> 00:07:34.810 It studies the typography and spacing rules. 00:07:35.089 --> 00:07:37.209 It essentially creates a reverse -engineered, 00:07:37.209 --> 00:07:39.970 detailed report on what makes your deck feel 00:07:39.970 --> 00:07:43.610 uniquely on -brand. Exactly. Then you save that 00:07:43.610 --> 00:07:46.509 report as a permanent skill. The next time you 00:07:46.509 --> 00:07:49.149 need a strategy deck, the AI automatically applies 00:07:49.149 --> 00:07:51.949 those exact design parameters. That is a massive 00:07:51.949 --> 00:07:54.910 time saver. Huge. There's also the social creative 00:07:54.910 --> 00:07:57.629 design skill. This one functions slightly differently. 00:07:57.949 --> 00:08:00.310 Yeah, this one is about capturing a vibe. You 00:08:00.310 --> 00:08:02.970 store strong visual references in an examples 00:08:02.970 --> 00:08:05.509 holder. Then you pair it with a style guide document. 00:08:05.790 --> 00:08:07.689 It studies the image direction and the visual 00:08:07.689 --> 00:08:09.930 mood. It doesn't just copy a single template 00:08:09.930 --> 00:08:13.410 rigidly. Right. But doesn't forcing the AI to 00:08:13.410 --> 00:08:16.300 study past examples. kill its creativity and 00:08:16.300 --> 00:08:18.860 make the output robotic. What's fascinating here 00:08:18.860 --> 00:08:20.959 is that constraints actually breed creativity. 00:08:21.319 --> 00:08:25.279 Yeah. When you give the AI a defined sandbox 00:08:25.279 --> 00:08:28.620 of approved colors and moods, it stops generating 00:08:28.620 --> 00:08:32.440 generic stock photo aesthetics. It starts combining 00:08:32.440 --> 00:08:35.039 your specific brand elements in highly creative, 00:08:35.179 --> 00:08:37.879 unexpected ways. Freedom within a strict framework. 00:08:38.039 --> 00:08:40.700 Exactly. That makes a lot of sense. The AI needs 00:08:40.700 --> 00:08:43.960 boundaries to be truly clever. How do you handle 00:08:43.960 --> 00:08:47.059 updating these skills over time when your brand 00:08:47.059 --> 00:08:50.120 strategy changes? You simply open the specific 00:08:50.120 --> 00:08:53.179 skill text file, rewrite the outdated step, and 00:08:53.179 --> 00:08:56.080 the AI instantly adopts a new process. So dynamic 00:08:56.080 --> 00:08:58.480 skill files prevent the system from getting stale. 00:08:58.580 --> 00:09:00.860 They make evolving your business incredibly seamless. 00:09:01.200 --> 00:09:03.419 Our playbooks are officially written. Now we 00:09:03.419 --> 00:09:06.000 use the slash agents command to hire the specialized 00:09:06.000 --> 00:09:07.919 talent to read them. We're finally assembling 00:09:07.919 --> 00:09:10.639 the AI team. For GoTravel, the test system created 00:09:10.639 --> 00:09:13.700 five highly specific agents. First up is the 00:09:13.700 --> 00:09:16.100 market researcher. This agent dives into audience 00:09:16.100 --> 00:09:18.899 insights, seasonal friends, and competitor angles. 00:09:19.120 --> 00:09:21.279 Second is the campaign strategist. Right. They 00:09:21.279 --> 00:09:23.659 take that raw research and turn it into actionable 00:09:23.659 --> 00:09:26.779 campaign ideas. offers and messaging. Third is 00:09:26.779 --> 00:09:29.980 the content creator. They write the actual deliverables, 00:09:30.019 --> 00:09:32.620 blog posts, social captions, and lead magnets. 00:09:32.919 --> 00:09:35.120 Fourth is the creative designer. They handle 00:09:35.120 --> 00:09:38.120 the visual direction and specific ad creatives. 00:09:38.200 --> 00:09:41.919 And finally, the data analyst. Yeah. They read 00:09:41.919 --> 00:09:43.860 the post campaign data and build performance 00:09:43.860 --> 00:09:46.259 dashboards to see what worked. We mentioned this 00:09:46.259 --> 00:09:49.000 briefly, but the golden rule here is keeping 00:09:49.000 --> 00:09:51.559 roles completely separate. You have to avoid 00:09:51.559 --> 00:09:55.399 functional overlap at all costs. The market researcher 00:09:55.399 --> 00:09:58.080 structures their data strictly so the strategist 00:09:58.080 --> 00:10:00.980 can read it. They don't try to draft the social 00:10:00.980 --> 00:10:03.720 posts. It's like stacking Lego blocks of data. 00:10:03.860 --> 00:10:06.240 Each agent perfectly builds on the previous one 00:10:06.240 --> 00:10:08.419 without stepping on any toes. That's exactly 00:10:08.419 --> 00:10:11.179 how the system avoids chaos. You use a built 00:10:11.179 --> 00:10:13.519 -in command called slash agents to generate these 00:10:13.519 --> 00:10:16.299 roles. Claude actively asks what the agent should 00:10:16.299 --> 00:10:18.679 do, which tools it can use, and which skills 00:10:18.679 --> 00:10:21.399 it has access to. And it saves a permanent agent 00:10:21.399 --> 00:10:24.440 file inside your project. Yeah. That file defines 00:10:24.440 --> 00:10:27.440 the specific working style for that digital employee. 00:10:27.929 --> 00:10:30.149 You keep their system prompts incredibly simple. 00:10:30.309 --> 00:10:32.970 You outline their main job. You list their specific 00:10:32.970 --> 00:10:36.029 skills. Most importantly, you explicitly list 00:10:36.029 --> 00:10:39.110 what they must never do. How do you stop agent 00:10:39.110 --> 00:10:41.730 boundary bleed when marketing tasks naturally 00:10:41.730 --> 00:10:44.889 overlap? Well, you clearly specify in the agent 00:10:44.889 --> 00:10:47.830 system prompt which upstream or downstream agent 00:10:47.830 --> 00:10:51.070 they must hand the work off to. So clear boundaries 00:10:51.070 --> 00:10:53.509 prevent the digital chefs from constantly fighting. 00:10:53.690 --> 00:10:57.529 Good fences make for very good AI agents. We 00:10:57.529 --> 00:10:59.870 have the specialized team. We have the comprehensive 00:10:59.870 --> 00:11:03.009 playbooks. Yep. But if you drop a massive project 00:11:03.009 --> 00:11:06.210 on their desk, who grabs it first? We need routing 00:11:06.210 --> 00:11:08.850 rules. This is the actual operating system of 00:11:08.850 --> 00:11:12.090 the entire agency. Without routing rules, Claude 00:11:12.090 --> 00:11:15.149 might call the wrong agent. Or it might use a 00:11:15.149 --> 00:11:17.649 heavy slow agent when a simple skill would work 00:11:17.649 --> 00:11:19.669 perfectly. We update the overarching manager 00:11:19.669 --> 00:11:21.789 file with these logic rules. Right. The simplest 00:11:21.789 --> 00:11:24.610 heuristic to use is this. Use a skill for simple 00:11:24.610 --> 00:11:27.470 execution and formatting. Use an agent for tasks 00:11:27.470 --> 00:11:30.009 needing judgment, deep thinking, or synthesis. 00:11:30.309 --> 00:11:32.769 If you just need a format change from a blog 00:11:32.769 --> 00:11:35.809 to an email, use a skill. Exactly. If you need 00:11:35.809 --> 00:11:37.549 to figure out a controversial campaign angle, 00:11:37.710 --> 00:11:40.710 triggers the campaign strategist agent. Let's 00:11:40.710 --> 00:11:42.610 look at the ultimate test outlined in the source. 00:11:43.230 --> 00:11:46.110 The Japan cherry blossom season campaign. This 00:11:46.110 --> 00:11:48.450 is where the theory gets real. Yeah. We give 00:11:48.450 --> 00:11:52.309 Claude one complex campaign task. Create a full 00:11:52.309 --> 00:11:56.009 Japan cherry blossom season campaign for GoTravel. 00:11:56.169 --> 00:11:58.929 We're asking for market research, a strategic 00:11:58.929 --> 00:12:02.529 brief, social posts, ad creatives, and a fully 00:12:02.529 --> 00:12:05.399 coded landing page. All from one prompt. Walk 00:12:05.399 --> 00:12:07.679 us through how they pass the baton. Okay. First, 00:12:07.980 --> 00:12:10.620 the manager reads the routing rules and activates 00:12:10.620 --> 00:12:13.379 the market researcher. It crawls for current 00:12:13.379 --> 00:12:16.240 travel trends. It discovers that travelers are 00:12:16.240 --> 00:12:19.000 actually exhausted by crowded Kyoto spots. They 00:12:19.000 --> 00:12:21.379 want hidden neighborhood gems. Next, the campaign 00:12:21.379 --> 00:12:23.940 strategist takes that specific data block. Right. 00:12:24.019 --> 00:12:27.019 It creates a strategic brief called Sakura Like 00:12:27.019 --> 00:12:29.970 a Local. The ankle isn't just about pretty flowers 00:12:29.970 --> 00:12:33.409 anymore. It's about a highly local, guided, less 00:12:33.409 --> 00:12:36.669 touristy experience. Wow. The brief rigidly defines 00:12:36.669 --> 00:12:39.429 the core message and the specific travel offer. 00:12:39.629 --> 00:12:41.809 Then the content creator agent steps in. Yeah. 00:12:41.909 --> 00:12:44.690 It's instructed to draft posts based only on 00:12:44.690 --> 00:12:47.529 that specific brief. It can invent new offers. 00:12:48.080 --> 00:12:50.480 It writes engaging posts about local neighborhood 00:12:50.480 --> 00:12:53.179 etiquette or common mistakes eager tourists make 00:12:53.179 --> 00:12:55.899 during the season. After that, the creative designer 00:12:55.899 --> 00:12:59.279 activates the social creative design skill. It 00:12:59.279 --> 00:13:01.899 references the style guide to make visuals matching 00:13:01.899 --> 00:13:04.919 that exact local vibe. Finally, the landing page 00:13:04.919 --> 00:13:07.960 skill uses all those assets to build the actual 00:13:07.960 --> 00:13:11.139 site. It uses the exact same message, the approved 00:13:11.139 --> 00:13:13.720 offer, and the foundational audience insight. 00:13:13.919 --> 00:13:18.360 Ooh. Imagine scaling this to a billion queries. 00:13:18.659 --> 00:13:21.840 Yeah. You could run hundreds of highly specialized 00:13:21.840 --> 00:13:24.500 localized campaigns simultaneously while you 00:13:24.500 --> 00:13:27.480 sleep. It's entirely possible today because every 00:13:27.480 --> 00:13:29.980 final output is logically connected. It's not 00:13:29.980 --> 00:13:32.740 a random quirky caption or a generic cherry blossom 00:13:32.740 --> 00:13:36.159 image. Everything flows downstream from one centralized 00:13:36.159 --> 00:13:38.500 strategic brief. How do you break down these 00:13:38.500 --> 00:13:40.940 massive complex campaigns so that the system 00:13:40.940 --> 00:13:43.659 doesn't crash halfway through? Well. You mandate 00:13:43.659 --> 00:13:46.059 in the routing rules that the AI must output 00:13:46.059 --> 00:13:48.899 a detailed step -by -step checklist before executing 00:13:48.899 --> 00:13:51.919 any actual work. So forced planning prevents 00:13:51.919 --> 00:13:55.080 the system from hallucinating wild ideas. It 00:13:55.080 --> 00:13:57.960 anchors the AI to a logical sequence before it 00:13:57.960 --> 00:14:00.840 writes a single word. This automated system works 00:14:00.840 --> 00:14:03.700 beautifully in a vacuum. Sure. But how does a 00:14:03.700 --> 00:14:06.860 human team actually interacts with it during 00:14:06.860 --> 00:14:09.259 a chaotic Tuesday afternoon. You have to connect 00:14:09.259 --> 00:14:11.559 it to the real world, use a Kanban board. The 00:14:11.559 --> 00:14:13.919 source suggests using a simple Notion task board, 00:14:14.100 --> 00:14:17.019 a standard layout. Yeah. To do. In progress. 00:14:17.519 --> 00:14:19.659 Complete. Real marketing work doesn't happen 00:14:19.659 --> 00:14:22.759 inside one clean, magical prompt. Tasks come 00:14:22.759 --> 00:14:25.120 from client emails, Slack messages, everywhere. 00:14:25.440 --> 00:14:27.620 Yeah. You need a centralized place where human 00:14:27.620 --> 00:14:30.080 managers can drop tickets for the AI to pick 00:14:30.080 --> 00:14:32.240 up. But you can't just write create social posts 00:14:32.240 --> 00:14:34.779 on an ocean ticket and expect magic. Oh, that's 00:14:34.779 --> 00:14:37.100 a recipe for disaster. The AI will just guess 00:14:37.100 --> 00:14:39.600 the context. You need highly specific bounded 00:14:39.600 --> 00:14:42.419 briefs. A good ticket looks like. Create five 00:14:42.419 --> 00:14:45.200 carousel slides for first -time Japan travelers 00:14:45.200 --> 00:14:47.980 based on the Sakura brief. The clearer the parameters 00:14:47.980 --> 00:14:51.240 of the task, the better the AI executes the workflow. 00:14:51.539 --> 00:14:53.679 And the source highlights a fascinating feature 00:14:53.679 --> 00:14:55.960 here called slash remote control. This feature 00:14:55.960 --> 00:14:59.360 is wild. It generates a secure temporary link 00:14:59.360 --> 00:15:02.000 for your active workspace. Okay. You can open 00:15:02.000 --> 00:15:04.580 it on your phone's browser. It lets you trigger 00:15:04.580 --> 00:15:07.779 your local computer's quad session from anywhere 00:15:07.779 --> 00:15:10.320 in the world. You could literally be buying coffee, 00:15:10.480 --> 00:15:14.039 check your phone, and text your AI. Yeah. Grab 00:15:14.039 --> 00:15:16.299 the highest priority Notion ticket and execute 00:15:16.299 --> 00:15:19.379 it. The AI securely reads the Notion board API. 00:15:19.799 --> 00:15:22.159 A digital bridge letting two different software 00:15:22.159 --> 00:15:24.899 programs talk. Right. It picks up the top task. 00:15:25.159 --> 00:15:27.559 It reads the writing rules to decide which agent 00:15:27.559 --> 00:15:30.720 to use. It does the heavy lifting. It saves the 00:15:30.720 --> 00:15:33.159 deliverables in the correct working folder. And 00:15:33.159 --> 00:15:36.279 finally, it marks the Notion ticket as complete. 00:15:36.879 --> 00:15:39.639 So what does this all mean? It means we've genuinely 00:15:39.639 --> 00:15:43.779 moved from querying an AI chatbot. to managing 00:15:43.779 --> 00:15:46.240 a digital co -worker pulling tickets from a queue. 00:15:46.440 --> 00:15:48.879 It's a profound shift in daily productivity. 00:15:49.279 --> 00:15:51.759 You aren't manually assigning tiny copy -paste 00:15:51.759 --> 00:15:54.120 steps anymore. You're managing an intelligence 00:15:54.120 --> 00:15:56.559 system. What happens if a human writes a notion 00:15:56.559 --> 00:15:59.059 ticket that is just too vague for the system 00:15:59.059 --> 00:16:01.919 to process? The AI will confidently generate 00:16:01.919 --> 00:16:05.679 a highly generic, useless output, proving that 00:16:05.679 --> 00:16:09.169 garbage in always equals garbage out. So vague 00:16:09.169 --> 00:16:11.889 inputs still guarantee completely useless AI 00:16:11.889 --> 00:16:14.769 output. Always. You absolutely cannot automate 00:16:14.769 --> 00:16:17.250 bad management. Let's recap the big idea here. 00:16:17.889 --> 00:16:21.470 Beep. The real shift isn't about writing better 00:16:21.470 --> 00:16:24.129 single prompts. Yeah. Prompts engineering is 00:16:24.129 --> 00:16:26.740 becoming obsolete. it's about building a structured 00:16:26.740 --> 00:16:29.259 operating system by combining permanent brand 00:16:29.259 --> 00:16:32.960 context rigid skills specialized agents and strict 00:16:32.960 --> 00:16:35.840 routing rules you create something entirely new 00:16:35.840 --> 00:16:38.240 you create a reliable system that can logically 00:16:38.240 --> 00:16:41.519 plan meticulously create and organize aligned 00:16:41.519 --> 00:16:44.240 marketing campaigns autonomously. It's a full 00:16:44.240 --> 00:16:46.620 agency living inside a code editor. It completely 00:16:46.620 --> 00:16:48.779 stops being a novelty toy. It becomes a functional 00:16:48.779 --> 00:16:50.559 business engine. Which brings me to a final, 00:16:50.600 --> 00:16:52.559 slightly philosophical thought. Two sec silence. 00:16:52.840 --> 00:16:55.600 If a solo user can build a five -person agency 00:16:55.600 --> 00:16:58.750 inside a code editor today. What happens in a 00:16:58.750 --> 00:17:01.090 few years when your autonomous AI agency starts 00:17:01.090 --> 00:17:04.210 independently communicating and negotiating with 00:17:04.210 --> 00:17:06.910 other companies' autonomous AI agencies? That's 00:17:06.910 --> 00:17:08.910 a wild thought. Full machine -to -machine commerce. 00:17:09.269 --> 00:17:11.930 Your AI negotiating a sponsorship deal with my 00:17:11.930 --> 00:17:14.490 AI. We'll leave you with that to ponder. For 00:17:14.490 --> 00:17:16.890 now, grab a notebook today. Write down just three 00:17:16.890 --> 00:17:19.750 repeatable weekly workflows that you can transform 00:17:19.750 --> 00:17:23.029 into your very first AI playbooks. Start small. 00:17:23.250 --> 00:17:25.529 Pick the repetitive tasks you absolutely hate 00:17:25.529 --> 00:17:28.289 doing. Exactly. Thank you for joining us on this 00:17:28.289 --> 00:17:30.730 deep dive. Stay curious. OTPO Music.