Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

This week in Osmo in Use, we’re featuring Get Hyped, build by Dylan Brouwer and Kevin Masselink. Here’s what he used: 1. Play Video on Hover (Lazy) 2. Live Form Validation (Advanced) 3. Osmo Scaling System 4. Dynamic Current Year 5. Lenis Smooth Scroll Setup

12,720 Aufrufe • vor 10 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

FABLE 5 + HIGGSFIELD TURN A $35,000 ANIMATED SITE INTO A ONE-SESSION, $12 BUILD. HERE'S EXACTLY HOW. a studio runs this across four people and three weeks. you run it across one chat window and one afternoon. THE BUILD, STAGE BY STAGE: STAGE 1 - THE CONCEPT Claude reads your brief and scripts the scroll before a line of code exists - what the visitor feels at second 3, 15, 40. prompt: "read this brief. script the scroll beat by beat, then scaffold the project with GSAP ScrollTrigger + Lenis." STAGE 2 - THE VISUALS (Higgsfield) every hero shot, transition, and ambient loop comes out of 30+ generative models - matched to the story, not pulled from a stock library. prompt: "generate the hero sting and one b-roll clip per section. 3-5s, high-res, cinematic." STAGE 3 - THE MOTION (Claude Code) Claude writes the ScrollTrigger timelines and Lenis smooth-scroll, extracts frames, optimizes every asset. zero hand-coded keyframes. prompt: "wire the scroll: pin the hero, scrub the video, reveal each section on scroll. keep it 60fps on mobile." STAGE 4 - THE POLISH six cinematic effects baked in, no config: film grain, particles, vignette, glass cards, color tints, scroll pacing. prompt: "bake in the cinematic layer, then QA load speed, mobile breakpoints, and whether the scroll actually lands - rewrite what doesn't." CONNECT HIGGSFIELD (MCP): add it as a custom connector in Claude Code: mcp_servers: higgsfield: url: " one OAuth flow. Claude generates and pulls clips directly - no exporting by hand. THE MATH: → what a studio charges: $6,000-$35,000+ → what it costs you: a Claude sub + a few dollars of Higgsfield credits → what it takes: 4 people + 3 weeks → 1 operator + 1 session the pipeline was the moat. it just became four prompts. Follow me, comment "MATH" and I'll send you the full step-by-step Playbook. full breakdown in the article 👇

ZEUS⚡️

47,174 Aufrufe • vor 1 Monat

FABLE 5 + HIGGSFIELD CAN BUILD A $35,000 ANIMATED WEBSITE. IN ONE AGENTIC SESSION. FOR ~$12 IN CREDITS. stop paying a web studio $6,000-$35,000. stop wiring GSAP, Lenis, and frame extraction by hand. Claude Code writes it. Higgsfield renders it. WHAT THE BUILD PRODUCES: → a fully animated, scroll-driven site → cinematic motion clips from 30+ generative models → GSAP ScrollTrigger timelines - zero hand-coded keyframes → Lenis smooth-scroll, tuned pacing → automated frame extraction + asset optimization → six cinematic effects baked in: film grain, particles, vignette, glass cards, color tints, scroll pacing → responsive layout + copy THE STACK: → Claude Code - concept, scaffolding, scroll code, QA → Higgsfield (MCP) - hero clips, transitions, ambient loops, thumbnails → GSAP + Lenis - the motion layer, written for you CONNECT HIGGSFIELD (MCP): add it as a custom connector in Claude Code: mcp_servers: higgsfield: url: " one OAuth flow. done. now Claude can generate and pull clips directly - no manual exporting. WHAT TO PROMPT: concept + scroll: "read this brief, script the scroll - what the visitor feels at second 3, 15, 40. scaffold the site with GSAP ScrollTrigger + Lenis." motion assets: "generate the hero sting and one b-roll clip per section from the story. 3–5s, high-res." polish pass: "bake in film grain, particles, vignette, glass cards, color tints, scroll pacing. no config." QA: "check load speed, mobile breakpoints, and whether the scroll actually lands. rewrite whatever doesn't." WHAT THIS REPLACES: → web studio build: $6,000-$35,000+ → motion artist: $800-2,000/project → front-end dev: $2,000-10,000/project → weeks of handoffs: gone Fable 5 + Higgsfield: a subscription + a few dollars of credits. one session. SETUP IN 10 MINUTES: - install Claude Code - add the Higgsfield MCP + authenticate - drop your brief + references - let it scaffold, generate, and animate in one pass - preview, send fixes in plain English, ship the pipeline was the moat. it just became a prompt. Follow me, comment "WEB" and I'll send you the full step-by-step Playbook. full breakdown in the article 👇

ZEUS⚡️

566,344 Aufrufe • vor 1 Monat

THIS GUY JUST REBUILT A $35,000 ANIMATED SITE FOR $12. IF YOU RUN A WEB STUDIO, YOU SHOULD PROBABLY KEEP SCROLLING. Every agency billing $100-149/hr is selling you five departments wearing one invoice. Here’s each one - collapsed into a single agentic session. LAYER 1 - THE CONCEPT ROOM (Claude) Reads the brief, pulls references, and scripts the scroll: what the visitor feels at second 3, second 15, second 40. → Used to be a strategist and a wall of mood boards. Now it’s a conversation. LAYER 2 - THE MOTION STUDIO (Higgsfield) Cinematic clips from 30+ generative models - hero shots, transitions, ambient loops - all matched to the story from Layer 1. → Used to be a motion artist on retainer. Now it’s a prompt. LAYER 3 - THE DEV TEAM (Claude Code) Scaffolds the site, writes the GSAP ScrollTrigger timelines and Lenis smooth-scroll, extracts frames, optimizes every asset. → A full scroll-driven build with zero hand-coded keyframes. LAYER 4 - THE DESIGN DEPT (baked-in cinematic layer) Six effects, zero config: film grain, particles, vignette, glass cards, color tints, scroll pacing. → The polish that justified the invoice - now it ships by default. LAYER 5 - THE QA PASS (Claude) Checks load speed, mobile breakpoints, and whether the scroll actually lands - then rewrites whatever doesn’t. → Used to be a client call and a revision cycle. Now it’s one more turn in the same session. Five departments. One operator. One pass. A strategist, a motion artist, a developer, a designer, and a QA lead - weeks of handoffs - now run in a single session. For a Claude subscription and a few dollars of Higgsfield credits. The studio was never selling talent. It was selling overhead. And the overhead just became five layers. Follow me, reply “website” to this post and I will send you the step-by-step Playbook 👇

ZEUS⚡️

141,226 Aufrufe • vor 1 Monat

004/100 Buttons. A bit of the process on building an animation. When looking at a finished animation or in this example a finished button, it can look quite complex inside the CSS. But when building it, it’s more like a lot of simple steps, one after another. Here I had the idea to make some kind of text animation like the footer logo on the Osmo site. I try to add the base animation with no complex easing, for example transition: translate 0.4s ease. Starting with just moving the one text from bottom to top and the other text to top. Adding a stagger, play around with it. Searching for a way to make it more circular. On the research I found the sin() function inside CSS which can build a more smooth non linear curve for the stagger which creates this circular effect. And step by step adding more complexity like, different easing for hover/hover-out, opacity, 3D transform and more. I use also the sin() function to rotate the letters, so the middle ones are getting more rotated than the outer ones. Another thing which helps is to add a small delay on hover, for example 0.05s or 0.1s, you don’t really see the difference, but when you hover pretty fast on and out it doesn’t get that jumpy. I’m using here GSAP’s SplitText to split every char into spans. And then I’m adding a CSS index variable to every span, starting from the center. SplitText can provide CSS index variables, but you cannot tell it from which direction. For the sin() it’s also important to have a max length, so I add another CSS variable with the max char number on it. Crafting 100 Buttons with Osmo ⏳ Total time: 63h

Eduard Bodak

166,023 Aufrufe • vor 3 Monaten

MLP in PyTorch by hand ✍️ ~ 7 steps walkthrough below Goal: fill in every blank in the PyTorch code to build a multi-layer perceptron. 1. Given Let us start with a code template on the left and the network it is supposed to build on the right. Every blank in the code can be worked out from the picture. 2. Linear layer We count: 3 features in, 4 features out. So the weight matrix is 4 by 3. There is an extra column for the biases, which means bias = T. 3. ReLU Let us apply the activation. ReLU crosses out the negatives, so -1 becomes 0. 4. Linear layer The input size is 4, because that is what the previous layer put out. The output size is 2. A 2 by 4 weight matrix, and this time no extra column, so bias = F. 5. ReLU We cross out the negatives again. 6. Linear layer Two features in, five out. A 5 by 2 weight matrix, with a bias column, so bias = T. 7. Sigmoid Let us finish. Sigmoid squashes the raw scores (3, 0, -2, 5, -5) into probabilities between 0 and 1. You have just implemented a three-layer deep neural network by hand. ✍️ == Story == Three years ago I gave this exercise to my students, to connect the code to the math. They found it odd. Every other AI course they were taking lived inside a Jupyter notebook, and here I was handing out paper. Three years later, my colleagues are the ones rushing to move their materials to paper. The exercise has not changed. Paper still asks the one thing a notebook lets you skip: do you actually understand what the code is doing? If you can tell me why the weight matrix is 4 by 3, and why bias is F on the second layer, you understand nn.Linear better than someone who has been copy-pasting it for a year. 💾 Save this post! #AIbyHand #PyTorch #DeepLearning

Tom Yeh

13,318 Aufrufe • vor 1 Monat