The argument in one line.
A non-technical creator can direct Claude Code to build a fully animated personal website by treating every section as a five-step loop: describe the feeling, mock it up cheaply, react with specific notes, push to preview, then ship only once it is right.
Read if. Skip if.
- A creator or solo founder with an existing personal brand who wants an animated, high-craft personal site without hiring a developer or designer.
- Someone who already has real brand assets (photos, logo files, bio/story) sitting in a tool like Notion and wants to feed that directly into an AI build instead of writing copy from scratch.
- Someone curious what an actual agentic Claude Code build session looks like end-to-end, including background task delegation and iteration cycles.
- A reader deciding whether to use a frontier/limited-access model (like Fable 5) for a big one-time build versus routine maintenance.
- You need a multi-page site with e-commerce, gated content, or complex backend logic - this is a single animated landing page, not a full web app build.
- You want a hands-off, zero-effort result - the video's own lesson is that getting it right took several hours of specific back-and-forth, not one prompt.
The full version, fast.
The video walks through building a fully animated personal website with Claude Code running the Fable 5 model, using Higgsfield MCP for AI-generated hero video, Kit for email capture, and 21st.dev purely as design inspiration. The core mechanism is a repeatable five-step loop applied to every section of the site: talk out the feeling and reference (no build request yet), mock up a cheap throwaway version to react to, give specific corrective feedback, push the approved version to a preview link only, and only ship to production after reviewing both desktop and mobile. Key conclusions: feed the AI real brand assets and story (not guesses), never let AI redraw a trademarked logo (composite the real file instead), treat mobile as a separate design pass, and reserve a frontier model like Fable 5 for the big one-time build rather than day-to-day maintenance.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open
States the claim and introduces herself as a creator strategist and founder of Lions Behavior.

02 · Tools you need
Claude Code, Fable 5, Kit, Dubsado, and 21st.dev - what each tool is for and why.

03 · Prompt 1: build an animated website with Fable 5
The literal first prompt used to frame the project, referencing Lewis Howes' site and asking Claude to interview her before building anything.

04 · Feed Claude your brand knowledge base
Pulling bio, origin story, and social links from Notion so the AI works from real material instead of guessing.

05 · Build the hero section with Higgsfield MCP
Turning an approved still image into a looping hero video; the bridge concept emerges from her Notion content.

06 · The five-step loop for every section
Talk it out, mock it up, react specifically, port to preview, review then ship - the repeatable framework used for the rest of the build.

07 · The foundation prompt: build the whole page
The single prompt that assembled the first full version of the site onto a preview link, with real copy, hero video, and Kit signup wired in.

08 · Change the colors and fonts
Swapping the original black-and-gold palette for cream and navy, plus a mobile-specific hero crop fix.

09 · Break the site into sections with Claude artifacts
Specs each section (logo ticker, work-with-me modal, content, this-is-nicky stories, community) and shows the New York subway-line navigation concept taking shape inside Claude artifacts.

10 · Credibility, Instagram story, and content sections
The 'This Is Nicky' bio section and the floating YouTube-thumbnail content section, both tied to the subway-stop navigation.

11 · Digital products and protecting the trademark
Adding the Draftloop product section, and the fix for AI mangling a trademarked logo on the product box render.

12 · Community, work with me, and newsletter sections
Lions Behavior community section, the Work With Nicky modal, and the Content Corner newsletter signup.

13 · The polish pass before publishing
Four-part copyedit pass: grammar/clarity, punctuation rule, one capitalization rule, and consistent emphasis.

14 · Hard lessons building a website with AI
Recap of the hard-won rules: mock before you build, never let AI draw your trademark, react with specifics, keyframe before you animate, mobile is a separate design, use real content.

15 · Free playbook and how long it took
Offers the downloadable prompt playbook and is candid that the polished version took several hours of tweaking, not one prompt.

16 · When to use Fable 5
Guidance to reserve Fable 5 for big one-time builds and switch to other models (Opus 4.8, Sonnet 5) for ongoing maintenance.
Lines worth screenshotting.
- A mockup you can actually feel beats any written description when directing an AI website build.
- Never let AI redraw a trademarked logo - composite the real logo file onto the AI-generated artwork instead of asking the model to draw it.
- Iterate on a still image before generating video, because video generation is slow and expensive to redo compared to a still.
- Mobile needs its own design review on a real phone; a desktop-approved layout can crop a subject completely out of frame on mobile.
- Deploying to a preview link first and shipping to production only once, at the end, keeps early iteration mistakes invisible to real visitors.
- Giving an AI agent your actual brand assets - photos, bio, story pulled from a tool like Notion - produces on-brand output where a written description alone would force it to guess.
- Reference sites should be used for behavioral inspiration only, not copied code, to keep a personal brand site from feeling templated.
- Specific, reactive feedback like 'the folder is too wide' or 'lower the opacity' resolves a design issue in one round, where vague feedback takes five.
- A final copyedit pass with explicit rules - no em dashes, one capitalization rule for headlines and buttons, consistent bold/italic use - keeps AI-drafted copy from reading inconsistently across sections.
- Reserving a frontier or usage-limited model for a single large build, then switching to a standard model for ongoing maintenance, is a practical way to manage a capped usage allowance.
A five-step loop turns vague AI website requests into a shipped site.
Directing an AI agent to build brand-facing work goes faster and further when every section follows the same disciplined loop: describe the feeling, mock it cheaply, give specific feedback, preview, then ship once.
- Describe the feeling and reference material first, and explicitly hold off asking for a real build until the direction is agreed on.
- Get a cheap, throwaway mockup before touching the real site - a mockup you can feel beats any written description and saves significant rework.
- Give reactive feedback in concrete terms ('the folder is too wide,' 'lower the opacity') rather than vague impressions, since specific notes resolve in one round instead of five.
- Push every change to a preview link first and keep the public/production version untouched until the very end of the process.
- Feed the AI real source material - an existing bio, story, and social links pulled from wherever they're already stored - instead of asking it to guess who you are.
- Never let an AI model redraw a trademarked logo; composite the real logo file onto AI-generated artwork instead, since the model will reliably get it close but wrong.
- Treat animation as a two-stage process: get the still frame exactly right first, since iterating on a still is fast and iterating on generated video is slow and costly.
- Review every section on an actual mobile phone as a separate design pass, since a layout approved on desktop can crop the subject out of frame entirely on mobile.
- Favor real photos, videos, and logos over AI-generated substitutes wherever the content faces real people, since authenticity reads as trust on a personal brand site.
- Reserve a frontier or usage-capped model for the one big build, then shift routine maintenance and small tweaks to a standard, less usage-constrained model.
Terms worth knowing.
- Fable 5
- A Claude model variant used here as an integrated site-building tool - generating images, video, and hosting a live preview - distinct from using Claude purely as a coding assistant.
- Higgsfield MCP
- A Model Context Protocol connector that lets Claude generate and animate images into short looping videos, used here to create the site's hero background.
- Kit
- An email marketing platform; here it is wired directly into the site's newsletter signup form via its own MCP connector.
- 21st.dev
- A library of website component and section examples used purely for design inspiration, not for copying code or content.
- MCP (Model Context Protocol)
- A standard that lets an AI agent connect to external tools and services (like an email platform or image generator) so it can act on them directly during a build.
Things they pointed at.
Lines you could clip.
“I can't believe Claude's Fable five made me a website, an interactive one at that, and I have no web design experience.”
“Mock before you build. This is going to save you so much tokens if you just mock it up before you push it to the site.”
“Never let AI build your trademark. They'll always get it wrong.”
“I didn't know what I really wanted until I saw it come to life.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Nicky Saunders opens with a simple, almost incredulous claim: an AI model with no web design experience behind the wheel produced her fully animated personal site. What follows is not a highlight reel but a section-by-section replay of the actual prompts, decisions, and corrections that got her there.
Named ideas worth stealing.
The Repeatable Loop: Five Moves, Every Section
- Talk It Out
- Mock It Up
- React Specifically
- Port To Preview
- Review, Then Ship
The framework applied to every section of the site build: describe the feeling and reference without asking for a build yet, get a cheap throwaway mock to react to, give specific corrective feedback, push the approved version to a preview link, then review on both desktop and mobile before shipping to production.
Hard-Won Lessons
- Mock before you build - a mockup you can feel beats any description
- Never let AI draw your trademark - composite the real file
- React with specifics - 'too foggy,' 'push it right' - one round instead of five
- Keyframe before you animate - get that exact still frame right first
- Mobile is a separate design - review on a real phone
- Use real content - real photos, videos, faces, logos, not templates
A consolidated list of the practical rules learned the hard way during the build.
How they asked for the click.
“Get the full playbook - every phase, every prompt, ready to copy and swap in your own details. Go to the link in the description.”
Clean full-screen CTA slide with QR code and 'link in the description' button, delivered mid-video after the lessons recap rather than only at the very end, then reinforced again in the closing seconds.
































































