Source: raw/Simple_System_for_Better_Websites_with_Claude_Design.md

Creator: Futurepedia URL: https://www.youtube.com/watch?v=TErjuicvK_c Duration: 17:22 Platform: YouTube Published: 2026-09-02

Futurepedia’s six-step method for getting a non-generic website out of Claude Design: Reference, Explore, Synthesize, Explode, Expand, Build. The idea is to stop Claude from settling on its default layout. You ask for six different homepage directions, combine the parts you like using comments, then use the Tweaks panel to generate many variants of every component and interaction inside that one direction. Only then does Claude build the other pages and hand off to Claude Code for deployment. His line: “you don’t avoid AI design slop with a magic prompt. You use a system.” This complements Eliot Prince’s brief-first playbook, published the same day, which puts the effort into the brief and copy. This one puts it into generating many options and choosing between them.

Recorded before the September merge

The video was published 2026-09-02 and uses the standalone claude.ai/design site. Since 2026-09-16, Design also works inside ordinary Claude conversations, and the standalone site stays up until 2026-12-14 (see Claude Dashboards and Motion § Claude Design migration). The steps below should carry over, but the menu paths may have moved.

Key Takeaways

  • The six steps, in his words: Reference (curate a style board that gives Claude taste), Explore (generate multiple directions instead of accepting Claude’s default), Synthesize (combine the strongest ideas into one direction), Explode (explore components, styles, details and interactions inside that direction), Expand (build the remaining pages from the visual language you set), Build (hand off to Claude Code and turn it into production software).
  • Reference: 2 to 5 sites, each with a note on what to take. “The typography from A, hero composition from B, navbar from C.” Add specific fonts, palettes or components, plus your real assets (logo, product shots, headshots) so Claude designs around the actual product. His sources: Lapa Ninja (filter by business type or style), Land-book, Awwwards (3D and immersive scrolling), Pinterest (broad inspiration; follow the related results), and React Bits and 21st.dev for single components. These are added to Design Inspiration Galleries.
  • Explore: ask for six directions, not one site. His prompt (in his free guide) fills in business, product and core features, says what each product image is and that it should be used as is, then says to use the references “as inspiration, but do not reproduce any one site”, to “synthesize the strongest ideas… rather than averaging them together”, and to “create six meaningfully different home page directions, not six color variations of the same layout”. It lists dimensions to vary: hero composition, typography, negative space, navbar treatment, asymmetry, grid breaks. Without that prompt, he says, “I could run that 10 times and I’d get back basically the same site every time.”
  • Synthesize with comments, not a new prompt. He expected no single winner. In Comment mode he clicked each element he liked across the six options, left a note on it, then asked: “Make a new option that incorporates the elements each of my comments are attached to.”
  • Explode with Tweaks. “Commit to 2A as the base direction… build that and incorporate many tweaks for me to explore,” followed by a pasted list of things to vary. The result is one page with dropdowns for nav style (glass pills, minimal inline, bordered rail, centered logo), hero layout, product presentation, feature layout (he chose bento), CTA bar, and under More: button fill and shape, card styles, spacing, text size, background, accent colour. Edit mode still gives manual control. He calls Tweaks plus Edit “what makes this way better for designing than Claude Code.”
  • A second explode pass for interactions. Prompt for tweaks covering hover states, button presses, scroll-triggered reveals, subtle parallax and so on. His rule: “one big one, everything else subtle.” His signature interaction, an audio waveform under the CTA that reacts to the cursor, came from an option Claude proposed because the product was a video editor (playhead, timecode ticks, waveform). He kept asking for variants of it (slower, then cursor-reactive).
  • Repeat from macro to micro. You can explode again around the options you selected, as many times as you want. Use Present → New tab to see the page as a visitor would.
  • Expand: the homepage is the source of truth. “Lock in everything we have and build out the other pages,” one per nav item. He did no iteration on the other pages, and they kept the same type, cards and components. Make a formal design system only when you need the visual language across projects or a team. For one site, the homepage is enough.
  • Build: download the zip as well as the prompt. Share → More formats → Claude Code gives a prompt, but he says pasting it alone “I run into issues a lot”, so he downloads the zip, unzips and renames the folder, and assigns it as the workspace in the Claude desktop app’s Code tab. Then he deletes the line telling Claude to fetch from Design over MCP, since the files are already local. This matches the zip preference in the July walkthrough.
  • Deploy from inside Claude Code. Connect the GitHub and Vercel connectors (both free accounts), then say “Push it to GitHub” and “deploy with Vercel”. In his run, Claude Code found and fixed build bugs during the Vercel step without being asked. Database, auth, payments and APIs come after this, in Claude Code.

Try It

  1. Build a taste board before opening Design. Pick 3 references from Lapa Ninja, Land-book or Awwwards and write one line per reference on what to take from it (“hero composition only”, “nav only”). Add your logo and one or two real product images.
  2. Ask for six directions. Use the prompt shape above: product facts, what each image is, “do not reproduce any one site”, “six meaningfully different home page directions, not six color variations”, plus the list of dimensions to vary.
  3. Comment on the best parts, then merge. Leave comments on the elements you like in any of the options, then ask for a new option that combines the elements your comments are attached to.
  4. Explode twice. First the layout and components (“commit to X as the base direction and incorporate many tweaks”), then interactions. Keep one signature interaction and make the rest subtle.
  5. Expand, then hand off with the zip. Ask for the remaining pages from the locked homepage. Download the zip, open it as a Claude Code project, remove the fetch-from-Design step, build, and deploy through the GitHub and Vercel connectors.

Implementation

  • Tool/Service: Claude Design (included with paid Claude plans, per the video), Claude Code in the Claude desktop app, GitHub and Vercel connectors.
  • Setup: Free GitHub and Vercel accounts, both connected as Claude connectors before the deploy step.
  • Cost: No figures given. The six-direction and explode steps produce many full variants per turn, so expect them to use more of your plan’s usage than a single-site prompt.
  • Integration notes: His product images (logo, UI hero, feature image) were generated in ChatGPT for the demo. He notes that AI-made assets push the result back toward an “AI feel”, so use real assets where you have them. His prompts for this and other Claude Design use cases (pitch decks, landing page from competitor screenshots, social templates, and the motion graphics prompts behind Claude Design animations) are in a free guide linked from the video. The guide wasn’t fetched for this article.

Open Questions

  • The full text of the explore and explode prompts is only paraphrased on screen. The free guide holds the exact wording and wasn’t retrieved.
  • How much usage a six-direction generation takes is not stated.
  • Whether Tweaks, Comment and Present work the same way in Design inside ordinary conversations (after the 2026-09-16 merge) as on the standalone site is not covered here.
  • Licensing of React Bits and 21st.dev components for client work is not covered (same gap as Power-User Tricks).