The part that makes this feel like a design team rather than a prompt is the file in the middle. Once your brand exists as text Claude can read, every later request starts from your rules instead of from its defaults, and the output stops drifting between chats.
This is the one from the reel, in full. Run it on its own and read the output properly, because everything downstream inherits whatever it gets wrong.
Read this page and write me a brand DNA file I can hand to a designer: [paste your URL].
Structure it under these headings, in this order. Brand in one line: what this is and who it is for. Voice: five specific adjectives, each with a real quoted line from the page as evidence, plus a short "we say this, not that" list of words the brand uses and words it avoids. Colour: the actual hex codes you can see in use, labelled by role (background, text, primary accent, secondary accent, borders), and say which one carries the calls to action. Type: the heading font, the body font, and roughly how big headings are compared with body text. Layout habits: how much white space the page leaves, whether corners are rounded or square, whether it uses shadows, borders, or neither, and how wide the text column runs. Imagery: what the photos and graphics have in common, including lighting, colour temperature, whether people appear, and what would look wrong here. Proof: the strongest specific claims, numbers, credentials or testimonials actually on the page, quoted exactly. Audience: who is clearly being sold to and who is not.
Rules while you do it. Quote the page rather than paraphrasing whenever you are describing voice, and mark anything you are inferring rather than reading directly with "inferred", because I am going to build a whole visual system on this. If the page is thin on a section, write "not enough on the page" instead of inventing something plausible. Finish by writing the whole thing again as one clean markdown file called brand-dna.md, with no commentary around it, so I can save it as is. Do not use em dashes.brand-dna.md. This is now the source of truth for your brand, and it is yours, not locked inside a chat.Generic content ideas are the reason most brand tools feel useless. This prompt forces every concept back through the DNA file, and asks for the visual idea alongside the copy so the two are designed together.
Using the brand DNA file in this project, give me eight social post concepts for the next month. Do not give me content pillars or a strategy essay, give me eight specific posts I could build this week.
For each one write: the concept in one line, the exact headline as it would appear on the creative in under nine words, one supporting line under twenty words, the visual idea described concretely (what is on the canvas, which brand colour dominates, whether it is one big number, a quote, a comparison or a list), and the caption angle in a sentence. Vary the formats deliberately so this does not turn into eight versions of the same card: include at least one single-number stat, one myth versus reality, one short list, one quote from the page, and one before and after.
Every concept has to be traceable to the DNA file, so after each one add a short line saying which part of the brand it is drawing on, for example the voice adjective, the proof point or the audience it targets. If a concept needs a claim that is not in the file, say so rather than inventing the claim. Rank the eight from strongest to weakest at the end and tell me honestly which two you would cut.This is the step that replaces the Canva afternoon. Claude writes each post as a single HTML file, which renders live in an artifact, and every brand value sits at the top as a variable rather than being scattered through the layout. That is what makes the whole set editable later.
Build concept [number] as a single self-contained HTML file I can screenshot as an Instagram post, using only the colours, fonts and layout habits in the brand DNA file.
Technical requirements. The canvas is exactly 1080 by 1350 pixels, set on a wrapper div with fixed width and height and overflow hidden, so nothing spills or reflows. Put every brand value in one :root block of CSS variables at the very top, named by role: background, text, muted text, primary accent, secondary accent, border radius, and the two font families. Nothing lower down may hardcode a colour or a font, everything references a variable, because I am going to change one line and re-render the whole set. Load fonts from Google Fonts if the brand fonts are available there, and if they are not, pick the closest match, name your substitute in a comment at the top, and tell me in the chat what you substituted and why.
Design requirements. One idea per canvas and one clear focal point. Type at post scale, so the headline is large enough to read on a phone at thumbnail size, roughly 64 to 96 pixels, and never smaller than 32 for supporting text. Leave generous margins, at least 80 pixels on every side. Use the accent colour on one element only, so it stays an accent. No stock icons, no clip art, no gradients unless the DNA file says the brand uses them, no lorem ipsum: use the real headline and supporting line from the concept.
Then render it as an artifact so I can see it, and underneath tell me in three bullets which brand rules you applied and anything you had to guess.A Canva design has to be updated one file at a time. A set built on variables updates together, which is the whole reason to build creatives as code rather than in a canvas tool.
Here are the creatives we have built so far. I want to change the system, not the individual posts.
Change [the primary accent to #XXXXXX / the heading font to X / the border radius to X], then regenerate every creative with that change applied, keeping every headline, every piece of supporting copy and every layout exactly as it is. Only the variables in the :root block should differ between the old version and the new one, so if you find yourself rewriting layout to make the change work, stop and tell me which creative is fighting the change instead of quietly redesigning it.
After the set is regenerated, show me each one and flag any where the new value breaks something real: contrast that is now too low to read, a headline that no longer fits its box, or an accent that has stopped standing out. For each of those, propose the smallest fix rather than a redesign.Once you have run this a few times, stop pasting four prompts. A skill is a small folder with a SKILL.md inside holding a name, a description of when to use it, and your instructions. Claude reads the description and pulls in the full skill when your request matches, so the chain becomes one word. Skills work on every plan, Free through Enterprise, and there is no code to write.
Build me a reusable Claude skill called "brand" that runs my whole brand creative chain.
Use skill-creator to write it. The SKILL.md description should say to use it whenever I ask for on-brand social creatives, campaign concepts or a brand style guide. The instructions should say: first look for a brand-dna.md file in the project and read it, and if there is not one, ask me for a URL and build it before doing anything else. Then, when I ask for creatives, generate each one as a single self-contained HTML file at 1080 by 1350 with every brand value declared as a CSS variable in a :root block at the top, generous margins of at least 80 pixels, one focal point per canvas, and the accent colour used on one element only. Always finish a creative by listing which brand rules were applied and anything that was guessed.
Include a rule that you never invent a statistic, testimonial or guarantee that is not in the brand DNA file, and that missing information is flagged rather than filled in. Then package it as a zipped folder I can upload.~/.claude/skills/ instead. Anthropic's creating custom skills article walks the same steps.The honest ceiling is taste. Claude will apply your rules faithfully, which means a vague DNA file produces confident, consistent, mediocre design. Time spent sharpening that one file pays out across everything you build afterwards.
Anthropic on artifacts, including single page HTML rendering and plan availability
Enable and use web search, on Claude retrieving content from a URL you give it
Creating and managing projects, including the five project limit on free accounts
Creating custom skills, the official install walkthrough