WEBVTT 00:00:00.000 --> 00:00:05.160 It's a very specific, very modern kind of pain. 00:00:05.879 --> 00:00:09.080 You spend 20 minutes crafting this perfect prompt, 00:00:09.439 --> 00:00:11.660 you tweak it, you get the nuance just right, 00:00:12.339 --> 00:00:16.640 and finally, the AI spits out gold. It's perfect. 00:00:16.679 --> 00:00:19.059 In the chat window, it looks immaculate. Exactly. 00:00:19.679 --> 00:00:23.000 Bold headings, crisp spacing, clean bullet points, 00:00:23.160 --> 00:00:25.399 and then, I'm a genius, and then you hit copy. 00:00:25.440 --> 00:00:27.920 And then reality hits. You paste it into Google 00:00:27.920 --> 00:00:31.800 Docs. and it just implodes. Total formatting 00:00:31.800 --> 00:00:34.560 entropy. The headings are just bold text. The 00:00:34.560 --> 00:00:36.299 bullet points become these weird little hyphens 00:00:36.299 --> 00:00:38.479 that don't indent. The spacing goes crazy. And 00:00:38.479 --> 00:00:40.299 suddenly you aren't doing high -level strategy 00:00:40.299 --> 00:00:42.159 anymore. You're spending the next 20 minutes 00:00:42.159 --> 00:00:45.299 manually reformatting text like it's 1995. It 00:00:45.299 --> 00:00:48.320 is the universal last mile. problem of generative 00:00:48.320 --> 00:00:50.399 AI. We pretty much solved the creation part. 00:00:50.439 --> 00:00:53.020 Right. But the export part is still kind of stuck 00:00:53.020 --> 00:00:56.439 in the Stone Age. It turns a 10 second task into 00:00:56.439 --> 00:00:58.740 a 20 minute cleanup job. But according to the 00:00:58.740 --> 00:01:00.359 research we're looking at today, it doesn't have 00:01:00.359 --> 00:01:02.960 to be that way. Welcome back to the deep dive. 00:01:03.079 --> 00:01:05.579 Glad to be here. Today we are tackling a very 00:01:05.579 --> 00:01:09.980 practical hands on friction point. how to stop 00:01:09.980 --> 00:01:13.379 fighting with copy paste and actually master 00:01:13.379 --> 00:01:16.560 AI document exports. This is one of those topics 00:01:16.560 --> 00:01:18.840 that sounds a little dry until you realize it's 00:01:18.840 --> 00:01:20.840 probably costing you, what, an hour or two a 00:01:20.840 --> 00:01:23.340 week? At least. We're going to look at why this 00:01:23.340 --> 00:01:26.579 breaks, and more importantly, the specific workflow, 00:01:27.159 --> 00:01:29.819 using a feature called Claude Artifacts that 00:01:29.819 --> 00:01:32.200 actually fixes it. OK, so here's the roadmap 00:01:32.200 --> 00:01:34.090 for our discussion. First, we're going to look 00:01:34.090 --> 00:01:36.150 under the hood and really understand why the 00:01:36.150 --> 00:01:38.090 text breaks during that transfer. Yeah, it's 00:01:38.090 --> 00:01:40.129 a technical conflict, really. Then we'll get 00:01:40.129 --> 00:01:42.290 into the tool itself, Claude Artifacts, and why 00:01:42.290 --> 00:01:44.030 it's so different from just a standard chat. 00:01:44.390 --> 00:01:46.310 And finally, we're going to get into the magic 00:01:46.310 --> 00:01:48.609 prompts and some advanced tactics, like style 00:01:48.609 --> 00:01:51.030 guides, to make sure you never have to manually 00:01:51.030 --> 00:01:53.549 hit that indent button again. It sounds technical, 00:01:53.549 --> 00:01:55.689 but you're saying it's really about psychology. 00:01:56.250 --> 00:01:59.069 It is. It's about understanding how the AI thinks 00:01:59.069 --> 00:02:02.170 about text versus how your word processor thinks 00:02:02.170 --> 00:02:05.049 about it. Let's start there, because to me, text 00:02:05.049 --> 00:02:08.550 is text, and A is an A. So why does it look like 00:02:08.550 --> 00:02:11.069 a beautiful magazine article in the chat, but 00:02:11.069 --> 00:02:14.030 a ransom note when I paste it into Word? Well, 00:02:14.409 --> 00:02:16.849 it really comes down to a mismatch in protocols. 00:02:17.449 --> 00:02:21.650 When you're talking to a chatbot, chat GPT, Claude, 00:02:21.930 --> 00:02:25.229 Gemini, it doesn't matter. It's generating text 00:02:25.229 --> 00:02:27.990 for the web. It's usually using a format called 00:02:27.990 --> 00:02:30.310 Markdown. Markdown. Yeah, we hear that term a 00:02:30.310 --> 00:02:32.169 lot. Give us the quick and dirty definition. 00:02:32.349 --> 00:02:34.689 Think of it like shorthand for the web. It's 00:02:34.689 --> 00:02:36.830 designed to be super lightweight, really fast 00:02:36.830 --> 00:02:39.150 to render on a phone screen. So simple symbols. 00:02:39.650 --> 00:02:41.710 Exactly. A double asterisk makes things bold. 00:02:41.949 --> 00:02:44.349 A hashtag makes a header. It's purely visual. 00:02:44.590 --> 00:02:47.090 OK, but it lacks deep structure. That's the key. 00:02:47.289 --> 00:02:49.650 Now compare that to Microsoft Word or Google 00:02:49.650 --> 00:02:51.569 Docs. I mean, those are complex engines running 00:02:51.569 --> 00:02:54.750 on XML or HTML. There is a huge amount of hidden 00:02:54.750 --> 00:02:57.210 code under every single sentence. Code that says 00:02:57.210 --> 00:02:59.870 more than just make this big. Way more. It's 00:02:59.870 --> 00:03:02.189 telling the software the specific line is a heading 00:03:02.189 --> 00:03:04.810 one object. It belongs in the table of contents. 00:03:04.849 --> 00:03:07.729 It has specific margin logic. So when I copy 00:03:07.729 --> 00:03:11.110 from the chat, I'm just copying that surface 00:03:11.110 --> 00:03:14.250 level shorthand. But I'm leaving all that deep 00:03:14.250 --> 00:03:16.889 structure behind. Precisely. You're copying the 00:03:16.889 --> 00:03:20.469 look, not the logic. So when you paste it, word 00:03:20.469 --> 00:03:23.189 has to guess. Right. It sees a bold sentence 00:03:23.189 --> 00:03:26.729 and thinks, hmm, maybe this is a header. Or maybe 00:03:26.729 --> 00:03:28.610 they just wanted to shout. It usually just plays 00:03:28.610 --> 00:03:32.389 it safe. and leaves it as bold text, which explains 00:03:32.389 --> 00:03:35.150 why I can't auto -generate a table of contents 00:03:35.150 --> 00:03:37.490 later. Word doesn't know those are headers. It 00:03:37.490 --> 00:03:40.270 just thinks they're loud paragraphs. And those 00:03:40.270 --> 00:03:42.750 bullet points in the chat, they're just hyphens. 00:03:43.250 --> 00:03:46.150 So when you paste them, Word just sees a hyphen 00:03:46.150 --> 00:03:49.180 and a space. It doesn't see a list object. So 00:03:49.180 --> 00:03:52.520 you lose the ability to tab them, to indent them 00:03:52.520 --> 00:03:54.379 properly. Yeah, you're essentially pasting a 00:03:54.379 --> 00:03:56.379 picture of text rather than the text structure 00:03:56.379 --> 00:03:58.659 itself. The goal here isn't just to generate 00:03:58.659 --> 00:04:02.060 better words, then. It's to generate better metadata 00:04:02.060 --> 00:04:04.740 around the words. That is the key insight. If 00:04:04.740 --> 00:04:06.479 you want to be a power user of this stuff, you 00:04:06.479 --> 00:04:08.379 have to stop asking for text and start asking 00:04:08.379 --> 00:04:10.849 for structure. So fundamentally, why does the 00:04:10.849 --> 00:04:14.250 transfer fail? Because chatbots prioritize conversation, 00:04:14.789 --> 00:04:17.290 flow over the structural code needed for word 00:04:17.290 --> 00:04:20.069 processors. That makes perfect sense. It's built 00:04:20.069 --> 00:04:22.629 for speed in the moment, not for exportability 00:04:22.629 --> 00:04:26.509 later. Exactly. OK, so we know the problem. The 00:04:26.509 --> 00:04:28.709 material we looked at points to a very specific 00:04:28.709 --> 00:04:31.670 solution, and it's not a plugin. It's a built 00:04:31.670 --> 00:04:35.050 -in feature in Claude called artifacts. What 00:04:35.050 --> 00:04:37.980 is an artifact? This is a really big shift in 00:04:37.980 --> 00:04:40.160 interface design. Usually you just have one stream 00:04:40.160 --> 00:04:42.399 of text, right? The chat. Yeah, but just one 00:04:42.399 --> 00:04:44.860 long conversation. Artifact splits the screen. 00:04:45.040 --> 00:04:47.759 So two windows. Exactly. On the left, you have 00:04:47.759 --> 00:04:50.480 your chat. That's the messy conversational back 00:04:50.480 --> 00:04:53.379 and forth. But when you ask for a document, Claude 00:04:53.379 --> 00:04:56.620 opens a separate window on the right. That is 00:04:56.620 --> 00:04:59.360 the artifact. Okay, visually I get it. Left is 00:04:59.360 --> 00:05:01.420 chat, right is the file. But why does that matter 00:05:01.420 --> 00:05:03.779 for formatting? Because it changes the intent 00:05:03.779 --> 00:05:07.379 of the AI. When text is inside an artifact, the 00:05:07.379 --> 00:05:09.740 AI treats it as a standalone file. Not part of 00:05:09.740 --> 00:05:11.699 the conversation. Right. It's not chatting anymore. 00:05:11.779 --> 00:05:13.779 It's like a mental switch for the machine. It 00:05:13.779 --> 00:05:17.480 really is. Beat. Whoa. I mean, imagine the AI 00:05:17.480 --> 00:05:20.519 realizing, oh, I need to stop chatting now and 00:05:20.519 --> 00:05:23.300 start building an actual file. It creates a standalone 00:05:23.300 --> 00:05:25.839 block of structured text. And the source material 00:05:25.839 --> 00:05:27.980 mentions that copying from this window is different, 00:05:28.100 --> 00:05:30.000 right? Oh, yeah. When you copy from the artifact 00:05:30.000 --> 00:05:32.600 window, you are not just copying web text. You 00:05:32.600 --> 00:05:35.399 are copying structured text. It actually preserves 00:05:35.399 --> 00:05:39.019 the H1 and H2 tags. H1, H2 tags. Just to clarify, 00:05:39.079 --> 00:05:40.860 those are the headers we were just talking about. 00:05:41.000 --> 00:05:43.519 Correct. H1 is your main title. H2s are your 00:05:43.519 --> 00:05:46.139 section headers. When you copy from an artifact, 00:05:46.660 --> 00:05:49.060 that hidden code we talked about actually travels 00:05:49.060 --> 00:05:51.579 with the text. So when I paste it into Google 00:05:51.579 --> 00:05:54.939 Docs, the software instantly recognizes Instantly. 00:05:55.220 --> 00:05:58.019 It says, oh, this is a header and boom. your 00:05:58.019 --> 00:06:01.079 formatting is preserved. So what is the key technical 00:06:01.079 --> 00:06:03.860 difference when copying from an artifact? It 00:06:03.860 --> 00:06:05.879 preserves the hidden tags, headers, and lists 00:06:05.879 --> 00:06:08.420 that tell Word exactly how to display the text. 00:06:08.620 --> 00:06:10.420 OK, so we have the tool. We're using Claude. 00:06:10.439 --> 00:06:12.699 We're looking for that artifact window. But the 00:06:12.699 --> 00:06:15.000 guide makes a really important point here. You 00:06:15.000 --> 00:06:17.920 can't just say write a blog post and expect this 00:06:17.920 --> 00:06:20.180 to happen. No, you have to prompt it correctly. 00:06:20.660 --> 00:06:23.199 If you're vague, the AI will just chat with you. 00:06:23.199 --> 00:06:25.519 You have to drive the bus. Right. The guide breaks 00:06:25.519 --> 00:06:28.160 this down into three steps. Step one is defining 00:06:28.160 --> 00:06:31.459 the document type. Why start there? Context is 00:06:31.459 --> 00:06:34.899 everything. If you just say, write this, the 00:06:34.899 --> 00:06:37.740 AI has to guess the format. If you say, I want 00:06:37.740 --> 00:06:39.980 to write a standard operating procedure or a 00:06:39.980 --> 00:06:43.879 business proposal, the AI loads a specific structural 00:06:43.879 --> 00:06:46.240 template in its background processing. So it 00:06:46.240 --> 00:06:49.180 knows an SOP needs numbered lists and a proposal 00:06:49.180 --> 00:06:51.439 probably needs a title page. Exactly. You're 00:06:51.439 --> 00:06:54.300 setting the stage. Step two is requesting the 00:06:54.300 --> 00:06:56.779 structure first. The guide suggests asking for 00:06:56.779 --> 00:06:59.160 an outline before you get the full text. This 00:06:59.160 --> 00:07:01.519 is such a great habit for any AI writing, not 00:07:01.519 --> 00:07:04.019 just for formatting. If you let the AI guess 00:07:04.019 --> 00:07:06.259 the headers, it might give you inconsistent sizes 00:07:06.259 --> 00:07:09.680 or a weird flow. By asking for the outline first, 00:07:10.220 --> 00:07:12.439 create a detailed outline with heading one for 00:07:12.439 --> 00:07:14.939 the title and heading two for sections, you're 00:07:14.939 --> 00:07:16.899 confirming the skeleton is solid before you add 00:07:16.899 --> 00:07:19.060 the muscle. I love that analogy. Skeleton first, 00:07:19.060 --> 00:07:21.740 then muscle. Okay, step three. This is where 00:07:21.740 --> 00:07:24.500 it gets interesting. The magic prompt. Yes. The 00:07:24.500 --> 00:07:26.759 source material gives a very specific instruction. 00:07:26.980 --> 00:07:30.300 Let's read it out. Please generate this as a 00:07:30.300 --> 00:07:34.459 standalone document artifact. Ensure clean AI 00:07:34.459 --> 00:07:38.800 document formatting with proper H1, H2, and H3 00:07:38.800 --> 00:07:41.560 tags. Okay, there are three distinct triggers 00:07:41.560 --> 00:07:43.680 in that one sentence. Let's break them down. 00:07:44.220 --> 00:07:46.939 First, standalone document artifact. That's the 00:07:46.939 --> 00:07:49.060 command. That's what forces the split screen. 00:07:49.259 --> 00:07:51.800 It acts as a barrier. It tells Claude, do not 00:07:51.800 --> 00:07:53.639 put this in the chat bubble. Put it in the editor. 00:07:53.860 --> 00:07:58.120 Got it. Second, proper H1, H2, and H3 tags. This 00:07:58.120 --> 00:08:00.720 is the crucial part for the export. You're speaking 00:08:00.720 --> 00:08:03.120 the native language of the word processor. You're 00:08:03.120 --> 00:08:05.139 not asking for big, bold text. You're asking 00:08:05.139 --> 00:08:07.459 for the actual code. You're asking for header 00:08:07.459 --> 00:08:10.300 one and header two. And the third part was clean 00:08:10.300 --> 00:08:12.819 formatting. That's a quality control filter. 00:08:13.000 --> 00:08:15.259 It just tells the AI to strip out markdown errors, 00:08:15.620 --> 00:08:17.639 weird spacing, or those little hashtags that 00:08:17.639 --> 00:08:19.519 sometimes show up. So it's really about being 00:08:19.519 --> 00:08:22.379 incredibly precise. You can't assume the AI knows 00:08:22.379 --> 00:08:24.379 you want a word doc. You have to tell it which 00:08:24.379 --> 00:08:26.639 language to speak. Exactly. You have to be explicit. 00:08:26.829 --> 00:08:31.230 So why is specifying H1 and H2 tags so critical 00:08:31.230 --> 00:08:33.970 in the prompt? It forces the AI to use structural 00:08:33.970 --> 00:08:36.950 code, not just visual styling like bold text. 00:08:37.129 --> 00:08:38.970 Okay, so we've got the prompt, we're generating 00:08:38.970 --> 00:08:41.730 the document. But here's something I struggle 00:08:41.730 --> 00:08:44.330 with, and the material brings it up too. If I 00:08:44.330 --> 00:08:48.769 ask for a huge document, say 2 ,000 words, sometimes 00:08:48.769 --> 00:08:52.409 the formatting just degrades. By the end, the 00:08:52.409 --> 00:08:54.669 headers are gone, the bullets are messy. Why 00:08:54.669 --> 00:08:56.889 does that happen? I still wrestle with prompt 00:08:56.889 --> 00:08:59.909 drift myself. It's a known issue. If you ask 00:08:59.909 --> 00:09:02.169 for too much at once, the AI effectively gets, 00:09:02.549 --> 00:09:05.710 well, lazy is the best word for it. It gets tired. 00:09:05.769 --> 00:09:08.210 It loses track. It loses track of the formatting 00:09:08.210 --> 00:09:10.830 rules you set at the beginning. Its context window 00:09:10.830 --> 00:09:12.710 gets filled up with the content it's generating. 00:09:12.809 --> 00:09:15.389 So how do we fix that? The guide suggests chunking. 00:09:15.470 --> 00:09:17.830 Chunking is essential. Don't try to eat the whole 00:09:17.830 --> 00:09:20.009 elephant in one bite. You write the document 00:09:20.009 --> 00:09:22.250 section by section, but within the same artifact. 00:09:22.399 --> 00:09:24.639 How does that look in practice? You start with 00:09:24.639 --> 00:09:26.500 prompt one, write the introduction in section 00:09:26.500 --> 00:09:28.419 one. It generates that in the artifact window 00:09:28.419 --> 00:09:31.940 on the right. Then you follow up. Now add section 00:09:31.940 --> 00:09:34.899 two to the artifact, maintaining the same formatting 00:09:34.899 --> 00:09:37.299 style. And it just appends it to the file? Yes. 00:09:37.679 --> 00:09:39.860 It updates the artifact. By doing it in these 00:09:39.860 --> 00:09:43.679 chunks, you force the AI to really pay attention 00:09:43.679 --> 00:09:46.470 to the details of every single section. The guide 00:09:46.470 --> 00:09:48.710 uses the analogy of painting a house. Right. 00:09:48.870 --> 00:09:51.490 It's like asking a painter to do one wall at 00:09:51.490 --> 00:09:53.750 a time perfectly, rather than just standing in 00:09:53.750 --> 00:09:55.450 the middle of the room and throwing paint everywhere. 00:09:55.590 --> 00:09:58.029 That's a vivid image, and probably a lot cleaner. 00:09:58.190 --> 00:10:01.350 Much cleaner. There's also a verification step 00:10:01.350 --> 00:10:04.090 mentioned, the self -correction prompt. I love 00:10:04.090 --> 00:10:06.049 this idea because I usually just trust the AI. 00:10:06.269 --> 00:10:09.710 Which can be a mistake. Always verify. The prompt 00:10:09.710 --> 00:10:12.100 suggested is simple. Please review the text in 00:10:12.100 --> 00:10:14.460 the artifact. Check for formatting errors. Make 00:10:14.460 --> 00:10:16.600 sure all headings are consistent. So you're turning 00:10:16.600 --> 00:10:19.820 it into an editor. Exactly. AI is surprisingly 00:10:19.820 --> 00:10:22.399 good at critiquing its own work if you just ask 00:10:22.399 --> 00:10:24.259 it to. It's like having a second pair of eyes. 00:10:25.179 --> 00:10:28.080 Then, finally, the pace test. The guide says 00:10:28.080 --> 00:10:30.820 a standard control V usually works. Yeah, if 00:10:30.820 --> 00:10:33.620 you've used the artifact prompt correctly, standard 00:10:33.620 --> 00:10:36.320 pace usually works perfectly. But if it still 00:10:36.320 --> 00:10:39.279 looks slightly off... Look for an option in Word 00:10:39.279 --> 00:10:42.440 or Docs called Paste from Markdown. That's the 00:10:42.440 --> 00:10:45.740 backup plan. So what is the primary risk of generating 00:10:45.740 --> 00:10:48.960 a long document in one go? The AI gets tired, 00:10:49.120 --> 00:10:52.659 causing it to drop formatting tags or mix up 00:10:52.659 --> 00:10:55.039 bullet styles near the end. We're going to take 00:10:55.039 --> 00:10:56.960 a quick beat here for a word from our partners. 00:10:57.019 --> 00:10:58.419 When we come back, we're going to talk about 00:10:58.419 --> 00:11:01.200 how to give your document a specific voice using 00:11:01.200 --> 00:11:04.039 style guides and why you might want to ditch 00:11:04.039 --> 00:11:07.240 ChatGPT for this specific type of work. Stay 00:11:07.240 --> 00:11:10.340 with us. Mid -roll sponsor, Reid. Welcome back 00:11:10.340 --> 00:11:12.940 to the Deep Dive. We've covered the why and the 00:11:12.940 --> 00:11:15.120 how of basic formatting, but now I want to get 00:11:15.120 --> 00:11:17.279 a little fancy. The source material talks about 00:11:17.279 --> 00:11:19.740 style guides. Yeah. This isn't just about H1s 00:11:19.740 --> 00:11:21.399 and H2s anymore. This is about the whole vibe 00:11:21.399 --> 00:11:22.940 of the document. This is where you move from 00:11:22.940 --> 00:11:25.659 just being organized to being a real power user. 00:11:25.980 --> 00:11:28.179 You can define the visual voice of the document. 00:11:28.379 --> 00:11:30.019 Give me some examples. What's the difference 00:11:30.019 --> 00:11:32.860 between, say, a corporate style and a creative 00:11:32.860 --> 00:11:36.019 style? Well, if you tell Claude, Use a corporate 00:11:36.019 --> 00:11:38.539 style guide? You're telling it a few things at 00:11:38.539 --> 00:11:42.840 once. Like what? Short paragraphs. Bold key terms 00:11:42.840 --> 00:11:48.879 only. Standard H2 headers. No emojis. It creates 00:11:48.879 --> 00:11:52.899 a very dense, skimmable, professional look. Okay. 00:11:53.100 --> 00:11:55.799 and the creative style. That might include emojis 00:11:55.799 --> 00:11:58.480 in the headers, area formatting with more white 00:11:58.480 --> 00:12:01.000 space, maybe using bullet lists more often just 00:12:01.000 --> 00:12:03.320 to make it feel lighter on the page. I see. So 00:12:03.320 --> 00:12:05.159 you're not just formatting the code, you're formatting 00:12:05.159 --> 00:12:07.460 the entire experience of reading it. Exactly. 00:12:07.629 --> 00:12:09.649 And you can save these prompts. If you have a 00:12:09.649 --> 00:12:11.590 specific way you like your internal memos to 00:12:11.590 --> 00:12:14.129 look, you write that prompt once, save it, and 00:12:14.129 --> 00:12:16.169 just paste it in every single time. That's a 00:12:16.169 --> 00:12:18.629 huge time saver. Now what happens if the AI just 00:12:18.629 --> 00:12:20.450 gets stuck? I've had this happen where it starts 00:12:20.450 --> 00:12:22.730 writing everything in italics. Oh yeah, the formatting 00:12:22.730 --> 00:12:25.269 loop. Or it refuses to stop bolding every other 00:12:25.269 --> 00:12:27.769 word. The best way to break it is the reset command. 00:12:28.009 --> 00:12:30.929 Which is? You literally tell it. Stop. You are 00:12:30.929 --> 00:12:33.769 losing structure. Reset and rewrite the last 00:12:33.769 --> 00:12:36.590 section. Focus strictly on clean document formatting. 00:12:36.789 --> 00:12:39.169 You have to be a bit stern with it. You do. You 00:12:39.169 --> 00:12:41.370 kind of have to snap it out of the hallucination. 00:12:41.669 --> 00:12:43.850 Let's talk tools for a second. We've been focusing 00:12:43.850 --> 00:12:46.009 on Claude because of this artifacts feature, 00:12:46.450 --> 00:12:49.009 but a lot of our listeners probably use ChatGPT 00:12:49.009 --> 00:12:51.629 or Gemini. Right. Can they do this too? The source 00:12:51.629 --> 00:12:53.750 material is pretty clear on this. ChatGPT and 00:12:53.750 --> 00:12:57.340 Gemini are amazing tools. for brainstorming, 00:12:57.620 --> 00:13:00.580 for ideation, for quick Q &A. They're fantastic. 00:13:00.679 --> 00:13:04.039 What? But for document creation, they lag behind. 00:13:04.179 --> 00:13:05.919 Because they don't have that dedicated window. 00:13:06.159 --> 00:13:08.799 That's the main reason. In ChadGPT, the text 00:13:08.799 --> 00:13:10.860 is still mixed in with the chat bubble. It's 00:13:10.860 --> 00:13:13.659 chat text. And when you copy from it, you often 00:13:13.659 --> 00:13:16.440 drag along background colors or font errors. 00:13:16.899 --> 00:13:20.629 It's just messy. And Claude is designed for copy 00:13:20.629 --> 00:13:23.669 ones used immediately. That's the design philosophy. 00:13:23.850 --> 00:13:25.789 The artifact is clean code. It is designed to 00:13:25.789 --> 00:13:28.250 be exported. So when should you choose Claude 00:13:28.250 --> 00:13:30.649 over the others? When you need a final export 00:13:30.649 --> 00:13:33.649 -ready document without any manual cleanup. It 00:13:33.649 --> 00:13:35.669 seems like such a simple distinction, but it 00:13:35.669 --> 00:13:38.309 saves hours in the long run. And the guide points 00:13:38.309 --> 00:13:40.230 out this isn't just for business people writing 00:13:40.230 --> 00:13:43.620 SOPs. No. Absolutely not. Think about students. 00:13:44.179 --> 00:13:46.460 You can dump messy lecture notes into Claude 00:13:46.460 --> 00:13:49.919 and say, create a study guide artifact with bolded 00:13:49.919 --> 00:13:53.100 terms for dates and key people. Or job seekers. 00:13:53.519 --> 00:13:56.759 Yes. Writing a cover letter that actually maintains 00:13:56.759 --> 00:13:59.340 its layout when you paste it into an email or 00:13:59.340 --> 00:14:02.409 a PDF builder. That cover letter example is huge. 00:14:02.789 --> 00:14:04.629 There's nothing worse than pasting a cover letter 00:14:04.629 --> 00:14:06.690 and having the address block formatting just 00:14:06.690 --> 00:14:09.649 explode. That looks so unprofessional. This solves 00:14:09.649 --> 00:14:11.710 that. Okay, let's bring this all home. We've 00:14:11.710 --> 00:14:14.330 covered a lot of ground. What's the big takeaway 00:14:14.330 --> 00:14:16.750 for you here? Because for me, it's not just about 00:14:16.750 --> 00:14:19.470 bold text. No, it's not. For me, the big idea 00:14:19.470 --> 00:14:22.409 is a mindset shift. We need to stop treating 00:14:22.409 --> 00:14:24.950 the AI as a chat buddy. and start treating it 00:14:24.950 --> 00:14:27.590 as a document secretary. I like that distinction. 00:14:27.769 --> 00:14:29.990 A chat buddy is for talking. A secretary is for 00:14:29.990 --> 00:14:33.710 filing. Precisely. If you accept chat text, you're 00:14:33.710 --> 00:14:35.870 accepting mediocrity. You're accepting that you're 00:14:35.870 --> 00:14:37.870 going to have to do the manual labor of formatting. 00:14:38.110 --> 00:14:41.129 But if you demand structure, if you use the artifact 00:14:41.129 --> 00:14:44.149 window and speak the language of H1 and H2 tags, 00:14:44.850 --> 00:14:48.110 you are elevating the AI to a tool that actually 00:14:48.110 --> 00:14:50.419 finishes the job for you. It's about respect 00:14:50.419 --> 00:14:52.980 for your own time, really. It is, yeah. We have 00:14:52.980 --> 00:14:54.720 these incredibly powerful tools. We shouldn't 00:14:54.720 --> 00:14:56.580 be spending our time fixing their margins. So 00:14:56.580 --> 00:14:58.940 let's recap the three main steps to mastering 00:14:58.940 --> 00:15:02.179 this. First, never accept chat text for a final 00:15:02.179 --> 00:15:04.539 document. OK. Second, always use the artifact 00:15:04.539 --> 00:15:06.679 window to isolate the work from the conversation. 00:15:06.820 --> 00:15:09.720 And third? And third, speak the language of structure. 00:15:10.340 --> 00:15:13.600 Ask for specific H1 and H2 tags in your prompt. 00:15:13.860 --> 00:15:16.559 Simple, actionable, and it sounds really effective. 00:15:16.720 --> 00:15:18.690 And it works for everyone. freelancer sending 00:15:18.690 --> 00:15:21.309 deliverables, students making notes, job seekers 00:15:21.309 --> 00:15:24.009 sending CVs. It's a universal productivity hack. 00:15:24.289 --> 00:15:26.529 So here is my challenge to you listening right 00:15:26.529 --> 00:15:29.070 now. Don't just file this away as interesting. 00:15:29.730 --> 00:15:32.710 Open Claude right now. Find an old rough draft 00:15:32.710 --> 00:15:35.490 or a messy email thread or just some notes on 00:15:35.490 --> 00:15:37.870 your phone. And then use the prompt. Yeah. Create 00:15:37.870 --> 00:15:41.029 a standalone document artifact. Use clean formatting 00:15:41.029 --> 00:15:44.529 with H1 and H2 tags. See the difference for yourself. 00:15:44.879 --> 00:15:47.379 Watch that second window open up and realize 00:15:47.379 --> 00:15:50.120 how much time you're about to save. It really 00:15:50.120 --> 00:15:52.279 is satisfying to see a perfect document just 00:15:52.279 --> 00:15:55.019 appear, completely ready to go. Fixing messy 00:15:55.019 --> 00:15:57.720 text doesn't have to be a daily struggle if you 00:15:57.720 --> 00:16:00.299 use the right tool for the job. Thanks for diving 00:16:00.299 --> 00:16:02.340 in with us today. Always a pleasure to clear 00:16:02.340 --> 00:16:04.500 up the chaos. We'll catch you on the next deep 00:16:04.500 --> 00:16:04.759 dive.