0:00 If you removed the logo and brand name, would you recognize the website Claude Code just built? 0:05 Honestly, probably not. It usually looks exactly like everything else. Welcome to the Deep Dive. 0:10 We're unpacking a highly specific, fascinating workflow today. Yeah, a four -step workflow, actually. Right. We're looking at how to build websites using Claude Code that actually reflect your personal style. Exactly, because the mission 0:22 here is avoiding that generic AI aesthetic. We really want to put you firmly in the director's chair. You know the look I'm talking about. Those bland, perfectly symmetrical pages. They just feel kind of totally soulless. And I have to 0:36 make a confession right here. I still wrestle with generic AI designs myself. Oh, I mean, we completely get it. It's the path of least resistance. 0:44 Right. It really is. It's so easy to just let the prompt take over. You just type a sentence, and boom, you have a website. But the results are rarely something you're actually proud of. 0:55 That's exactly why we're tracing this complete journey today. We're moving from scattered inspiration to a fully custom interactive website. And it requires shifting how you interact with the AI. 1:06 You stop being a passive user, you become an art director. To avoid that generic AI aesthetic, you can't just ask Claude for a website. You have to feed it a visual diet first. The source material calls this building a taste fault. I 1:19 love that concept. It sounds like a secure facility for your creativity. It's essentially a curated design reference library. Before you even touch a line of code, you need inspiration. You have to actively show Claude code the designs that 1:32 resonate with you. Because the AI can't read your mind, it doesn't know what you think is beautiful. It desperately needs a baseline for your visual taste. The guide recommends hunting for this inspiration across four main platforms. 1:43 First up is Pinterest. This is where you go for the broad strokes. Yeah, Pinterest is fantastic for the overall mood. You aren't really looking for code there. You're looking at overarching layouts. You're absorbing general visual styles 1:57 and striking color palettes. Exactly. It's kind of the vibe check. Next is Dribbble. This is where things get much more specific. Dribbble is the hub for polished UI designs. It's heavily focused on digital interfaces. You can find incredible 2:13 landing page concepts there. The details are usually really sharp. Then we have X. You could follow web designers directly on your feed. The design community there is relentlessly active. 2:23 It's essentially a real time stream of cutting edge ideas. You get to see what people are experimenting with today, not what was popular like two years ago. And finally, a platform called 21st .dev. 2:35 This one is highly targeted. It is. It's a bit more technical. You use it to find very specific UI components. Think clever animated buttons or unique card layouts. So. You're browsing these platforms. You're finding designs that catch 2:50 your eye. What's the actual workflow? You just take a screenshot? Mm -hmm. You grab a screenshot of everything you like. And you drop all those images into one specific folder on your computer. 3:01 You're hoarding styles, layouts, and colors. 3:03 It's a massive collection of visual data. But a folder full of raw image files is incredibly messy. It's chaotic to look through. It's a nightmare to navigate manually. But this is exactly where the AI magic starts. You open Cloud Code. You 3:20 point it at that chaotic folder of screenshots. 3:22 And you give it a very specific prompt. You ask it to turn those raw images into your taste fault. 3:29 You're commanding the AI to analyze the images. 3:31 But it goes beyond just looking at them. It studies the visual style and the overall mood. It analyzes the typography choices. It breaks down the color palettes and the specific UI components. Right. 3:43 And then it actually builds a custom tool for you. That's the part that blew my mind. It builds a simple functional web app, a local app, where you can browse and organize your references. 3:54 It takes your messy folder and structures it. 3:57 It groups similar designs together automatically. 3:59 It creates a clean interface to preview everything you've saved. It's kind of like stacking Lego blocks of data for the AI. You're building a structured visual database. It's entirely different from a traditional mood board. It's way more 4:12 powerful. You can filter your references by dark mode or light mode. You can sort by color. You can keep feeding it new screenshots over time. 4:22 Why build a whole web app just to look at screenshots instead of just dumping them in a folder? Because a folder is totally static. Building the Taste Vault app automatically tags your screenshots by visual style. It categorizes your inspiration. 4:36 That makes your entire design library instantly searchable for any future project. Got it. So it turns a messy folder into a searchable design database. Exactly. It makes your inspiration completely functional. But having a visual library 4:49 is mostly just great for us, right? Yeah. It helps humans see the big picture. To get the AI to actually build a website, we have to translate those images into rules. And that requires setting up the right parameters. We have to teach the 5:03 AI how to interpret your taste. We need Claude Code to deeply study that taste vault. It has to understand the DNA of your preferred visual style. So you open your working project in Claude Code and you send it a highly detailed, very specific prompt. You tell Claude to act as a 5:23 senior web designer. You explicitly cast it in the role of a front -end design director. I highly recommend this roleplay tactic. It severely focuses the AI's output. It forces it to adopt a professional analytical lens. You command it to deeply analyze 5:41 the Taste Vault folder. You want it to turn all those screenshots into a reusable design system. 5:47 The visual analysis required here is intense. 5:50 You instruct Claude to inspect every single pixel carefully. It cannot just skim the file names. 5:56 It has to look at the overall page layout. It analyzes the content structure and font hierarchy. 6:02 It looks at how text is sized and spaced. It even estimates the exact hex values for your favorite colors. And a hex value is just a six -character code used to identify a specific color. 6:13 Right. It notes the spacing. It looks at the alignment of buttons and cards. It identifies the unique navigation styles that keep popping up. But I'm going to push back here for a second. 6:23 How does Claude actually know what makes a design good? How does it truly see design rather than just mindlessly copying a screenshot? That is a phenomenal question. The AI doesn't have taste in the human sense. It doesn't feel emotion when 6:38 it sees a nice font. But it is an absolute monster at pattern recognition. The prompt specifically trains it to identify recurring design patterns. 6:48 Ah, so it's constantly looking for repetition across your images. Precisely. It cross references all your screenshots. It looks for the colors and typography styles you consistently save. 6:59 It actively separates recurring themes from random one -off details? Yes. The prompt tells it not to use every single element everywhere. It's mathematically extracting the underlying rules of your aesthetic. It's definitely not just making 7:13 a cheap photocopy of an image. The final output of this intense analysis is a specific document. 7:20 It generates a file called design -reference .md. It's a markdown file. It's just a simple text format used for organizing information clearly. 7:30 This text file becomes your master rulebook. 7:33 It permanently records your visual direction. 7:35 It locks in your preferred color palettes and typography pairings. It aligns your layout principles. 7:40 It even includes a list of design elements to actively avoid. That negative constraint is incredibly useful. And you have to set strict boundaries for this step. Claude must analyze the images before writing a single word. It absolutely must 7:56 keep your original screenshots untouched. And crucially, it must not build the website yet. 8:02 That is the golden rule here. Just write the report. Do not write any code for the actual site. What happens if the AI hallucinates design details that aren't actually in my screenshots? 8:12 That's a huge risk with large language models, but this prompt specifically forbids the AI from inventing details. It strictly commands cloud code to only report on the visual evidence it actually finds in the images. So the prompt strictly 8:25 locks the AI into only using what it actually sees. Exactly. It completely anchors the AI to your actual taste. Now that we have a mathematical rulebook for your aesthetic, things get really exciting. Yeah. It's finally time to generate 8:40 some actual designs. But we aren't just asking for one generic draft. We are setting the visual direction through options. You have your organized taste vault. You have your master design reference file. Now you decide how the final product should 8:55 look. Most people fail right here. They just ask the AI to build the landing page immediately. 9:01 Right. And that's a massive mistake. You're backing yourself into a corner. Instead, you ask Claude to create three completely different design concepts. 9:10 It gives you the power to compare styles before you commit to one. Let's use the fictional app from the source text to picture this. The app is called 14. It's a platform to help people discover free, legal, dispersed camping spots. 9:21 Sounds incredibly useful for road trips. You open your project in Claude code, you explain the core function of the app, and then you command it to explore three distinct visual directions. 9:31 You explicitly remind it to review your taste fault. You force it to read that design dash reference file first. It has to ground its ideas in your established rules. Then it generates three completely separate landing page concepts. 9:45 Each concept must carry its own unique mood. 9:48 They need different typography scales, different color palettes, different hero sections. The prompt is ruthless here. It says make these three concepts look clearly and obviously different. 9:57 Right. You can't just change a background color and call it a new concept. It needs original layouts that fit the outdoor camping experience. 10:05 It really feels like having three different ad agencies pitching you ideas at the same time. 10:09 That's the perfect analogy. You're the demanding client. The AI is the eager design agency. The source text gives us three fantastic examples of these concepts. Concept A is titled Field Guide. This one leans into a calm, natural aesthetic. 10:24 It uses earthy greens and browns. The layout is very clean and structured. Concept B is called Nightmap. This one shifts entirely. It's a dark, bold, highly technical design. It uses striking neon orange accents. It heavily highlights the 10:41 actual map interface of the app. And finally, Concept C is Desert Postcard. This concept is completely different again. It's a warm, playful, inviting style. It uses soft colors that give off a vintage travel vibe. And these aren't just 10:56 static images. Each concept comes as a fully working page. You can click around. You can switch between desktop, full page, and mobile phone views. You get to see exactly how the design responds to different screens immediately. So 11:09 you take your time. You review the three pitches. 11:12 You evaluate the typography, the spacing, and the vibe. You can even cherry pick your favorite parts from different concepts to merge later. 11:19 If I like field guide, but the layout isn't quite right, do I just start tweaking the code? Nope, you stay completely away from the code. You simply write another prompt. You ask Claude to generate three fresh variations based purely on that field 11:33 guide aesthetic. It builds new layouts while keeping that exact earthy vibe you liked. Ah, so you branch out again before ever touching a single line of code. Exactly. You're iterating on the creative concept, not debugging syntax. 11:48 So we've successfully picked our favorite concept, but constantly writing new prompts just to change a font size is... Utterly exhausting. It totally drains your energy. It really does. There's a much better way to handle the fine tuning. We're 12:00 going to get into that right after this quick break. Sponsor. Welcome back. We're deep diving into a custom workflow for AI web design today. 12:08 We just locked in our visual direction using the 14 camping app as our guide. We picked our favorite design concept. Now it's time for the micro adjustments. This brings us to the final major shift in the process. Building a custom adjustment panel. Normally, if you're using AI 12:23 and you want to change a button color, what do you do? You write another prompt. You tell Claude, please make the header font slightly larger and bolder. And that gets old so fast. Testing five different shades of green through text prompts 12:34 is maddening. It's called prompt fatigue. It completely destroys your creative momentum. So we bypass that entirely. We fix this by having Claude build a custom adjustment. panel. We tell it to inject this panel directly onto the right 12:48 side of your live website. It's a brilliant tactical move. Instead of writing endless prompts, you get physical sliders and toggles. You tweak the design visually and watch it update instantly. 12:59 You send a prompt asking Claude to construct this overlay panel. You demand control over as many visual variables as mathematically possible. 13:08 The sheer amount of control it gives you is staggering. 13:11 Let's break down what's actually on this panel. 13:14 First up is colors. You get smooth sliders for your main palettes, background colors, text colors. 13:19 You can dynamically adjust the hue and color intensity on the fly. Next is the typography section. You get simple drop -down menus for font families and text pairings. You can drag a slider to change the heading size. You adjust font weights. You tweak line height and letter 13:34 spacing instantly. Then you have layout and spacing controls. You can easily widen the content area. 13:40 You adjust the padding between sections. You tweak how the hero image aligns with the text. 13:46 It even generates controls for visual effects. 13:48 This is where it gets really playful. You can toggle background textures on or off. You drag a slider to change the border radius. You can deepen the drop shadows or make them softer. 13:57 It adds specific sliders for your images, too. 14:00 You can scale, rotate, or slightly tilt illustrations. 14:03 And finally, animations. You control how fast things move on the screen. You adjust hover effects and scroll animations. You essentially get a mixing board for motion intensity. Whoa. Imagine adjusting the whole site's mood with one slider. 14:19 You can change the CSS instantly without rewriting a single prompt. It's totally wild. And CSS variables are the underlying tech that makes this possible. 14:28 Dynamic design labels that let you instantly change styles across your site. Yeah, it happens in absolute real time in your browser. The panel also includes a few crucial utility buttons. 14:38 There's a surprise me button. You click it and it scrambles the variables to give you a totally random design combination. That's perfect for discovering happy accidents you wouldn't have thought of. There are preset buttons to switch between your overarching styles and there's a 14:51 vital reset button to instantly restore the original design if you mess up. Plus it gives you a way to save your exact settings once it looks perfect. 14:59 This step fundamentally changes your relationship with the software. It totally shifts your role. 15:04 You go from struggling as a coder to operating as an art director. You're just pulling levers and making high -level aesthetic choices. Does adding this complex panel risk breaking the beautiful landing page Claude just built? It absolutely 15:16 could destroy the layout without strict guardrails, but the prompt explicitly protects the site structure. 15:22 It commands Claude not to remove or break any existing sections. It uses those CSS variables to safely sandbox all your visual changes. So it overlays the controls safely without destroying the foundation underneath. Exactly. The panel floats safely on top of your hard work. It's 15:38 just a remarkably elegant workflow. It really is. Let's zoom out for a second and look at the bigger picture here. The core philosophy driving this whole deep dive. AI web design offers us unprecedented creative leverage right now. The Claude code is more than capable of handling 15:54 all the heavy lifting. It writes the syntax flawlessly. 15:57 It builds the structure. But the final aesthetic completely depends on the visual direction you enforce. If you give it nothing, it spits out generic, soulless slop. But if you take the time to build a taste vault, it gives you a masterpiece. 16:11 Supplying genuine, curated personal taste is the only defense against generic AI design. You have to do the human work of curation first. 16:19 The AI doesn't feel what looks good. It only analyzes the visual patterns you feed it. You start by hunting down designs that actually move you. You feed the AI those precise references. 16:30 You force it to explore varied concepts. And then you build a custom panel to physically tune the page until it feels right. That is the secret to creating an AI website that actually feels uniquely human. It requires your intuition at 16:44 the very beginning to gather the inspiration. 16:46 And it requires your intuition at the very end to slide the dials. The AI just executes the tedious middle part. For now at least. Right. 16:54 And that brings up a really profound point to close on. We just spent this entire deep dive learning how to build a custom adjustment panel. 17:02 We built it to make our human jobs easier today. 17:04 We built it to help us art direct the AI. But if AI can build its own custom adjustment panel to make web design easier for you today, how long until it realizes it doesn't need the panel or us to decide what looks beautiful? That's a wild thought. Something to mull over until 17:20 next time. Thank you so much for taking this deep dive with us.
Community discussion