Drake Ng retweeted
clean cool collection of Carousel components
shadcnblocks.com/blocks/cove…
more like this on → shoogle.dev/fresh
Drake Ng retweeted
opus 5.5 is f*cking cracked at motion design
this entire video is code, 0 after effects
im open sourcing the prompt template for these motion designs
steal it to recreate these ↓
<inputs>
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).
</inputs>
<direction>
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.
</direction>
<structure>
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.
</structure>
<build>
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.
</build>
<gotchas>
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.
</gotchas>
<start>
Ask me for the inputs, then show me the state list on the beat grid before you write any code.
</start>
Drake Ng retweeted
Introducing Design Mode on v0:
• Quickly tweak your generation — copy, typography, layout, colors, styling, and more
• Preview changes and save when ready
• No need to spend credits or wait for an LLM
• Tailwind and shadcn native
Drake Ng retweeted
I watched Pantheon until its Season 2 finale. Uploaded intelligences; human minds emulated in a computer that can accelerate their thinking. What if they came about now?
The result is a hard scifi series I highly recommend, especially the epic ending.
amazon.com/Pantheon-Season-1…
Drake Ng retweeted
we just launched lovable 2.0 – and we want you to launch with us
build a 2.0 version of any product with lovable and quote this tweet with it
our favorite by monday wins $8k
Drake Ng retweeted
Since I open sourced my .mdc rules for Cursor I've been getting a lot of questions.
Here are all the answers in one place:
1. Isn't 20 mdc files too much information for Cursor?
No. This is what .mdc files solve. Cursor Rules file is now deprecated. You no longer provide all your information in one go, but in small chunks (.mdc files). Each of my .mdc files is <50 lines.
2. Do you need to manually tag Cursor?
There are 4 options for rules:
a. Always - the rule is part of every chat
b. Auto attached - e.g. auto attach whenever you're chatting about ".tsx" files, or "tailwind.config" file.
c. Agent requested - the agent can request to read the file. This is what I use most of the time. The agent decides whether to request a rule based on the description you set for the rule
d. Manual - only applied when tagging it.
I mostly use c. And I'll often tag the a rule file for Cursor myself as I'm not certain it will always read it otherwise.
3. How do I write the rules?
I have a cursor-rules.mdc that writes rules. Easiest way to do this:
* Share a snippet of code with Cursor (command-shift-L on relevant text)
* Tag the .cursor-rules.mdc file
* Ask Cursor to create a new .mdc file for this pattern
Pro tip" Cursor a little bit buggy here. I prefer to do this in Ask mode and copy the result into an mdc file. Sometimes you'll see Cursor show empty files when I do this in Agent mode.
4. Does it work?
Yes. Watch it in action at the end of the video (linked in next tweet).
If you let the AI do its own thing it will invent new patterns. A lot of the code we write is the same thing over and over (e.g. add a form, make an LLM call, add a server action that updates the db, etc.). There's no one right way to write code. But in your project there is. You want the code to be consistent. The code for each form should look more or less the same. Rules help Cursor do this effectively. (Tagging other code examples in your codebase is another way to do this, but .mdc is cleaner and less noise).
5. Is it worth the effort to set up rules?
Yes. It's a minimal, one-time effort to set up a rule. Especially once you have a base to work off of. And they provide value forever.
Cursor Agent is my no 1 employee. Giving it the context it needs to be as effective as possible is well worth the effort.
6. What rules do you use?
So far my rules can be broken down into a few buckets:
a. Code patterns (e.g. add a form, server action, or test)
b. General knowledge (e.g. project structure)
c. Features (e.g. this is what the inbox cleaner does and how it works)
Most of my rules fall under "code patterns". But I'm steadily adding more "feature" rules. I'm often repeating myself over and over to LLMs. I might be using Claude or Anthropic and I can copy paste in these notes now. And of course I can tag these notes in Cursor too.
If you want to see my rules in action, check out my YouTube channel or Inbox Zero GitHub. Links below.
Drake Ng retweeted
🎉 Introducing: Animated Gradient Background for @Framer.
Copy and paste into your project, select style from 6 presets or customize your own.
Retweet and comment "GRADIENT" and I'll send it.










