Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Claude Sonnet 5.5 is Incredibly efficient for web deisgn. Built a North Face concept site with live rain physics, a 3D jacket that gets wet as it pours, and a full checkout flow. Demos and tutorial below 👇

56,538 Aufrufe • vor 27 Tagen •via X (Twitter)

11 Kommentare

Profilbild von Viktor Oddy
Viktor Oddyvor 27 Tagen

I've uploaded all prompts from this video on Access 500+ website prompts. 100+ 3D scenes, 100+ interactive gradients, 300+ backgrounds, motion sections. Everything's a prompt.

Profilbild von WeornW
WeornWvor 26 Tagen

claude cant be stopped atp

Profilbild von Faheem Ur Rehman
Faheem Ur Rehmanvor 27 Tagen

Its been a while when this 3d idea came to web designers and now its everywhere, actually its common nature that people love to interact things like this which have any interesting factors..!

Profilbild von Eamin
Eaminvor 27 Tagen

Taste still decides the final look.

Profilbild von Kaitlyn Olivah
Kaitlyn Olivahvor 27 Tagen

The jacket getting wet is the part people can’t fake with one prompt. Checkout staying in the same world is what makes it feel like a real site.

Profilbild von avangard
avangardvor 27 Tagen

This looks like the new standard — brands will soon switch to dynamic websites like this at scale.

Profilbild von Rohit
Rohitvor 26 Tagen

Good video. One line caught my attention. You said figma has no future. Sure, but then people like me who are entering UI UX for the love of design.. shouldn't they be using figma to learn stuff and create things on their own first? Just like how you have done for over 10 years and developed a taste for design!

Profilbild von ged
gedvor 26 Tagen

Jolie site web

Profilbild von Zane Campbell
Zane Campbellvor 26 Tagen

As far as web design, do you find that Sonnet 5.5 is better than Opus 5.5? Or are they relatively the same? I am currently using Opus, so I want to get your feedback.

Profilbild von NAXXtech𝕏
NAXXtech𝕏vor 27 Tagen

Better than Opus 5.5 in your opinion?

Profilbild von Rudra
Rudravor 27 Tagen

Really nice work! 🔥

Ähnliche Videos

This workflow will save you thousands with Claude. Run Opus 5.5, Sonnet 5.5, Haiku 5.5, and Fable 5.1 together, and stop spending Opus tokens on work that doesn't need Opus. The entire idea in one line: Opus plans, Sonnet edits, Haiku reads, Fable reviews at decision points. Roles, broken down: - Opus 5.5, high effort, owns the plan and reviews the final code - Sonnet 5.5, medium effort, is the worker: edits files, runs tests - Haiku 5.5, low effort, splits into explorer (searches and reads the codebase) and researcher (pulls docs). it's the first Haiku with an effort setting - Fable 5.1, set with /advisor fable. Opus calls it at decision points, and it gets the full transcript each time Three moments Opus tends to call it: → before committing to a plan: is this the right approach? → the same error shows up again: is this going nowhere? → before marking the task done: did something get skipped? Why Haiku only reads: Anthropic's launch post says Sonnet 5.5 and Opus 5.5 are still the better choice for complex agentic coding (Terminal-Bench 4.0: 39.2% for Haiku 5.5, 70.6% for Sonnet 5.5) and that Haiku 5.5 fits narrowly scoped subagent work. so it gets the lookups, not the edits. Anyone still running one model for everything is paying $4 per million input tokens to check whether a file exists. Haiku 5.5 does it for $0.10. Drop this into Claude Code 👇 "Rebuild my Claude Code setup around this structure: Confirm Claude Code is v2.1.293 or later, so the haiku alias resolves to Haiku 5.5. If it isn't, stop and tell me to run claude update. Look through ~/.claude/agents and .claude/agents for subagents already covering explorer, worker, and researcher. Only create new ones for roles that are missing. Set model: haiku, effort: low on explorer and researcher, with no Edit or Write tools. Set model: sonnet, effort: medium on worker. If an existing subagent is locked to a different model, leave it as is and just list it. Name the explorer subagent Explore so it overrides the built-in one, which otherwise runs on my main model. In ~/.claude/settings.json, set advisorModel to fable, and set effortLevel to high for claude-opus-5-5 under modelSettings. A top-level effortLevel in user settings doesn't apply to Opus 5.5. Check for anything disabling the advisor: CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, or anything blocking feature-flag fetches. Also check CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort settings, and CLAUDE_CODE_SUBAGENT_MODEL_FORCE, which makes Claude Code ignore subagent model fields. Report what you find. Don't change any of it yet. Add one line to ~/.claude/CLAUDE.md: consult the advisor before a big plan, when the same error shows up twice, and before marking a long task done. Show every change as a diff first. Wait for my go-ahead before touching anything."

Alvaro Cintas

56,940 Aufrufe • vor 18 Tagen