Create profile and social assets
Bio, avatar, banner, and first posts
After this, you'll be able to create a profile asset packet and use it to move from vague brand taste toward a usable identity system.
Before you start
Complete Assemble the small brand kit first.
The idea
Profile assets are often the first place the brand gets judged. This lesson asks you to make a profile asset packet, 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 bio, avatar, banner, and first posts each feel like separate choices. After, they all follow the same promise, voice, and visual rules. 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: Use the brand kit to create a profile packet for one real platform. 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.
- Messy inputThe raw brand identity material before the lesson shapes it.
- a profile asset packetThe thing you can inspect, edit, and reuse.
- Review checkThe brand review check that catches a weak assumption.
- Next stepThe output moves into the next lesson instead of sitting alone.
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
- Writing a bio that sounds like every competitor.
- Using an avatar that fails small.
- Posting before the promise is visible.
Paste this into Claude
Use this brand kit: [paste]. Create a profile asset packet for [platform]. Include bio options, avatar guidance, banner copy, pinned post or intro post, visual notes, and what not to include. 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 profile asset packet - 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
- The platform is named.
- Bio, avatar, banner, and first post are included.
- Visual notes follow the brand kit.
- Exclusions are included.
Go deeper (8 min)
Paste this into Claude
Without rereading the lesson, explain why a profile asset packet 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 profile asset packet 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
- You explained the lesson idea from memory before applying it again.
- The second example changes the artifact instead of copying the first answer.
- The public-use check names a real risk.
- The next action can be done in one sitting.
When this breaks
- Breaks when profile assets do not share a promise because the brand feels scattered.
- Fails when platform context is ignored because the asset does not fit its real use.
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 profile asset packet, 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 profile asset packet.
- You can explain what brand decision it makes clearer.
- You can name the assumption that still needs checking.
- You can use the output in the next lesson.
Key takeaways
Profile assets are a small public test of the brand kit.
- Profiles need platform context.
- Bios should carry the promise.
- Avatar use tests the logo territory.
- First posts should introduce the brand job.