Build Your Brand with Claude ยท Free guide ๐Ÿ’š

Your portfolio.
Built in a single session.

A step-by-step guide to building a professional portfolio site with Claude โ€” from positioning to published. Four phases, eight prompts, one live URL by the end.

Why your portfolio is the most important thing you're not doing

Most professionals are invisible online. Their work exists โ€” in their heads, in Slack threads, in annual reviews โ€” but it isn't anywhere a hiring manager, a potential client, or an inbound opportunity could find it. That invisibility has a cost.

A portfolio site changes the dynamic. Instead of you chasing opportunities, opportunities start finding you. Instead of explaining your value in an interview, you send a link. Instead of hoping your resume lands right, you show your work in the way only you can frame it.

Here's what's changed: building a professional portfolio used to take a designer and a developer and weeks. With AI, it takes an afternoon โ€” and the result is fully yours, editable, and live. The barrier is gone. There's no reason not to have one.

This guide walks you through building yours from scratch, in one session, today.

How to use this guide

Four phases. One session. One live site.

This guide is structured as four sequential phases, each building on the last. You'll start by generating your content with Claude, define your visual direction, mock up your site, and then publish it with Lovable. By the end, you'll have a live URL you can share.

Work through the phases in order. Each phase has one or two prompts โ€” they're written to get Claude to do the heavy lifting while keeping you in control of the decisions that matter. Open Claude in one tab and this guide in another, and work through them section by section. The prompts are designed to be run in a single Claude conversation โ€” Claude builds context as you go, so each prompt gets smarter because of what came before it.

A few things to know before you start: you don't need any technical knowledge, you don't need to be a designer, and you don't need to know what your positioning is yet โ€” Prompt 1 will draw it out of you. The only thing you need to bring is honesty about your work. The more real you are in your answers, the sharper your site will be.

At a glance
โšก
All 8 prompts at a glance
The full session in one view
# Phase What it does Time
1 Content Positioning statement โ€” Claude asks you 4 questions, writes 3 versions ~5 min
2 Content Project highlights โ€” pushes you from job-description to results language ~5 min
3 Content Point of view paragraph โ€” shows how you think, not just what you've done ~3 min
4 Content Full content package โ€” assembled, formatted, ready for Lovable ~2 min
5 Design Extract design DNA from an inspiration site โ†’ save as your design skill ~3 min
6 Wireframe ASCII wireframe โ€” test structure and layout before you write any code ~3 min
7 Mock-up Full HTML mock-up โ€” styled and viewable, ready to iterate on ~5 min
8 Build Lovable prompt โ€” generate and publish your live site ~5 min
Phase 1 of 4
1
Phase 1 ยท Content

Content with Claude

Three prompts that pull the most important content out of you โ€” your positioning, your project highlights, and your point of view. Run them in sequence in the same Claude conversation.

~15 min
1
Positioning statement
Three versions โ€” pick the one that surprises you

The positioning statement is the one or two sentences that sit at the very top of your portfolio โ€” the thing that tells a visitor in ten seconds who you are, what you do, and why it matters. Most people default to their job title. That's a mistake. Your job title tells someone where you've been; your positioning tells them what you're worth.

This prompt has Claude ask you four questions, one at a time, and then write three different versions of your positioning. You'll pick the one that sounds most like how you'd introduce yourself at your best. Claude builds context as you answer each question, so give honest, specific answers โ€” the more real you are, the sharper the output will be.

Prompt 1 โ€” Paste into Claude
I'm building a professional portfolio site and I need to nail my positioning โ€” the one or two sentences that go at the very top. Ask me the following questions one at a time and wait for my answer before moving on: 1. What do you actually do โ€” not your job title, but what problem you solve or what you create? 2. Who do you do it for โ€” what kind of organization, team, or person? 3. What's the thing you do that most people in your field can't or don't? 4. What's the result that someone gets from working with you? Once I've answered all four, write me three versions of a positioning statement. Make each one feel different: - One direct and confident (leads with what I do and at what scale) - One outcome-led (leads with the result someone gets from working with me) - One voice-forward (more human, specific, shows personality) Rules: no job titles, no "passionate about," no buzzwords. If any version sounds like it could belong to 1,000 other people, rewrite it.
What good positioning looks like

Real examples from portfolio sites built by professionals in different fields:

  • "Enterprise healthcare. Agile design. 15 years of leading $40M teams."
  • "Head of Design at Rekki. Building products with purpose and sweat over details."
  • "A creator that designs for creators."

Notice what's absent: job titles, "passionate about," years of experience for its own sake, buzzwords. Specific and confident beats warm and vague every time.

If the output is too generic

Tell Claude: "These still sound like they could be anyone. What's the most specific, unusual, or unexpected thing about my background? Lead with that."

One follow-up question is usually enough. The goal is a version you'd actually put on your site โ€” not one that sounds impressive in the abstract.

2
Project highlights
What changed because of you โ€” not just what you did

Project highlights are where most professionals undersell themselves โ€” not because their work isn't impressive, but because they describe it in the wrong language. Resume language ("I led a team of five") is about activity. Portfolio language is about impact. Claude is going to push you out of the first and into the second.

For each project, Claude will help you write a sharp name, a one-sentence problem statement, your specific contribution, and a result with a real number or a clear before/after. If you don't have a number, Claude will ask the right questions to find one. This is the part where people discover they've been significantly underselling their work.

โŒ Resume language

"Led a team of 5 designers"

โœ“ Portfolio language

"Led a team that shipped a redesign adopted by 200+ hospitals"

Prompt 2 โ€” Same Claude conversation
Now help me write 2โ€“3 project highlights for my portfolio. For each project, I need: - A sharp project name (evocative, not just the company name) - The problem in one sentence โ€” what was broken or missing before I got involved? - What I specifically did (not my team โ€” me) - The result or scale: a number, a before/after, or external validation (press, awards, adoption at scale) Here's how to push me: - If my language sounds like a job description ("I led the design of X"), ask me: what did that enable? What's the number? Who was affected? - If I say "we improved efficiency," ask: by how much? For how many people? Over what period? - If I can't give you a number, ask: what's the before/after? What did someone say about it? Did it get covered anywhere? - Don't accept vague language. Push until it's specific. I'll describe my projects now. Ask me about them one at a time.
โšก

The moment to sit with: when Claude asks "what changed?" โ€” don't answer quickly. The real answer is usually more significant than you've been letting yourself claim.

What if my work is confidential?

Replace company names with categories: "a Fortune 500 retailer," "a Series B fintech startup," "a federal government agency."

The specificity that matters is the result, not the client. "Reduced processing time by 40%" lands just as hard without a name attached.

3
Point of view
The paragraph that shows how you think, not just what you've done

A point of view paragraph is what separates a real portfolio from a glorified resume. Your credentials and project highlights tell someone what you've done. Your point of view tells them how you think โ€” and that's what makes someone want to work with you specifically, rather than the person on the next page with a similar resume.

Claude will ask you three questions about how you approach your field โ€” what others get wrong, what you've learned from experience, what you'd teach someone. Then it will write a short paragraph from your answers. The goal is something that sounds like you'd say it at a dinner table, not something you'd put on a LinkedIn headline.

Prompt 3 โ€” Same Claude conversation
Now write me a short POV paragraph for my portfolio โ€” 3 to 5 sentences that show how I think about my work, not just what I've done. Ask me these three questions one at a time and wait for my answer before moving on: 1. What's something most people in your field get wrong? 2. What do you know from experience that you couldn't have learned from a course or a book? 3. If you could only teach someone one thing about how you approach your work, what would it be? Then write a paragraph based on my answers. Rules: - First person - No "passionate about," no "I believe in the power of," no buzzwords - It should sound like something I'd say at a dinner table, not on LinkedIn - If it sounds generic after writing it, tell me what's missing and ask one more question to fix it
If the paragraph doesn't sound like you

Read it out loud. If you'd never say it, tell Claude: "This doesn't sound like me. Here's how I'd actually say it: [say it in your own words, even roughly]."

One round of this usually gets you to something real. The goal isn't polish โ€” it's honesty. A slightly rough paragraph that's true to your voice will outperform a perfect-sounding one that isn't.

4
The full content package
Assembles everything into one clean document โ€” ready for your site builder
Run this last

Once you've finished Prompts 1โ€“3 and are happy with your positioning, your project highlights, and your point of view, this prompt compiles everything into a single, cleanly formatted content document. This document is what you'll hand directly to Lovable in Phase 4 โ€” so save or copy the output before moving on.

Prompt 4 โ€” Same Claude conversation
Great. Now compile everything we've built into a clean portfolio content document with these sections in order: 1. POSITIONING โ€” the version I chose 2. PROJECT HIGHLIGHTS โ€” all 2โ€“3, formatted consistently 3. PROOF STRIP โ€” based on my background, suggest 3 quick-hit credibility markers (scale numbers, speaking, mentoring, press, awards โ€” whatever fits best) 4. POINT OF VIEW โ€” the paragraph we just wrote 5. CTA โ€” suggest the single best way for someone to reach me based on what I've shared Format it clearly with section headers. This document is going directly into a site builder, so keep the writing tight and ready to publish.
โ†’

Save this output. You'll use it in Phase 4 when you build in Lovable. Copy it somewhere you can get back to โ€” a notes app, a doc, or just keep the tab open.

Phase 2 of 4
2
Phase 2 ยท Design

Design Direction with Claude

Extract a design system from a site you love and save it as a reusable skill. You set it once โ€” and Claude applies it to everything you build going forward.

~5 min
5
Extract your design DNA
Save it as a reusable skill โ€” used on every future project

Before building anything, you need a design direction. This doesn't require a designer โ€” it requires one site you love. Claude will analyze that site, extract its visual system (colors, typography, layout feel, vibe), and save it as a file called design-skill.md in your working directory. From that point on, every time you build something in Claude Cowork, you can reference /design-skill and it will apply your visual identity automatically.

This is one of the most powerful patterns in this guide: you're not just building a portfolio site, you're establishing a design system you own. Every future document, deck, or page you build with Claude will automatically feel like you.

๐Ÿ“Œ

Before running this prompt: have a site you admire bookmarked and ready. If you don't have one, use Option B below โ€” it asks you four preference questions instead.

Option A โ€” From an inspiration site (recommended)

Find a portfolio, brand site, or any site whose visual feel you want to channel. It doesn't have to be in your field โ€” it just has to feel right. Then run this prompt in Claude Cowork with the URL.

Prompt 5A โ€” Run in Claude Cowork
I'm going to build a portfolio website and I want it to feel like this site. Analyze this page and extract my design system: - Primary and accent colors (with hex codes if possible) - Typography style and feel - Layout approach and use of space - 5 words that capture the overall vibe Then save this as a design skill file called design-skill.md in my working directory. I'll use this skill on any future project by referencing /design-skill. Site to analyze: [paste the URL of the site you love]
Option B โ€” From preferences (no inspiration site)

If you don't have a site in mind, this version asks you four quick questions about how you want your site to feel, then builds a design system from your answers.

Prompt 5B โ€” Run in Claude Cowork
I'm building a professional portfolio and I want to define my design direction before I build anything. Ask me 4 quick questions about my visual preferences: 1. Three words that describe how you want your site to feel 2. Light background or dark background? 3. Clean and minimal, or rich and expressive? 4. One brand, site, or designer whose aesthetic you admire (doesn't have to be in your field) Then generate a design system for me: - A color palette (2โ€“3 colors with hex codes) - Typography direction (serif or sans-serif for headers, clean body font) - Layout feel (generous whitespace, tight and dense, editorial, etc.) - 5 words that capture the vibe Save this as a design skill file called design-skill.md in my working directory.
โœจ

Why this matters beyond today: once the skill is saved, every future project you build in Claude โ€” decks, documents, landing pages โ€” automatically uses your visual identity. You set it once; it follows you everywhere.

Phase 3 of 4
3
Phase 3 ยท Mock-up

Mock-Up with Claude

Wireframe first, then HTML. Testing structure and layout before writing code saves you from rebuilding. Two prompts โ€” one fast, one polished.

~10 min
6
ASCII wireframe
Test the content structure and layout before committing to code

A wireframe is a simple text diagram of how your site is laid out โ€” which sections appear in which order, and how much space each one takes. It takes two minutes to change a wireframe and two hours to change a coded site. This step exists so that you make those decisions now, before anything is built.

If a section has too much content in the wireframe, it will feel overwhelming in the actual site. If the order doesn't feel right, fix it here. Claude will flag anything that looks crowded and suggest cuts โ€” take those suggestions seriously.

Prompt 6 โ€” Run in Claude Cowork
Using my portfolio content and my /design-skill, build an ASCII wireframe of my portfolio site. Structure it as a one-page site with these sections in order: 1. Hero โ€” positioning statement + one CTA button 2. Project highlights โ€” 2โ€“3 cards, each with project name, problem, result 3. Proof strip โ€” 3 credibility markers in a row 4. About / POV โ€” short paragraph 5. Contact โ€” one CTA Keep each section clearly labeled and separated. One idea per section. If any section has too much content, flag it and suggest what to cut. Save as portfolio-wireframe.txt in my working directory.
โ†’

Review before moving on. Does the order feel right? Is any section text-heavy? Push back with specific edits: "move the proof strip above the project highlights" or "the about section is too long โ€” cut it to 3 sentences."

7
HTML mock-up
Styled, viewable, and ready to iterate before you build in Lovable

This is where things start to feel real. Claude takes your wireframe and turns it into a fully designed, viewable HTML file โ€” complete with your color system, typography, and layout from Phase 2. You'll be able to open it in your browser, see what it looks like, and iterate on it in plain English before you commit to Lovable.

This step matters because it's much easier to say "the hero section feels too crowded" when you can see it than when you're describing it from memory. Make the changes you want here โ€” get it to a place you're happy with โ€” and then carry it into Phase 4 as your blueprint.

Prompt 7 โ€” Run in Claude Cowork
Now build a complete HTML portfolio site from portfolio-wireframe.txt. Use my design skill: /design-skill Requirements: - Single self-contained HTML file (all CSS inline or in a style block) - Responsive โ€” looks good on mobile and desktop - Each section has generous whitespace and clear visual hierarchy - Project highlights as cards with the project name, problem sentence, and result - The proof strip as a clean 3-column row - One clear CTA at the bottom - No placeholder images โ€” use background colors or simple geometric shapes instead Save as portfolio.html in my working directory. When it's saved, show me the link to preview it.
How to iterate on the HTML preview

Give Claude specific edits in plain English โ€” you don't need to know any code:

  • "the hero section feels too crowded โ€” remove the subtitle and just keep the positioning line."
  • "make the project cards taller with more breathing room."
  • "change the CTA button color to match the accent from my design skill."
  • "the proof strip numbers need to be bigger โ€” that's the most important part of that section."

Iterate until you're satisfied with the overall structure and feel. You don't need to get it perfect here โ€” just good enough that you know what you're building toward.

Phase 4 of 4
4
Phase 4 ยท Build

Build & Publish with Lovable

You have a designed HTML mock-up and a complete content document. This is everything Lovable needs to build your live site. A published URL in under 60 seconds.

~5 min
8
Generate the Lovable prompt
Translates your HTML mock-up into a prompt Lovable can build from

Lovable is an AI site builder that takes a prompt and generates a fully functional, hosted website with a live URL. This final prompt has Claude translate everything you've built โ€” your HTML mock-up, your design skill, and your content package โ€” into the exact input Lovable needs.

You don't need to modify anything Claude generates. Take the Lovable prompt it gives you, go to lovable.dev, start a new project, paste the prompt, and click Build. Your site will be live in under 60 seconds.

Prompt 8 โ€” Run in Claude Cowork
I'm ready to build my portfolio site in Lovable. Based on portfolio.html and my /design-skill, generate the complete code and instructions I need to paste into Lovable to build this site. Give me: 1. The exact prompt to paste into Lovable to generate the initial build 2. Any specific design or layout instructions Lovable will need 3. The content to paste in (from my portfolio content document) Make the Lovable prompt detailed enough that the output matches the structure and feel of portfolio.html as closely as possible.
โ†’

Then in Lovable: go to lovable.dev, start a new project, paste the prompt Claude generated, add your content, and click Publish. Takes about 60 seconds. You'll have a live URL to share.

Making edits in Lovable after publishing

Lovable responds to plain English edits the same way Claude does:

  • "make the header font larger"
  • "change the background color to cream"
  • "add a thin line between each section"
  • "center the CTA button"

Once you're satisfied, hit Publish again and your changes go live instantly. Your site lives at a Lovable URL by default โ€” you can connect a custom domain anytime from the Lovable dashboard.

After today
โ†’
Keep building on it
Version 1 is just the start

The best portfolios get sharper over time. A few commitments to make to yourself now that your site is live:

  • Every time you finish a meaningful project โ€” add it
  • Every time you get external validation (press, award, speaking) โ€” add it to the proof strip
  • Every time your direction in your work changes โ€” update your positioning
  • Share your live URL โ€” put it in your email signature, your LinkedIn, everywhere
๐Ÿ“…

Your portfolio and LinkedIn need to tell the same story. Once your portfolio is live, the next step is making sure your LinkedIn reflects the same positioning โ€” the same voice, the same results language, the same version of you. That's the work of the next session.

โ˜…
Share this guide
Pass it on to someone who needs it

If this guide was useful, the best thing you can do is share it with someone else who should have a portfolio and doesn't yet. Most people don't know this process exists โ€” that you can go from zero to a live, professional portfolio site in a single afternoon with AI.

โ˜…

More guides and sessions at: angela-builds.com โ€” LinkedIn rewrite, content system, network activation, and more.

โ†’ Visit Angela Builds