The argument in one line.
Claude's reasoning capabilities make it dramatically better than rigid node-based automation for maintaining brand consistency across AI-generated illustrations because the model can actually understand intent rather than just execute predefined steps.
Read if. Skip if.
READ IF YOU ARE…
- You've built a week-long n8n automation that produces inconsistent or poor output and want to understand why AI reasoning might solve it faster.
- A solopreneur or small team maintaining repetitive visual or content workflows who needs consistency but lacks design skills and wants a maintainable system.
- You're evaluating Claude Code as a replacement for node-based automation tools and want a real-world case study showing the tradeoffs between the two approaches.
SKIP IF…
- You're already proficient with n8n or Zapier and believe visual consistency is best solved through design templates, not code—this video argues the opposite.
- You need to build workflows that non-technical team members can edit and update without touching code; Claude Code skills require some technical literacy.
- Your brand visual system is already stable and you're looking for optimization tips rather than a complete rethink of your automation architecture.
The full version, fast.
Rigid automation strips reasoning out of AI workflows, while skills preserve it. The video chronicles a week spent building an n8n pipeline for on-brand illustrations—webhooks, switch nodes, conditional logic feeding image APIs—that technically ran but produced output disconnected from the established brand guidelines. The rebuild as a Claude Code skill took thirty minutes: a folder containing a skill.md instruction file, reference documents for the visual world and aesthetic guidelines, sample illustrations, and a Python script calling the Gemini image API. Treat Claude Code itself as the application rather than a tool for building separate apps. Codify brand or process knowledge into reference files the model can reason over, and reserve node-based automation for genuinely deterministic logic.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 01:34
01 · Open + Promise
Brand-identity problem introduced, n8n failure teased, Claude Code skill solution previewed. Failure/fix arc in under 90 seconds.
01:34 – 03:16
02 · The Final Output
Screen tour of buildermethods.com showing finished illustrations. Shows destination before the journey — strong structural choice.
03:16 – 09:45
03 · Brand Identity Process with Claude
Long Claude.ai conversation used as thought partner. Three artifacts: Visual World doc, Idea-to-Illustration Mapping Guide, Illustration Aesthetic Guidelines. Dribbble research and Google Gemini prototyping for style exploration.
09:45 – 17:22
04 · The n8n Workflow
Full walkthrough of Slack webhook -> switch -> AI image gen -> Google Drive -> Slack pipeline. Technically worked but output was off-brand. Core diagnosis: discrete nodes strip model reasoning ability.
17:22 – 19:48
05 · Why Claude Code Skills Win
Defines a skill as a self-contained mini system. Explains the image generation bridge: Claude Opus reasons, Gemini generates pixels via Python script inside the skill.
19:48 – 22:20
06 · The Skill Structure
Screen walkthrough of brand-illustrator skill folder: skill.md, visual world docs, aesthetic guidelines, mapping guide, brand colors, sample illustrations, Python script. Notes Claude Code v2.1.2 direct invocation as key new feature.
22:20 – 25:13
07 · Live Demo
Invokes /brand-illustrator, requests hero image for systems mindset blog post, receives three concept pitches, selects Blueprint Stack, watches Gemini generate the image live. Shows previous iteration takes.
25:13 – 26:30
08 · Lesson + CTA
Core thesis: rigid automation removes AI reasoning; skills preserve it. Design OS plug and subscribe CTA.
Lines worth screenshotting.
- One week of n8n automation work was scrapped and rebuilt as a Claude Code skill in 30 minutes that produced higher-quality output — rigid pipelines cannot match model reasoning.
- n8n workflows break on edge cases because they follow predetermined paths; Claude Code skills reason through each generation and adapt to whatever the current input requires.
- Building a visual brand identity requires defining a world, not just a color palette — the day-in-the-life of a builder concept gives the AI consistent recurring objects to place.
- Using Claude as a thought partner across a long project conversation — stored in a project with full memory — is more effective than a single prompt because context accumulates.
- A Claude skill that maintains brand visual guidelines is effectively a repeatable system for generating any illustration in a consistent style without rewriting complex prompts.
- The visual world concept — a set of constant objects like a home studio, notebook, and mug — creates a recognizable brand identity that compounds with every new piece of content.
- Codifying a visual brand into a guidelines document that Claude can reference turns one-off image generation into a production pipeline with a consistent output.
- Over-engineering a simple problem is a forcing function — the n8n failure revealed that the real requirement was reasoning about style, not conditional logic across nodes.
- Claude Code skills are the most underrated feature for turning AI into repeatable business workflows because they package a reasoning process, not just a static prompt.
- Workflow automation tools like n8n are optimized for deterministic processes; creative tasks with aesthetic judgment should route through model-native reasoning instead.
- Spending time developing the brand concept before touching any technical workflow determines the quality ceiling of all subsequent AI-generated visuals.
- Saving all brand-related conversations inside a Claude project with dedicated memory means every future visual decision benefits from the full history of previous decisions.
Steal the framework, not the workflow.
Builder playbook
Rigid automation removes AI reasoning — skills preserve it, and for contextual work that gap is everything.
- If a task requires judgment, context, or creative interpretation, a Claude Code skill will outperform an n8n/Zapier pipeline every time.
- Separate brand definition into three layers: Visual World (subject matter), Mapping Guide (decision logic), Aesthetic Guidelines (style spec). Claude can co-author all three as a thought partner before you touch any tooling.
- The skill-as-folder pattern (skill.md + reference docs + script) is worth copying for any repeatable workflow, not just image generation.
- Claude Opus for reasoning + external API for generation (images, audio, video) is a composable pattern that scales to almost any creative automation.
- The 30-minute rebuild vs. 1-week waste framing is a story worth telling on your own channel. Audiences respond to honest failure arcs more than polished tutorials.
- Direct skill invocation via /skill-name in Claude Code v2.1.2+ means skills are now first-class tools. Build yours accordingly.
Terms worth knowing.
- n8n
- An open-source workflow automation platform that connects apps and services using a visual node-based editor, similar to Zapier but self-hostable.
- webhook
- An HTTP callback that allows one service to send real-time data to another when a specific event occurs, commonly used to trigger automation workflows.
- conditional logic node
- A node in a workflow automation tool that routes data down different paths based on whether specified conditions are true or false.
- Claude Code skill
- A reusable, self-contained script or module that extends Claude Code's capabilities to perform a specific automated task via the command line.
- Gemini API
- Google's API for accessing its Gemini family of AI models, including multimodal and image generation capabilities.
- Imagen
- Google's AI image generation model, accessible via the Gemini API, capable of producing high-quality images from text prompts.
- visual brand identity
- The cohesive set of visual elements — colors, typography, illustration style, and imagery — that consistently represent a brand across all media.
- illustration aesthetic guidelines
- A documented set of rules defining the artistic style, color palette, subject matter, and composition standards for a brand's custom illustrations.
- Dribbble
- A design community and portfolio platform where designers share work samples, often used as inspiration or reference for visual style research.
- Design OS
- A personal or brand operating system for design decisions, capturing style rules, component libraries, and aesthetic guidelines in a structured format.
- Python script
- A program written in the Python programming language, used here to call the Gemini API and handle image generation within a Claude Code skill.
Things they pointed at.
26:06productDesign OS
Lines you could clip.
25:35
“By breaking everything into discrete nodes and rigid logic, I stripped away the intelligence that makes AI actually useful. The model couldn't think. It could only execute my predefined steps.”
01:06
“I scrapped the whole thing, that whole week of work, gone. But then, I rebuilt it as a Claude code skill and it only took thirty minutes.”
26:01
“Claude code itself became the application.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogystory
00:00I've always wanted my brand to have a strong visual presence when anyone comes across my content or my website or my products. You know, like the vibe that you get when you walk through the storefront of a shop in your neighborhood. But my writing and my videos can only do so much to set that tone and so I've always tried to create strong visuals to complete the experience.
00:18The problem is I'm not an illustrator and I don't need just one great image. I need dozens and I want them all to follow the same visual aesthetic for every page, every piece of content that I publish.
00:30Well, it's 2026 now, so you would think that AI image generation would make this easy. And the models have gotten really good at creating one off images. But what I need is a repeatable system.
00:40Something that can maintain my brand aesthetic without recrafting these complex prompts every single time I need to generate a visual. So I spent the past week and some late nights trying to solve this.
00:53I created this complex automation workflow using n eight n. You know, nodes connected to nodes, API calls, conditional logic everywhere. And when I finally got it all hooked up, the output was garbage.
01:06I scrapped the whole thing, that whole week of work, gone. But then, I rebuilt it as a Claude code skill and it only took thirty minutes. And I didn't just rebuild it, I made it better.
01:16Higher quality output and it's way easier to maintain. So today, I'll tell you or I'll show you the story of how I over engineered what seems like a simple problem and it's a reminder that Claude code skills might be the most underrated feature in turning AI into repeatable business workflows.
01:34And hey, if you're new to the channel, I'm Brian Castle and I help professional builders stay ahead of the curve with AI. And every Friday, I send my builder briefing. That's a free five minute read where I give you my take on what's actually working right now.
01:46You can get yours by going to buildermethods.com. By the way, if you're serious about adopting Claude code here in 2026, my new course build with Claude code is available now for Builder Methods Pro members.
01:58Alright. Now, let me show you what happened. Okay.
02:00So I'll start by showing you the final output that I'm actually using now here on my Builder Methods site. So this is you know the home page and I've got this visual of the computer and the coffee here on the desk and let's see if I look at builder methods pro, know, now like the hero section has a similar vibe, you know, like a professional builders studio, The desk, we've got the chair, the the plant in the background.
02:22If I take a look at the new build with Claude code course page, this too has, you know, some visuals, a different plant there. And then as I scroll down, know, we've got additional illustrations and objects that help to support or offer like metaphors or visuals that go along with the content that I'm showing on the page.
02:44Each of these illustrations follows a very very similar illustration style.
02:51They all have a very consistent level of detail, the use of color. It's all the same, you know, and and it has the same look and feel.
02:59It's also feels like they're all pulled from the same visual world. And you know, it took me a really long time to develop and land on the exact style that I want and then how we can actually like describe the style and sort of codify it into a a brand visual guideline. So what I'm gonna show you here today is the entire process that I went through to get to the final output that got me here.
03:24Right? So I'll show you the, you know, multiple days of conversations that I had with Claude just to develop the visual brand, the visual world, the guidelines. I'll show you some of the early prototypes that I that I went through with this stuff.
03:39I'll show you how I went about finding inspiration on Dribbble. And then we will dig into the the highly complex n eight n workflow that I put together and I'll show you my thinking behind the systems on all of this and how I intended for it to work.
03:56Most of it actually did work and I'll show you how I went about assembling something this complex in in n eight n and I'm not even an n a typical n eight n user. You know, it interacts with the Slack account. Uh, but then ultimately, you know, I landed on building it out as a Claude code skill and I'll show you that as well.
04:14I'll walk through all of those pieces and sort of the creative decision making process that I went through along the way to arrive at this. Now, wouldn't make sense for you to just lift the entire system that I created here because it is very specific to my brand and and my guidelines.
04:30I hope that you'll be able to take away some of the ideas that went into the systems design and if you're doing any sort of like brand visual exercise, maybe some of my process that went into that could help as well. Now before I get into, you know, like the technical workflow or the Claude code skill, I do want to emphasize how much time I actually spent just creating the guidelines for for for what, you know, landed me on these final visuals.
04:56I did that using a basic conversations in my Claude account. This one here is extremely long. You could see how long it is.
05:03I actually put it inside of a project called builder method. So all of my projects, all my creative writing or planning or stuff that I do for the builder methods business and brand, I do that inside of the builder methods project in my cloud account so that it has all the memory of of what the business is all about and it has the history of all of my decision making that went into it.
05:25So my very first prompt was this, right? You know, I want to develop a visual brand identity for builder methods.
05:33I want to publish a lot of content including articles, workshops, courses and I want visuals. That was like the rough concept that I had in my mind, right, of of I just want it all really well connected.
05:44So then I just went through a really long back and forth. This is Claude being a thought partner for me. First I'm just saying like how should we even go about starting this whole process?
05:54That was my very first question to Claude. Right? And then we just sort of like engaged in this back and forth where I'm asking Claude to suggest some ideas and then I'm giving my reaction to those like I like this, I don't like that.
06:06It asked me questions for, you know, what what I like or and and how how things fit together. And you know, before we even get into the visual aesthetic part, this first one is really just about defining the brand, who I speak to like on my YouTube channel and and who I create things for, who I want to resonate with, who who what I'm all about.
06:27Ultimately, we're what we're creating is a visual identity system and we're sort of like building a a world.
06:35We're we're telling a story if if you will, know, and we and we sort of landed on this concept of a day in the life of a builder. Right? And sort of defining some constant things that you would see in this world like the home studio, the notebook, the mug.
06:49Um, and ultimately, these should show up as little pictures that that appear on the pages or on a thumbnail or or on a workshop. Let's see.
06:59These three, the main artifacts that came out of of this part of the process. Right?
07:04The first one that I want to highlight is kind of the builder methods visual world. So I I like this as a very first artifact to try to get to. We're not describing how things look.
07:16What we're defining here is like the subject matter. What the types of objects or scenes that you might see in this in this world. So that's the world definition and you know, just to show you sort of like the level of detail that that this goes into.
07:29Okay. So that's the the visual world. You know, an another key part of this system is the process by which we decide what to actually illustrate.
07:40Right? So for each little piece of content, I not only want to have the AI generate the actual image but I also don't want to be the one responsible for dictating, okay, we definitely need a mug sitting on a desk next to a pair of headphones.
07:55Like, that's a lot of mental cycles that a, I don't want to spend the time doing that and b, I don't necessarily come up with the most creative ideas. So then we we arrived at this artifact which is called idea to illustration mapping guide.
08:10Right? So we've already established the visual world and the concept that the day in the life of the builder but this is the guide to take the piece of content that I'm giving it or the landing page or wherever I need an illustration, analyze what that content is all about and the topic and who it's for and what I'm trying to say and then use this guide to decide or suggest or pitch concepts to me back to me on what we should convey in the illustration.
08:38What what should the actual object or the scene be. Right? So we've got like a literal like decision process for like what is the core idea?
08:46How do we choose subject matter from our visual world? How do we choose specific objects? And then some like example mapping.
08:54So like if I'm doing a thing about prompt engineering then maybe there's going be an image about chat interface. You know, I talk a lot about spec driven development. If the core concept is spec driven development then maybe the specific opt objects that we show are like an open notebook or or wire print with wire frames or notes or planning before building is the concept.
09:15So we need objects like a blueprint or an architectural drawing, you know, things like that. Okay. But then we come to the actual visual style.
09:23So this artifact is called illustration aesthetic guidelines and this sort of like locks in exactly how each illustration should actually end up looking.
09:32Now how do we come to this? And this this took the most time really. You know, I started this process by, you know, scrolling through Dribbble and getting some some ideas also through this through this long conversation.
09:45I started pasting in some images that I found on Dribbble, like things that I liked and then having Claude sort of send back to me like its description of of what these different styles are. So then I can use these descriptions that Claude helps me to to craft and I can use those to then sort of prototype what the actual AI generated illustrations could end up looking like for builder methods.
10:11So that's when I hopped into Google Gemini, you know, just the straight like Gemini chat product here. And so it gave me like some some options for me to to sort of consider and then I asked it to alright, let's run with this option and see what that looks like, you know, and then we started playing with different colors and different levels of detail.
10:30This one was kind of cool and different but then as we sort of move move along into the into the process we're just exploring and trying different styles on to see how I feel about them and the way that I'm I'm evaluating these is a like obviously do do I like it?
10:47Do I think that it fits the general feel? But also like is it a style that can expand out to many different images and you and be used in many different situations?
10:58Is it flexible? Another thing that I'm looking for is like is it distinctive? You know, does it look super AI generated?
11:05Does it look very typical to things that we see all over the Internet? Know, some of these were were interesting. Let's see if I move along.
11:13So this was another direction that I started to kind of like a little bit more like pixelated. The thickness of the lines, what we went through like different iterations like how thick and how consistent should the lines be. Just going deeper and deeper down the rabbit hole, you know.
11:25But ultimately, we we start to land on something that looks good. Now, by the way, I tried to see if I can get Google Gemini to generate a truly transparent image and I couldn't actually.
11:37So it it thinks that it's creating a transparent image here but it's not like the the checkerboard is actually in the image which is not helpful. So AI generation will generally just create you know flat PNG images. So that's the guidelines piece.
11:51So once I was happy with that, then I moved into the next phase which was to start to build this out as an n eight n automation. My goal with this was to have a Slack channel called illustrations and you can see these were like all of my tests where I could just put in a simple message like, hey, I need an illustration for a LinkedIn post about the morning coffee rituals.
12:12I was just doing these like test examples and then have the bot, you know, respond back to me and then pitch to me three illustration concepts and then I can reply back with a b or c and then it'll go ahead and and generate that.
12:29Behind the scenes this whole chat is powered by this n eight n automation. So my goal with this, number one, I wanna only be able to use Slack. I don't wanna have to like open up n eight n every time I want an illustration or anything like that.
12:44I just wanna be able to chat into into Slack and and then get some options back. I will sort of walk through how this all came together but I just want to tell you that like I am not an n eight n expert by any means. In fact, this was the first big project that I ever really worked on.
13:01How did I actually go about building this? You know, not being an N8N expert. Well, I used Claude, obviously.
13:07So this one no. This one is my conversation that I had with Claude and the way that I set it up was I just put this, you know, on the side and I put n eight n over here, you know.
13:21It looked like something like that. And and I would, you know, just be prompting and talking to Claude on the left side while I build out the thing the workflow on the right. So then we start to actually build out like node by node, you know, one node at a time, you know, for example, like if I just open up, let's say, this node which is a switch node, you know, I'm just I'm just pasting screenshots of what I see in in edit n into Claude and then it's it's telling me like, alright, fill fill out this configuration or we did that for every single node in this workflow.
13:58I'll walk through some of the logic for how we put this together. So we start with a webhook which comes from Slack. So when I when I initiate this with a message in the Slack channel, it sends this webhook.
14:12Then we load in all of those prompts and guidelines, we put them into some code variables and then this switch is sort of handling if it's like a brand new request then we're sort of processing that down here. If the request is already in process and now we're sort of like gathering information about what this illustration should be about, that interaction is happening up here.
14:32And this check says like, do we now have all the information that we have that we need? Is that complete? Then those feed into Okay.
14:41Now we are generating concepts. Meaning like in text giving me three concepts like it says here are three illustration concepts.
14:50That is happening here. So we have a prompt that says like how to generate a concept and then how to formulate your message, how to send it into Slack and then based on the selection a, b or c or if I ask it to like regenerate then it can sort of loop back and give me another round of concepts. But once I select the concept then we move into the actually create the image.
15:12Basically, I wanted to test out Google Gemini versus OpenAI's image generation.
15:18So those are like the two models that offer image generation. I wanted to have a split where I can I can just tweak this to say like I want Gemini for this one or I want OpenAI? I was also playing around with the idea of having it do multiple takes at the same time.
15:35So like generate basically giving it the same prompt and for the same illustration so that I can just choose like alright this version is a little bit better.
15:44This is the call to the to the actual model where we are like generating the image then it like sort of saves the image into a Google Drive folder then it sends me a message in Slack which looks like this. Now here is the link to view the image.
15:58Right? Now, let's see if I can view that one. Yeah.
16:02So here you go. So ultimately, when, you know, when it was all said and done, despite all of the all the effort that I that I put into this, I ended up with this and I tried it a few different times and, you know, this looks kind of cool but it is it's it's pretty far off from from what I actually want for my page here.
16:25Right? You know, it has way too much detail. It doesn't even follow the illustration guidelines at all in terms of like what it should be illustrating.
16:33Like, we were supposed to just make a picture of a mug on a table and I got a picture of an office with a with a weirdly shaded window. Right? So, you know, I thought incorrectly that I could build in the intelligence into this system.
16:50I thought I was doing that when I was loading when I was loading in all of these, you know, guidelines at the at the start of the system.
16:58And we do reference all this stuff in the prompts that we generate here. So, you know, I'm sure I'm sure one of the n8n wizards on on YouTube can probably figure out this problem. But I just, you know, yes, got it all technically to work like it it technically did deliver images into a Google Drive folder for me, um, but they were just way off from what I wanted, uh, which doesn't solve the problem.
17:23So that's when I gave up on this and yeah, I I thought I was done with this whole project until I came up with the idea of using a Claude code skill which duh, I should have done that from the very beginning. Now you're about to see me build this out as a Claude code skill, but first let me quickly explain what a skill actually is.
17:41Think of it as a self contained capability in a folder. So not just a prompt, but an entire mini system with its own files and templates and logic.
17:50And skills are super useful in application development, but in this case, the Claude code skill and Claude code itself is the actual tool for the job. I'm not actually building an app for this. Now, you might be wondering, how can I get Claude code to generate images when Claude doesn't offer an image generation model?
18:08Well, that's the beauty of a skill. I can build a simple script or Claude can build a simple script that uses Google's Gemini API or ImageGen or Nano Banana, whatever they're calling it this month.
18:21That's for the image generation piece. And then we can use Cloud Opus for the interaction and the prompting. Alright.
18:27Let me show you how I set this up. So as I said, this n eight n workflow turned out to be way over engineered and it just fundamentally didn't solve the problem that I was trying to solve.
18:37And I was pretty discouraged by that. I I really thought I wasted a lot a lot of time on this. But then I remembered about Claude code skills.
18:44And so here is the Claude conversation where I kicked off that process to try this out as a Claude code skill. So again, I started by giving it my guidelines that I had established in the first part of this project and then I gave it I would like to build a skill and then Claude read everything and Claude used its its own skill creator skill that's built into Claude to essentially build out the skill.
19:09Right? So, you know I course corrected it a few times then you know Claude suggested this structure for for what will go into the actual skill itself and it laid out some of the key decisions that it made and then it gave me the files to actually just download the skit the you know, like what what makes up the skill.
19:27I wanted to see if I could actually just run this in regular Claude but it turns out since we need since we do need to hit, you know, the, uh, API and I have to have like my my keys in there and everything, um, we end up using it only in Claude code. Okay.
19:40So here we are in the project and as you can see here, the project or the code base if you will is not even a code base. It's it's not an actual application. All it consists of is a Claude folder and inside that a skills folder and then and then I have one skill, the the brand illustrator skill that I had created, uh, with the help of Claude.
20:01I dropped that in and inside the brand illustrator skill, we have the skill m d and I'll I'll walk through this a little bit. Then it has these references to, you know, my visual world document, the visual style, some of the the prompts that will go into the system, that idea to illustration mapping system for it like how to choose what objects or what scenes to illustrate, and then sort of defining the brand colors here.
20:28Those are all the references in assets and I still actually need to build this out more. These are sample illustrations.
20:36Right? So this helps to train the model on how I want my illustrations to look and I I still intend to add more.
20:43I've been able to use the skill as is to achieve, you know the the illustrations the way that I want them. And then finally obviously like the most important part is the script and that is a Python script.
20:55I'm not even a developer in Python. I didn't write any of this. It was all written by Claude.
21:00This is what integrates with my API key which is in the the dot m file. You know, this generation script is pulling in all the references and it's assembling the prompt that goes out to the Gemini API.
21:15Okay. And then of course this the actual skill dot m d. This is like the core skill file that that makes it a skill.
21:24This is the thing that is essentially read by Claude Opus. I'm using Claude Opus 4.5 which is fantastic and this is sort of just going through like when we start it needs to create a project folder.
21:36Oh and then like this is the projects folder. So for every illustration this skill is instructed to create a new folder for each illustration and then you know save the the illustration takes inside that folder.
21:47Right? It needs to generate three concept options, wait for my choice, where to find the color system, how to reference all of the like the visual world, the aesthetic style, the prompts, the idea mapping, all of that is linked or referenced from the skill here.
22:03Like how to name the folder, you know, name it by date, sort of like the workflow for communicating with me and and yeah. So then ultimately it will it will go to work. So let's why don't we actually just test it out and I'll show you finally how how this works.
22:17Right? So I'm going to fire up And by the way, is brand new, uh, today or yesterday.
22:24This is version two point one point two and this is a an update that I've been waiting for. My previous video about Claude's skills when it first came out back in 2025, my main gripe was that we can't directly invoke.
22:38But now here in 2026, we can just do this, brand illustrator and just just go for that. And then I'll say something like, I'm creating a video all about how to develop a systems mindset.
22:52I need a hero image to go with the accompanying blog post. So brand illustrator skill is running and now it's going to gather the the information that it needs from me.
23:04Yeah. Let's go with the red. Then it's asking me about the dimensions and it recommends this one and that works.
23:10Okay. So it has everything that it needs. So it went ahead and it created a new folder in my project and that's this one.
23:19Okay. So now it's presenting to me three concepts. So again, I didn't need to think through like what are some good concepts for this particular blog post.
23:27It's given me these ideas and I can choose between them. Let's see. A workflow notebook, the blueprint stack, building blocks in sequence.
23:35I think the blueprint stack sounds kind of cool. Let's do that. So it says let me read the prompt reference to craft the best prompt.
23:43Alright. So now it it took everything that we just discussed and it put that into a little markdown file. So now it's running that Python script which hits Google Gemini's API to to generate the image.
23:55I think we're using the the image gen API which I mean they just keep renaming these things. It's it's kind of crazy.
24:02Alright. So we have v one. Let's take a look.
24:05And okay. So you know as you can see it it follows my guideline. You know this looks like it's pretty similar or consistent at least with the aesthetic of the type of image that could appear on my site like this.
24:19Right? It again like I didn't have to recreate all the nuanced detail for exactly how I want these lines to look.
24:26Now in practice I end up going back and and having it regenerate, you know, a couple different takes because I get a little bit more creative or I get very picky about how I want different objects and and things to look. So I can just show you like some of the previous ones like this one I went through, you know, five different attempts to just get it just right, you know.
24:48Let's see. This one this one actually has like two different images. One for the left side and then one for the right side.
24:56So you could see like like this one was like almost perfect but I didn't like how this how the shade was covering up the chair. So let's see. I think like the next one yeah.
25:04We sort of fixed the chair issue but the the rug is a little out of whack. So you know, just like little details that like that I would just go through and and re prompt. But that's essentially how I'm doing this.
25:15You know, then I'll bring it into Photoshop and make it transparent and and, you know, I'm even inverting it so that I can get a like a light and a dark mode working on the site. So that's kind of cool too. So what did I learn here?
25:27Well, the NA to N workflow technically worked. But by breaking everything into discrete nodes and rigid logic, I stripped away the intelligence that makes AI actually useful.
25:39't think. It could only execute my predefined steps. But when I moved to the Claude code skill, the model could actually reason about my brand guidelines.
25:48It could understand my intent and deliver what I need while still following my process and nail the consistency that I'm going for. Now, what's interesting is we usually think of Claude code as a tool for building software, but what I built here is really a workflow.
26:04It's an interface for a business process that I'll use over and over. So . And I took the same approach when I created design OS.
26:14That's a free open source system that turns Claude code into a complete product design workflow. So after you hit subscribe here on the channel, over there and I'll show you my complete workflow for how I use Claude code to power Design OS. Let's keep building.
The Hook
The bait, then the rug-pull.
Brian Casel opens with a brand-identity problem every creator recognizes. By the time he drops the word ‘garbage’ to describe a full week of n8n work, the hook is set — and the 30-minute rebuild that follows lands twice as hard.
Named ideas worth stealing.
07:00concept
Visual World Document
Defines the subject-matter universe of a brand before specifying visual style. Separates what to illustrate from how it looks.
Steal forAny brand building an AI image generation workflow — define the world first, then the aesthetic
08:12model
Idea-to-Illustration Mapping Guide
Decision tree that takes a piece of content and outputs a suggested illustration concept. Removes cognitive load of writing illustration briefs.
Steal forAny creator who wants AI-generated visuals to feel intentional rather than generic
17:43concept
Skill as Self-Contained Mini System
A Claude Code skill is not a prompt. It is a folder with files, templates, scripts, and references. The model reads skill.md and executes against the whole system.
Steal forAny repeatable business workflow requiring context, judgment, and multi-step execution
25:35concept
Automation vs. Reasoning Tradeoff
- Rigid node graphs = deterministic execution, no reasoning
- Skills = model reasons over guidelines, contextual output
For deterministic processes, automation wins. For contextual or creative processes, skills and model reasoning win.
Steal forDeciding whether to build in n8n/Zapier vs. Claude Code for any given workflow
How they asked for the click.
VERBAL ASK
26:06next-video
“After you hit subscribe here on the channel, over there and I'll show you my complete workflow for how I use Claude code to power Design OS.”
Clean end-screen redirect. Low pressure. No subscribe beg before the lesson is complete.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
OTHER LINKSAlso linked in the description.
Visual structure at a glance.
