Ngulang kaayaan UI anu robah

Tanyakeun ka abdi kanggo: 8 dugi ka 12 kaayaan UI anu abdi pikahoyong pikeun bentukna (contona tombol, loader, pamuter, slider, toggle, tab, bagan, palét paréntah, roti panggang), hideung bodas murni atanapi hiji warna aksen, sareng lagu bébas royalti sakitar 120 BPM (contona Mixkit, gratis kanggo panggunaan komérsial).

Gerakan UI tingkat Dribbble. Hiji bentuk, teu pernah dipotong: unggal kaayaan mangrupikeun unsur anu sami anu ngarobih ukuran, radius sareng warnana sedengkeun eusina silih genti ku blur pondok. Kursor ngadorong unggal parobihan ku klik sareng sered anu nyata. Kanvas kulawu haneut hampang, komponén hideung bodas, hiji font UI anu bersih (Geist). Springs di mana-mana, paling-paling aya overshoot leutik. Kaméra ngazum supados unggal kaayaan ngeusian pigura. Pigura terakhir nyaéta pigura munggaran, janten éta ngulang.
Dilarang: ngurangan gerakan nu mantul, semburan partikel, cahaya nu caang, gradien dina UI chrome, goresan ikon nu teu cocog, waktu nu teu aktip, naon waé nu siga citakan.

120 BPM, 7 bar, aya waé anu kajadian dina unggal ketukan.
Tombol → pangunggah → cék → pulo dinamis → pamuter musik kalayan morf puter/pause → gosok bilah kamajuan → éta janten geseran volume anu manjang nalika diséréd ngalangkungan maks → toggle ngabalikeun dina ketukan → kenop janten indikator tab cair → tab muka kana bagan anu ngagambar sorangan, kalayan tooltip nalika ngalayang → éta runtuh kana ⌘K → tipe pikeun nyaring → lebet → toast → balik deui ka tombol.

1. Hiji file HTML, pasagi 1440x1440. Unggal gaya diitung tina waktos di jero seek(t): teu aya transisi CSS, teu aya timer, teu aya status anu dibawa antara pigura.
2. Springs nyaéta réspon léngkah bentuk katutup. Nilai anu ngarobih target sababaraha kali nyaéta jumlah hiji spring per parobahan, janten tetep fungsi murni waktos.
3. Dua sisi indikator tab nganggo pegas anu béda, janten sisi hareupna manjang ka payuneun sisi tukangna. Trikna sami pikeun kenop toggle.
4. Sered nyaéta manipulasi langsung: nalika kursor ditahan, nilaina diitung tina posisina. Nalika dileupaskeun, éta bakal muncul deui ti tempatna asalna.
5. Analisis lagu nganggo numpy pikeun grid ketukan teras mimitian ku ketukan handap. Tempatkeun unggal sora UI dumasar kana puncak anu diukur.
6. Render nganggo Playwright: 4 subframe per frame, dicampur sareng ffmpeg tmix kanggo motion blur dina 60fps.
7. Render hiji pigura per ketukan sateuacan render pinuh. Koreksi naon waé anu teu nyambung, sempit atanapi hésé dibaca.

Ulah pernah nempatkeun "will-change" dina naon waé anu diskalakeun ku kaméra atanapi téksna janten burem. Téks anu robah dina wadah anu robah peryogi waktos asup sareng kaluar sorangan atanapi éta bakal tumpang tindih. Jieun pigura terakhir sami sareng anu munggaran, posisi kursor sareng kecepatan kalebet, atanapi loop bakal gagap.

Pék tanyakeun inputna ka abdi, teras témbongkeun daptar kaayaan dina beat grid sateuacan anjeun nyerat kode naon waé.

Ask me for: 8 to 12 UI states I want the shape to become (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), pure black and white or one accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use).

Dribbble-level UI motion. One shape, never cut: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, a tiny overshoot at most. The camera zooms so each state fills the frame. The last frame is the first frame, so it loops.
Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template.

120 BPM, 7 bars, something happens on every beat.
Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it becomes a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs open into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button.

1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state carried between frames.
2. Springs are closed-form step responses. A value that changes target many times is the sum of one spring per change, so it stays a pure function of time.
3. The tab indicator's two edges ride different springs, so the leading edge stretches ahead of the trailing one. Same trick for the toggle knob.
4. Drags are direct manipulation: while the cursor is held, the value is computed from its position. On release it springs back from wherever it was.
5. Analyze the song with numpy for the beat grid and start on a downbeat. Place every UI sound by its measured peak.
6. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps.
7. Render one frame per beat before the full render. Fix anything off the grid, cramped or hard to read.

Never put will-change on anything the camera scales or the text renders blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the last frame identical to the first, cursor position and speed included, or the loop stutters.

Ask me for the inputs, then show me the state list on the beat grid before you write any code.

Pitunjuk dicandak tina pos @demonugc.