WEBVTT

00:00:00.000 --> 00:00:02.899
Picture this incredibly familiar and totally

00:00:02.899 --> 00:00:06.280
frustrating scenario. You spend two hours dragging

00:00:06.280 --> 00:00:09.019
boxes around a blank canvas template. You carefully

00:00:09.019 --> 00:00:11.660
tweak every single little detail on the screen.

00:00:12.640 --> 00:00:15.380
But the final Instagram carousel still looks

00:00:15.380 --> 00:00:18.199
completely average. It really is the ultimate

00:00:18.199 --> 00:00:20.500
creator bottleneck. Yeah, that happens way too

00:00:20.500 --> 00:00:22.679
often. It completely drains your creative energy

00:00:22.679 --> 00:00:25.440
right from the start. But today we are unpacking

00:00:25.440 --> 00:00:28.640
a really radical new workflow. We are using Claude

00:00:28.640 --> 00:00:32.060
AI to build vector -sharp, pixel -perfect Instagram

00:00:32.060 --> 00:00:34.579
carousels. It is going to totally change how

00:00:34.579 --> 00:00:36.859
you approach design. And the shift in thinking

00:00:36.859 --> 00:00:39.200
here is pretty massive. We aren't asking the

00:00:39.200 --> 00:00:41.500
AI to draw images for us. We are actually asking

00:00:41.500 --> 00:00:43.820
it to write code instead. That is the fundamental

00:00:43.820 --> 00:00:46.340
difference for this entire deep dive. Exactly.

00:00:46.700 --> 00:00:48.460
We are trading the frustration of traditional

00:00:48.460 --> 00:00:51.020
design tools for something much better. Standard

00:00:51.020 --> 00:00:53.159
image generators have some really inherent flaws.

00:00:53.420 --> 00:00:56.500
We are bypassing those entirely with this completely

00:00:56.500 --> 00:00:59.119
new method. Right. Because I still wrestle with

00:00:59.119 --> 00:01:01.320
prompt drift myself when trying to get mid -journey

00:01:01.320 --> 00:01:03.840
to spell a simple word. It feels like pulling

00:01:03.840 --> 00:01:07.060
teeth sometimes. Why do tools like mid -journey

00:01:07.060 --> 00:01:10.659
or Deloitte fail so spectacularly for content

00:01:10.659 --> 00:01:13.000
creators? Well, it comes down to how those models

00:01:13.000 --> 00:01:15.659
actually think. They weren't really built for

00:01:15.659 --> 00:01:19.560
typography at all. They generate images by predicting

00:01:20.079 --> 00:01:23.159
pixel noise. They don't actually understand letters

00:01:23.159 --> 00:01:25.340
or alphabet structures. Mm -hmm. They just know

00:01:25.340 --> 00:01:27.219
what a shape generally looks like. Right. And

00:01:27.219 --> 00:01:30.959
because of that, image AI inevitably produces

00:01:30.959 --> 00:01:33.900
distorted text. You get these weird melted letters

00:01:33.900 --> 00:01:35.959
on your screen. And when you expert the file,

00:01:36.079 --> 00:01:38.359
the whole thing is completely blurry. It just

00:01:38.359 --> 00:01:41.040
lacks that crisp professional edge. I have seen

00:01:41.040 --> 00:01:43.579
that happen so many times. And the most agonizing

00:01:43.579 --> 00:01:46.439
part is the revision process. If you spot a typo,

00:01:46.719 --> 00:01:49.260
Every single correction requires regenerating

00:01:49.260 --> 00:01:51.719
the whole image. You basically roll the dice

00:01:51.719 --> 00:01:53.459
again. Yeah, and you lose all your creative momentum

00:01:53.459 --> 00:01:55.439
instantly. It becomes a total guessing game.

00:01:55.760 --> 00:01:57.680
You fix a typo, and suddenly the background color

00:01:57.680 --> 00:02:00.180
completely changes. It is maddening. But Claude

00:02:00.180 --> 00:02:02.219
approaches this very differently. Because it

00:02:02.219 --> 00:02:05.519
uses HTML and CSS code instead of pixels. Exactly.

00:02:05.599 --> 00:02:08.300
It builds each slide as a real -time mini web

00:02:08.300 --> 00:02:10.879
page. It is writing the structural language of

00:02:10.879 --> 00:02:13.819
the internet. That is a massive difference in

00:02:13.819 --> 00:02:16.770
workflow. Using Claude is kind of like stacking

00:02:16.770 --> 00:02:20.750
Lego blocks of data. You are not painting with

00:02:20.750 --> 00:02:24.699
unpredictable watercolors. And you see all this

00:02:24.699 --> 00:02:26.819
happening inside the artifacts window, right?

00:02:27.259 --> 00:02:29.300
For anyone unfamiliar, we should clarify what

00:02:29.300 --> 00:02:31.860
that is. It is a built -in screen showing live

00:02:31.860 --> 00:02:34.360
code as working mini apps. Yeah, the artifacts

00:02:34.360 --> 00:02:36.520
window is a total game changer. It makes this

00:02:36.520 --> 00:02:39.520
entire process super accessible. You see the

00:02:39.520 --> 00:02:41.979
raw code turn into a visual slide instantly.

00:02:42.599 --> 00:02:44.120
And the best part is you don't even need to know

00:02:44.120 --> 00:02:46.300
how to read the code yourself. How does this

00:02:46.300 --> 00:02:48.539
code approach change the editing process when

00:02:48.539 --> 00:02:51.460
you inevitably make a typo? You literally just

00:02:51.460 --> 00:02:53.620
change the texturing itself. The code updates

00:02:53.620 --> 00:02:55.800
instantly without destroying the rest of the

00:02:55.800 --> 00:02:58.199
design. You do not regenerate anything at all.

00:02:58.340 --> 00:03:00.360
So you tweak the code, not the entire image.

00:03:00.439 --> 00:03:03.400
Got it. Exactly. But obviously, having a functional

00:03:03.400 --> 00:03:05.199
coding environment doesn't automatically mean

00:03:05.199 --> 00:03:07.520
you have a good eye for aesthetics. We need to

00:03:07.520 --> 00:03:09.319
figure out the actual design. Which brings us

00:03:09.319 --> 00:03:11.620
to the psychology of what actually makes someone

00:03:11.620 --> 00:03:14.430
stop scrolling. Moving from understanding the

00:03:14.430 --> 00:03:17.389
tech to creating a specific visual style feels

00:03:17.389 --> 00:03:20.490
daunting, but you really don't need a design

00:03:20.490 --> 00:03:23.150
degree for this process. Not at all. You start

00:03:23.150 --> 00:03:25.430
by finding scroll -stopping Instagram carousels

00:03:25.430 --> 00:03:27.770
on your phone. You just screenshot four to six

00:03:27.770 --> 00:03:30.229
of them. You are basically building a mood board

00:03:30.229 --> 00:03:33.550
of proven winners. When we are hunting for these

00:03:33.550 --> 00:03:36.050
references, what exactly are we looking for?

00:03:36.129 --> 00:03:39.050
Because the AI needs really solid reference material

00:03:39.050 --> 00:03:43.460
to understand what works. Look for soft backgrounds

00:03:43.460 --> 00:03:45.819
that let the text breeze. That negative space

00:03:45.819 --> 00:03:48.759
is really crucial for readability. Look for bold

00:03:48.759 --> 00:03:50.699
headlines that immediately grab your attention.

00:03:51.560 --> 00:03:53.520
And pay close attention to the intentional spacing

00:03:53.520 --> 00:03:55.860
between elements. Then you upload these screenshots

00:03:55.860 --> 00:03:58.370
directly to Claude. And here is where the prompt

00:03:58.370 --> 00:04:00.490
engineering becomes really fascinating. What

00:04:00.490 --> 00:04:03.150
exactly are we asking the AI to do with these

00:04:03.150 --> 00:04:05.729
images? You ask it to act like a master graphic

00:04:05.729 --> 00:04:08.770
design expert. You ask it to extract the specific

00:04:08.770 --> 00:04:11.849
layout math from the images. We want the hex

00:04:11.849 --> 00:04:14.469
colors, the Google fonts, the exact padding and

00:04:14.469 --> 00:04:17.029
margins. We basically want the underlying structure.

00:04:17.269 --> 00:04:18.889
Wait, I need to push back on this a little bit.

00:04:19.009 --> 00:04:21.569
Is this just plagiarism? Are we essentially stealing

00:04:21.569 --> 00:04:23.730
someone else's hard work and slapping our name

00:04:23.730 --> 00:04:26.509
on it? That is a very fair question. And it is

00:04:26.509 --> 00:04:28.910
an important ethical boundary. But no, it is

00:04:28.910 --> 00:04:31.129
definitely not plagiarism. We are completely

00:04:31.129 --> 00:04:33.689
ignoring their text and their specific content.

00:04:34.089 --> 00:04:36.290
We're only extracting the mathematical layout

00:04:36.290 --> 00:04:39.290
rules. We call this the design DNA. OK, that

00:04:39.290 --> 00:04:42.009
makes sense. There is a fine line between stealing

00:04:42.009 --> 00:04:44.600
someone's soul and borrowing their math. We're

00:04:44.600 --> 00:04:47.540
just looking at the scaffolding. And then Claude

00:04:47.540 --> 00:04:50.079
outputs this structural data as a JSON format.

00:04:50.319 --> 00:04:53.339
Let us define that quickly. It is a simple text

00:04:53.339 --> 00:04:56.160
file organizing data into readable lists. Right.

00:04:56.180 --> 00:04:58.100
And it includes things like your exact brand

00:04:58.100 --> 00:05:00.579
colors. It is perfectly organized for the AI

00:05:00.579 --> 00:05:02.680
to read. It strips away all the visual noise

00:05:02.680 --> 00:05:05.079
and leaves pure data. We should probably define

00:05:05.079 --> 00:05:07.800
hex colors too. There are six symbol codes for

00:05:07.800 --> 00:05:10.920
exact brand colors. Exactly. Things like hashtag

00:05:10.920 --> 00:05:15.019
FFFFF for pure white. It guarantees perfect color

00:05:15.019 --> 00:05:17.360
matching every single time you generate a slide.

00:05:17.980 --> 00:05:20.500
It completely removes human error from the branding

00:05:20.500 --> 00:05:23.779
process. Once I have this JSON file, do I have

00:05:23.779 --> 00:05:26.399
to keep pasting it in every time I open the app?

00:05:26.639 --> 00:05:29.459
You could, but there is a much better way. There

00:05:29.459 --> 00:05:32.079
is a specific feature that permanently memorizes

00:05:32.079 --> 00:05:34.839
these rules for you instead. So the JSON becomes

00:05:34.839 --> 00:05:38.000
a reusable recipe for the AI. Makes sense. It

00:05:38.000 --> 00:05:40.560
really is a recipe. And now we need to talk about

00:05:40.560 --> 00:05:43.560
locking in that extracted design DNA. Because

00:05:43.560 --> 00:05:45.899
having the recipe is great, but we want every

00:05:45.899 --> 00:05:48.360
future post to be perfectly on brand without

00:05:48.360 --> 00:05:50.600
starting over. Right. So we have essentially

00:05:50.600 --> 00:05:52.620
captured the mathematical essence of a great

00:05:52.620 --> 00:05:55.160
design. This is where Claude's projects feature

00:05:55.160 --> 00:05:58.259
comes into play. You treat a project like onboarding

00:05:58.259 --> 00:06:00.420
a human design assistant. Yeah, that is the perfect

00:06:00.420 --> 00:06:02.860
way to look at it. You just paste your JSON recipe

00:06:02.860 --> 00:06:05.259
into the project's custom instructions. This

00:06:05.259 --> 00:06:07.120
sets the permanent foundation. for everything

00:06:07.120 --> 00:06:10.220
you build moving forward. The AI will constantly

00:06:10.220 --> 00:06:12.540
reference this exact document. The secret here

00:06:12.540 --> 00:06:14.939
is establishing those ground rules right in the

00:06:14.939 --> 00:06:17.339
custom instructions. You tell it to make every

00:06:17.339 --> 00:06:20.600
single slide 1080 by 1080 pixels. Right. You

00:06:20.600 --> 00:06:23.339
lock in the exact aspect ratio. You can also

00:06:23.339 --> 00:06:25.319
add structural elements like a small progress

00:06:25.319 --> 00:06:27.759
bar at the bottom of each slide. You mandate

00:06:27.759 --> 00:06:30.519
those exact hex codes from your JSON file. You

00:06:30.519 --> 00:06:33.139
also require a mandatory call to action on the

00:06:33.139 --> 00:06:36.410
final slide. Something like save this post or

00:06:36.410 --> 00:06:39.589
follow for more it forces the AI to remember

00:06:39.589 --> 00:06:42.389
the overall marketing objective Yeah, you establish

00:06:42.389 --> 00:06:45.029
these strict rules once then you literally never

00:06:45.029 --> 00:06:47.189
have to think about them again It handles the

00:06:47.189 --> 00:06:49.850
formatting totally automatically to sex silence.

00:06:49.949 --> 00:06:54.120
Whoa Imagine scaling to a billion queries and

00:06:54.120 --> 00:06:56.939
every single one perfectly matches your brand's

00:06:56.939 --> 00:06:59.319
exact shade of blue. It is incredibly powerful.

00:06:59.540 --> 00:07:01.459
You do not ever have to fix the branding again.

00:07:01.740 --> 00:07:03.579
The system just inherently knows what to do.

00:07:03.959 --> 00:07:06.019
It frees up so much cognitive bandwidth for the

00:07:06.019 --> 00:07:07.980
actual content. What if I run an agency with

00:07:07.980 --> 00:07:09.759
five different clients who all have different

00:07:09.759 --> 00:07:11.980
visual aesthetics? You just create a separate

00:07:11.980 --> 00:07:14.079
project workspace for each client with their

00:07:14.079 --> 00:07:16.600
unique JSON instructions. It takes seconds to

00:07:16.600 --> 00:07:19.430
switch. Distinct workspaces keep client branding

00:07:19.430 --> 00:07:22.050
perfectly separated. Brilliant. It really sells

00:07:22.050 --> 00:07:23.709
a massive headache. So we have our assistant

00:07:23.709 --> 00:07:26.189
build now. Exactly. The scaffolding is rock solid.

00:07:26.629 --> 00:07:29.790
But an empty slide deck does not get views. How

00:07:29.790 --> 00:07:32.290
do we translate messy input into something this

00:07:32.290 --> 00:07:35.189
system can actually use? That is the fun part.

00:07:35.610 --> 00:07:38.220
Your input can literally be anything. a half

00:07:38.220 --> 00:07:41.019
-finished blog post, a rambling voice memo, or

00:07:41.019 --> 00:07:44.160
just simple bullet points. The key is using a

00:07:44.160 --> 00:07:46.920
highly structured prompt to guide the AI. You

00:07:46.920 --> 00:07:49.620
have to ask Claude for a 10 slide outline before

00:07:49.620 --> 00:07:52.779
it writes the code. Yes. That is absolutely crucial.

00:07:52.860 --> 00:07:55.199
If you just ask it to build a carousel, it will

00:07:55.199 --> 00:07:57.579
hallucinate the structure and the code all at

00:07:57.579 --> 00:07:59.920
once. You also need to enforce a strict limit

00:07:59.920 --> 00:08:03.779
of 15 to 25 words per slide. Asking for the outline

00:08:03.779 --> 00:08:06.259
first is like reviewing the architect's blueprints

00:08:06.259 --> 00:08:08.470
before pouring the concrete. It prevents really

00:08:08.470 --> 00:08:10.629
expensive mistakes later. I love that analogy.

00:08:10.930 --> 00:08:13.170
It saves you from burning through your AI usage

00:08:13.170 --> 00:08:15.529
limits. And when you are reviewing that blueprint,

00:08:15.589 --> 00:08:17.750
you want to focus heavily on the very first slide.

00:08:18.209 --> 00:08:20.149
Have Claude generate three different options

00:08:20.149 --> 00:08:22.569
for the hook slide. What kind of hooks are we

00:08:22.569 --> 00:08:24.810
asking for? Because the psychology of that first

00:08:24.810 --> 00:08:27.389
impression is everything. You asked for one based

00:08:27.389 --> 00:08:31.350
on pure curiosity, one promising a highly tangible

00:08:31.350 --> 00:08:34.710
result, and one targeting a deep audience frustration.

00:08:35.519 --> 00:08:39.419
If slide one fails, the rest are invisible. Nobody

00:08:39.419 --> 00:08:42.360
will swipe. And keeping the word count low forces

00:08:42.360 --> 00:08:45.559
the AI to be punchy. It caters to how people

00:08:45.559 --> 00:08:48.240
actually scroll. But what if the generated slides

00:08:48.240 --> 00:08:50.720
look a bit flat in the preview? You just type

00:08:50.720 --> 00:08:53.379
plain English commands to add CSS effects. You

00:08:53.379 --> 00:08:55.559
can ask for text shadows or background color

00:08:55.559 --> 00:08:57.620
gradients to add depth. You literally just ask

00:08:57.620 --> 00:08:59.960
for shadows and gradients. Too easy. It really

00:08:59.960 --> 00:09:02.539
is. But we also need to talk about applying human

00:09:02.539 --> 00:09:05.129
psychology to the AI's layout. because pretty

00:09:05.129 --> 00:09:06.990
code doesn't matter if it doesn't resonate emotionally.

00:09:07.549 --> 00:09:09.769
We need to get this right before we export to

00:09:09.769 --> 00:09:12.169
Instagram. Let us unpack the layout psychology.

00:09:12.529 --> 00:09:15.129
We use the 80 -20 rule for the design. You give

00:09:15.129 --> 00:09:17.370
80 % of the viewer's attention to the main title

00:09:17.370 --> 00:09:19.950
or the primary number. Make it take up one -third

00:09:19.950 --> 00:09:22.590
of the entire slide. We also deeply need to consider

00:09:22.590 --> 00:09:25.710
color psychology. The colors in your JSON file

00:09:25.710 --> 00:09:29.250
dictate the mood. Blue is great for creating

00:09:29.250 --> 00:09:32.149
trust and professionalism. It is absolutely perfect

00:09:32.149 --> 00:09:34.870
for finance or educational content. While red

00:09:34.870 --> 00:09:37.830
or orange creates a visceral feeling of urgency,

00:09:38.509 --> 00:09:41.309
black and white signals luxury minimalism. And

00:09:41.309 --> 00:09:43.990
you must always ensure high text contrast for

00:09:43.990 --> 00:09:46.779
readability. Exactly. If people have to squint,

00:09:46.899 --> 00:09:49.039
they just keep scrolling. Now, for the actual

00:09:49.039 --> 00:09:51.940
export process, because we have code, not a JPEG,

00:09:52.019 --> 00:09:55.620
you open the HTML file in Chrome or Safari, you

00:09:55.620 --> 00:09:58.039
use the browser's capture node feature to save

00:09:58.039 --> 00:10:00.980
high -res PNGs. So to be clear, because we wrote

00:10:00.980 --> 00:10:03.559
code instead of drawing a picture, we are basically

00:10:03.559 --> 00:10:06.360
using Google Chrome as our camera to take a perfect

00:10:06.360 --> 00:10:09.200
high -res snapshot of a mini website. Right,

00:10:09.320 --> 00:10:11.399
and that snapshot is completely flawless. Sometimes

00:10:11.399 --> 00:10:14.159
the download button vanishes due to a weird browser

00:10:14.159 --> 00:10:16.519
bug, though. If that happens, how do we fix it

00:10:16.519 --> 00:10:18.980
without losing the work? You just prompt Claude

00:10:18.980 --> 00:10:21.419
to show slides as separate high -res image blocks.

00:10:21.860 --> 00:10:24.259
It forces the code to render individually. It

00:10:24.259 --> 00:10:27.539
fixes the issue immediately. Neat. I have to

00:10:27.539 --> 00:10:30.259
point something out. Saving code as an image

00:10:30.259 --> 00:10:33.179
by screenshotting a browser node feels like a

00:10:33.179 --> 00:10:36.240
clunky final step. It feels like a temporary

00:10:36.240 --> 00:10:38.139
workaround. It kind of does feel like a hack,

00:10:38.340 --> 00:10:41.259
yeah. But this workaround guarantees absolute

00:10:41.259 --> 00:10:44.019
vector -sharp quality. It totally eliminates

00:10:44.019 --> 00:10:47.019
that fuzzy Canva Blur effect forever. You get

00:10:47.019 --> 00:10:49.200
perfect typography. Once they are downloaded,

00:10:49.299 --> 00:10:51.460
do I just dump all ten images onto Instagram?

00:10:51.659 --> 00:10:54.580
No. You must post them in exact sequential order.

00:10:55.220 --> 00:10:57.919
Then pair them with a highly sincere, deeply

00:10:57.919 --> 00:11:00.889
personal caption to ground the aesthetic. Proper

00:11:00.889 --> 00:11:03.610
sequence and a human caption seal the deal. Got

00:11:03.610 --> 00:11:06.570
it. Exactly. Let us zoom out and compare this

00:11:06.570 --> 00:11:09.169
new method against traditional workflows. Because

00:11:09.169 --> 00:11:11.269
this isn't just a new feature, it is a completely

00:11:11.269 --> 00:11:13.590
new way of working. We really need to define

00:11:13.590 --> 00:11:16.110
the human's ultimate role here. Look at Canva.

00:11:16.409 --> 00:11:19.009
Canva is massively constrained by millions of

00:11:19.009 --> 00:11:21.769
people using the exact same templates. Your brand

00:11:21.769 --> 00:11:24.230
inevitably looks like everyone else's. Cloud

00:11:24.230 --> 00:11:26.669
offers limitless unique layouts instantly. But

00:11:26.669 --> 00:11:28.649
we shouldn't overcomplicate the design itself

00:11:28.649 --> 00:11:31.950
just because we can. Simple, clean posts perform

00:11:31.950 --> 00:11:34.070
much better than chaotic designs with too many

00:11:34.070 --> 00:11:37.769
sparkling effects. Exactly. The tool only executes

00:11:37.769 --> 00:11:40.610
the commands you give it. The profound thinking

00:11:40.610 --> 00:11:43.330
and the unique voice must still come from the

00:11:43.330 --> 00:11:45.330
user. You cannot hand everything over to the

00:11:45.330 --> 00:11:48.110
machine. The AI is the assistant, not the creative

00:11:48.110 --> 00:11:50.850
director. You have to maintain your own personal

00:11:50.850 --> 00:11:53.710
standard of quality. Writing prompts is really

00:11:53.710 --> 00:11:56.950
just clear thinking made visible. If you are

00:11:56.950 --> 00:11:58.929
a sloppy thinker, you will get a sloppy output.

00:11:59.490 --> 00:12:02.370
Mastering a specific tool is temporary, but clear

00:12:02.370 --> 00:12:05.190
communication compounds over time. That is the

00:12:05.190 --> 00:12:07.970
real secret here. The platforms will update,

00:12:08.190 --> 00:12:10.389
the tools will change, but clear thinking never

00:12:10.389 --> 00:12:13.210
goes out of style. It is the ultimate future

00:12:13.210 --> 00:12:16.049
-proof skill. Before I hit publish on an AI -generated

00:12:16.049 --> 00:12:18.769
deck, what is the one ultimate filter I should

00:12:18.769 --> 00:12:21.029
use? Read it back and ask yourself, would I honestly

00:12:21.029 --> 00:12:23.309
stop and read this on my own feed? The ultimate

00:12:23.309 --> 00:12:25.980
test is your own scrolling attention span. That

00:12:25.980 --> 00:12:28.139
is the only metric that really matters. If you

00:12:28.139 --> 00:12:29.980
scroll past it, your audience will scroll past

00:12:29.980 --> 00:12:32.620
it too. Let us slowly recap the core journey

00:12:32.620 --> 00:12:36.139
we took today. We moved from dragging boxes on

00:12:36.139 --> 00:12:38.899
a screen to acting as a creative director. We

00:12:38.899 --> 00:12:40.980
stopped fighting with blurry image generators.

00:12:41.320 --> 00:12:43.299
We completely flipped the script. We started

00:12:43.299 --> 00:12:45.679
using actual code to build our visual assets.

00:12:45.919 --> 00:12:49.179
We extracted design DNA into a mathematical JSON

00:12:49.179 --> 00:12:52.460
format. We locked that DNA into Claude projects

00:12:52.460 --> 00:12:55.230
to build a permanent brand brain. We prompted

00:12:55.230 --> 00:12:59.450
for HTML and CSS mini webpages. By doing all

00:12:59.450 --> 00:13:02.029
of this, we bypass the blurry limitations of

00:13:02.029 --> 00:13:04.110
image generators entirely. I really want you

00:13:04.110 --> 00:13:06.509
to try this today. Take screenshots of three

00:13:06.509 --> 00:13:08.769
carousels you absolutely love. Feed them into

00:13:08.769 --> 00:13:11.230
Claude right now. Extract your very first design

00:13:11.230 --> 00:13:14.049
DNA JSON file. You will be absolutely amazed

00:13:14.049 --> 00:13:16.759
at how well it understands layout. If AI can

00:13:16.759 --> 00:13:19.179
perfectly mimic the aesthetics of top -tier design,

00:13:19.659 --> 00:13:21.620
maybe the only true differentiator left in the

00:13:21.620 --> 00:13:24.559
future of content is the raw, unpolished sincerity

00:13:24.559 --> 00:13:26.639
of your actual ideas. Something to think about.