Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

claude opus 5.5 completely solved three.js it took a floor plan and turned it into a 3d house you can walk through home builders pay $5k to $10k per floor plan for this, so buyers can tour a home before it's built and change things if needed here's how...

299,491 görüntüleme • 2 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

This is f*cking insane. This tip saved me thousands of dollars. run Opus 5.5, Sonnet 5.5, and Fable 5.1 together, and stop burning Opus on work it was never needed for. the whole idea in one line: the strong model plans, the mid-tier model executes, Fable stays quiet until it's actually needed. roles, broken down: Opus 5.5, high effort, owns the plan and ships the final code Sonnet 5.5, medium effort, splits into explorer (reads the codebase), worker (edits files, runs tests), researcher (pulls docs) Fable 5.1, called through /advisor fable, reads everything happening in the session but stays silent unless something's actually wrong three moments where Fable speaks: → a plan goes out: is this actually the right call? → the same failure shows up again: is the search going nowhere? → the task gets marked finished: did something get skipped? Jev engineering does the same thing one level down. the forks that don't need real thought, which file, which tool, keep going or stop, go straight to Jev and come back in under half a second. the big models only ever see the forks that genuinely need a decision. anyone still running one model for everything is paying Opus prices to decide whether a file exists. drop this into Claude Code: "Rebuild my Claude Code setup around this structure: 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: sonnet, effort: medium on each. If an existing subagent is locked to a different model, leave it as is and just list it. In ~/.claude/settings.json, set effortLevel to high and advisorModel to fable. Check for anything disabling the advisor, CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, or anything blocking feature-flag fetches, plus CLAUDE_CODE_EFFORT_LEVEL, which can override subagent effort settings. Report what you find. Don't change any of it yet. Add one line to ~/.claude/CLAUDE.md: check in with 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."

rvaniaaa

253,200 görüntüleme • 13 gün önce

everyone's sharing motion graphic videos that Opus 5.5 made, and it's genuinely insane everyone says they created it with "one prompt", but my one prompt video looked mid so i went through a bunch of these videos to see how they were actually made, and found the workflow that works here's how to generate pro level motion graphic videos w/ opus: 1. get reference videos to direct from -> pick 1-2 videos whose style you want and tell opus to match them. naming a style works way better than describing one without a reference, opus falls back to its default look: centered text, gradient background, everything fading in that's why so many of these videos look the same. a reference gives it the pacing, the type and the transitions to copy 2. install HyperFrames or Remotion so opus can build the video both let opus write every scene as code and render it straight to mp4. no video editor without one, opus can only describe a video or hand you a rough html page you have to screen record with it, every frame is exact, and when you ask for a change it edits one line and re-renders instead of starting over 3. install 21st for high quality components in the video real buttons, cards and UI components made by design engineers, instead of whatever opus invents on the spot without it, opus draws your product UI from scratch and it looks off. wrong spacing, placeholder boxes, fake-looking buttons anyone who's used good software can feel it in a second, and the whole video reads as cheap 4. steps 1-3 were context + setup. now dump all of it into opus your brand (logo, colors, fonts), screenshots of your real product, the reference video, and a quick braindump of how you see the video then ask for 3 storyboard variants without this, opus guesses your colors, your font and what your product even does. the video could be for any startup with it, it could only be yours. and 3 variants means you pick a direction instead of fixing the first idea it had 5. pick the storyboard you like ask for one still frame per scene before anything moves. fixing a storyboard is way cheaper than fixing a render without this step, you only find out scene 4 is wrong after the whole thing is animated, and every fix means re-rendering. a still frame takes seconds to change 6. let claude cook then give notes like a director: "slow every zoom to 0.7x", "hard cut here", "push in on the button" without notes, the first render is usually 80% there, and that last 20% is what makes it look pro. vague notes like "make it better" get random changes. camera words get exactly the change you want everyone has the same model. the context you give it is what makes it look pro let it cooookk

Rexan Wong

636,058 görüntüleme • 19 gün önce