Website, deck, profile, email, and invoice
After this, you'll be able to create a real-context brand test and use it to move from vague brand taste toward a usable identity system.
Before you start
Complete Critique the identity like a buyer first.
The idea
A brand is ready when it works in the places the business actually uses it. This lesson asks you to make a real-context brand test, not a vague creative preference. The output should be specific enough that Claude, Canva, Adobe Express, Claude Design, or a designer can use it without guessing.

Here is the before and after: Before, the identity looks good in a controlled mockup. After, it is tested across website, deck, profile, email, invoice, and any customer-facing asset that matters. For example, a solo service brand should show who it helps, what promise it makes, what proof supports that promise, and where the identity must appear first. A company brand should add rules for collaborators, templates, and repeated use.
Now try it: Pick five contexts and score the brand kit against each one. Make one choice before asking Claude to write: audience, promise, reference, asset type, tool, launch context, or review risk. That choice keeps the work from turning into generic brand inspiration.
The lesson is done when the artifact can guide a real brand asset and survive one honest review.
Try it (16 min)
Watch out for
Paste this into Claude
Test this brand kit across real contexts: [paste]. Contexts: website, deck, profile, email, invoice, and [other]. Score clarity, trust, readability, fit, and asset gaps. Recommend fixes. If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Brand Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Use This Publicly Without Fixing It. Keep the answer practical enough that I can paste it into my brand working doc.
What a good response looks like
Finished Artifact: - a real-context brand test - Why it matters: it gives the brand system a concrete thing to inspect instead of a vague intention. - Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything. Reality Check: - The artifact names the user, input, decision, owner, or proof it depends on. - The weakest assumption is visible. - The next step can be completed in one sitting.
What good looks like
Go deeper (8 min)
Paste this into Claude
Without rereading the lesson, explain why a real-context brand test matters in three bullets. Then apply it to a second brand example: [describe a different solo brand, company, or project]. Return What Changed, What Stayed The Same, What To Check Before Public Use, and the exact next action.
What a good response looks like
Transfer Check: - What changed: the second example has a different audience, input, or delivery context. - What stayed the same: a real-context brand test still needs a source, a review check, and a next step. - Before trusting it: inspect the brand review check that would catch a wrong assumption. - Next action: run the check once, then carry the revised artifact into the next lesson.
What good looks like
When this breaks
AI can help with this
Paste the exercise prompt into Claude with your real brand context. Ask Claude to interview you one question at a time, produce a real-context brand test, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next brand step.

You can now
You can point to a real-context brand test.
Key takeaways
Real-context testing proves whether the brand can leave the moodboard.