Skip to content
Agentic Levels

Everything starts here.

GuestLocal progress only
PreferencesSign in
01Start with one taskBest first move for beginners.02Check your LevelMeasure where you are.03Score an AI resultFind the habit to practice first.04Return to Your WorkScores, links, and checkpoints.
Start here

Begin

HomeThe main entry point.New to AIStart with one useful task.
Know where you are

Measure

Check your LevelUse this after you have tried AI.Fluency ScoreScore an AI result you can review.
Build the habit

Learn

LevelsLessonsTracks
Find the reference

Library

PromptsReferenceResourcesCompare Tools
Turn it into work

Apply

Your Next MoveChoose what AI should change next.Tool SetupGet the tools ready.
Come back later

Return

Your WorkScores, links, and checkpoints.My PathContinue from your level.Updates
Site

Site

PricingAboutFAQ & FeedbackPreferences

© 2026 Fuentes Studio

Privacy·Terms
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

Tracks›Build Your Portfolio
L1Lesson 4Free

Briefing Claude to Build Your Portfolio

After this, you'll be able to write a brief specific enough that Claude generates a real portfolio layout on the first or second try, preview it inside Claude before downloading, and get a contact form that actually works on Netlify.

Before you start

Complete Writing Your Portfolio Copy with Claude first; this lesson uses the copy you wrote there.

The idea

A brief that names five things (your role, sections in order, visual direction, real content, and "self-contained HTML file") is what turns Claude from a fragment generator into a deployable portfolio on the first try. Claude does not build websites by default. It builds whatever you describe. The difference between a generic result and a result you would actually use comes down to how specific your brief is.

The portfolio task for Briefing Claude to Build Your Portfolio begins with scattered assets, unclear proof, and no publish-ready decision.
The portfolio task for Briefing Claude to Build Your Portfolio begins with scattered assets, unclear proof, and no publish-ready decision.

A strong brief tells Claude five things: what kind of creative you are, the exact sections you need in order, the visual direction (dark or light, one dominant color), the actual content for each section (your real Vimeo URL, your bio text, your software list), and the output format. That last one, output format, is the most important and most often forgotten. The output you want is a single HTML file (HyperText Markup Language, the plain text file every web page is built from), with all the styling included inside it.

Here is the before and after: A weak brief ("Build me a portfolio website") returns a template with a hero, an about section, and a contact form: it looks like every other AI-generated site. A strong brief that ends with "give me a complete, self-contained HTML file with all CSS in a style block, ready to save as index.html and open in a browser" returns something deployable (ready to put live on the web) in one drag-and-drop. CSS here means Cascading Style Sheets, the rules that set colors, fonts, and spacing, kept inside the same file so there is nothing extra to upload.

Without that instruction, Claude returns code fragments you would need to assemble yourself. Adding `data-netlify="true"` to the contact form tag (a small label that tells Netlify, your future web host, to catch each message and email it to you) makes the form actually send email. Leave it out and the form silently fails.

Now try it: run the exercise prompt below with your Portfolio Brief pasted at the top and all five inputs filled in: type of work, sections in order, visual direction, actual content, output format instruction. Click the Preview button inside Claude before downloading to catch any layout problems. When the preview looks right, download the file. That is your portfolio, ready to drag onto Netlify.

Try it (12 min)

Watch out for

  • Not specifying 'self-contained single HTML file'. Claude will give you fragments you cannot deploy
  • Not using the Preview button before downloading. Two minutes of checking inside Claude beats discovering a broken layout after deploy
  • Using a placeholder Vimeo URL like 'vimeo.com/yourvideo'. Claude will embed a broken link; use your real URL
  • Forgetting data-netlify='true' on the form. Without it, form submissions go nowhere. It is the most commonly missed instruction in this lesson.
  • Not hosting your images before writing the brief. Unhosted local image paths produce broken image boxes after deploy. Claude cannot access files on your computer
  • Asking for JavaScript frameworks (React, Vue). Netlify drop works with plain HTML; frameworks need a build step you do not want right now

Paste this into Claude

[Paste your Portfolio Brief here: the paragraph you wrote in Lesson 0]

---

Build me a complete, self-contained portfolio website as a single HTML file with all styling included. I have my copy ready from the previous lesson. No external files needed, no programming tools needed. I should be able to save it as index.html and open it in a browser.

Here's what I need:

**Type of work:** [video editor / photographer / motion designer / your specific role]

**My copy (use this exactly):**
- Hero tagline: [paste your tagline from the copy lesson]
- Short bio: [paste your short bio]
- Long bio: [paste your long bio for the About section]

**Sections (in this order):**
1. Header with my name and navigation links to each section
2. Showreel section: embed this video: [your Vimeo or YouTube URL]
3. Project grid: [number] projects in a 3-column grid. Titles: [list your project titles]
4. Project descriptions: [paste your project descriptions, or ask Claude to use placeholder descriptions in the 3-sentence format from the previous lesson]
5. About section: use my long bio above
6. Contact section: a form with name, email, and message. Add data-netlify="true" to the form tag so Netlify processes submissions automatically.

**Images:** [If you have hosted image URLs, list them here. If not, write: "Use color-block placeholders with the project title as a label"]

**Visual direction:**
- Theme: [dark background with light text / light background with dark text]
- Accent color: [one color, e.g., "warm amber yellow" / "#FCB116" / "the same green as Spotify"]
- Typography: clean and modern, good for creative work

**Important:** Make it fully responsive for mobile. Use only CSS, no JavaScript. Self-contained single file. After generating, I will use the Preview button to check it before downloading.

Created by potrace 1.16, written by Peter Selinger 2001-2019 What good looks like

  • You clicked the Preview button and saw your portfolio rendered as a live page inside Claude
  • The preview shows your actual tagline and bio, not placeholder text
  • The showreel section shows your actual video URL (not a broken link)
  • The contact form has data-netlify='true' in the opening form tag (you can check by looking at the code Claude generated)
  • You downloaded the file, opened it in a browser, and it looks like a real website
ProofMove through Briefing Claude to Build Your Portfolio, check proof, then fix only the weak part.
yesnorun it again
StartBegin with the real task
Briefing Claude to Build YourAfter this, you'll be able to write a brief specific enough that Claude generates a
1Proof visible?You clicked the Preview button and saw your portfolio rendered as a live page inside
Ready to usePreview your portfolio inside Claude, confirm the contact form has
Fix the weak partBreaks when the brief is too vague about sections. 'a few project images' produces an

When this breaks

  • Breaks when the brief is too vague about sections. 'a few project images' produces an arbitrary grid; '8 projects in a 3-column grid, titled Commercial, Music Video, Corporate, Wedding, Documentary, Social, Animation, Other' produces exactly what you asked for
  • Breaks when the user pastes a broken or private Vimeo URL. Verify the video is publicly accessible before briefing Claude

AI can help with this

Use Claude or your build tool to help you you can write a brief specific enough that Claude generates a real portfolio layout on the first or second try, preview it inside Claude before downloading, and get a contact fo.... Start with the exercise prompt and your real input. Ask for one draft, then check it against this proof: You clicked the Preview button and saw your portfolio rendered as a live page inside Claude. Accept only the version you can verify yourself.

The task passes through brief, build, review, and publish proof before the portfolio surface is trusted.

Created by potrace 1.16, written by Peter Selinger 2001-2019 You can now

✓

You clicked the Preview button and saw your portfolio rendered as a live page inside Claude

  • ✓The preview shows your actual tagline and bio, not placeholder text
  • ✓The showreel section shows your actual video URL (not a broken link)
  • ✓The contact form has data-netlify='true' in the opening form tag (you can check by looking at the code Claude generated)
  • ✓You downloaded the file, opened it in a browser, and it looks like a real website

Key takeaways

Specificity is the unlock. The five things Claude needs: your role, your sections in order, your visual direction, your actual content, and the output format. 'Self-contained single HTML file' is the one instruction that separates a deployable result from fragments. 'data-netlify=true' is the one instruction that makes your contact form actually work.

  1. 1Use the Preview button inside Claude to check your portfolio before downloading. Fix problems there, not after deploy.
  2. 2'Self-contained single HTML file with CSS in a style block' is the magic phrase for a deployable result.
  3. 3'data-netlify=true' on your form tag is the only instruction needed for a working contact form on Netlify. No backend required.
  4. 4Host your images first on an image host (a free service that gives each photo a public web link, like Cloudinary, Imgur, or Google Photos). Local image paths (files on your own computer) produce broken boxes after deploy, because the web host cannot reach your machine.
  5. 5Have your real Vimeo/YouTube URL ready before you start. Placeholder URLs produce broken embeds.

Was this helpful?

Up nextEmbedding Your Showreel→
← Back to Build Your Portfolio