Refine & Render (@refineandrender) header
Refine & Render (@refineandrender) profile picture

The best of design engineering, shared daily.

Read newsletter →
Joined November 2026
Agree, as long as I can still read what the prompt does before it touches my repo. npm install never edited my layout file.
This is how quick start guides for libraries in 2026 should look like. Just show me the prompt. Showing the npm install command is a thing of the past.
The useful part is the list of changes that still block on a second human. Auth, infra, deploy config. Write that list before you copy the 53%.
In January, almost every PR at Linear had a second human reviewer. By October, 53% were reviewed by an agent and the author alone. We’ve become more deliberate about where human attention goes. Here’s what we’ve learned: linear.app/data/code-review
1
Bookmarking for the scroll-driven mask fade alone. Most tab bars just clip the last tab in half and hope you figure it out.
As promised, here's the scrollable tab UI design in detail. This one is tricky because it involves a lot of nuances: 🖱️ Horizontal scrollbars look bad, but if you hide them, mouse users will have a hard time scrolling. 📱 Touch devices don't need a scrollbar, but if you don't clearly show that there are more items to scroll to, users might not even try. One solution is to fade out the edges of the viewport when there are more items. You can do this purely with CSS (mask and scroll-driven animation). 💻 On desktop, you can conditionally render chevron buttons. But users may not realize they've reached the end and misclick the element underneath. To prevent that, keep the scroll button disabled at low opacity while it's hovered. Then just remove it once the pointer moves away. All it takes is CSS hover, scroll-driven animations, and a little bit of JS for the scrolling itself. ⌨️ Keyboard focus must skip the chevron buttons and the fade-out. You can do this with CSS scroll-padding.
1
Using the seasons behind the same row of gummies to show time passing is such a good journaling idea. No dates, no streak counter.
a sneak peek at the visual concepts i've been developing for a journaling app currently in the works 🌝 made with SwiftUI Canvas & metal shaders. turn on sound for the full experience 👯‍♀️👯‍♀️
1
Too much for the 50th import, perfect for the first one. The scanner sweep landing on each frame in sync with the counter is the bit I'd keep.
Be honest, is this too much?
3
The highlights shifting with the cursor are what sell the glaze. Strong pick for 003.
make it pop: 003 glazed
3
15
"Or your own" is carrying that design system list. Curious how much of a real component library survives the swap.
We built an A2UI playground Ask the agent for anything and watch it build live, interactive UI. - See the A2UI it writes, line by line - Swap design systems: shadcn, Material, or your own - Copy one prompt to add it to your app a2ui.open.bot
1
10
Swapping the colors was always the easy half. Redoing every image so it doesn't look pasted onto the light theme was the week of work, and that's the part they handed to the agent.
The Framer website went from dark mode to light mode in just a few minutes using one simple skill, with the Agent handling everything from switching the colors to using image generation to create new images that match the light theme, all without changing the original design.
1
10
Refine & Render retweeted
Introducing 𝚡𝚎𝚎𝚝: xeet-rs.vercel.app. A hermetic, pixel-perfect X post renderer in safe Rust / wasm. Zero browser, network, filesystem, system fonts. Renders a post to PNG in ~1ms (and 0.4 ms for @jack's "setting up my twttr" 😁). X is the global town square, and the medium is the message. Being able to preview what things will look like before posting is great for both humans and agents. Rendering with xeet is is 100x-1000x faster than booting up a browser and taking a screenshot, yet it's just as accurate. It reproduces Blink & HarfBuzz text shaping, 1/64px line breaking, RTL bidi, 28 Chirp font subsets, CJK/Math/Emoji fallbacks, "Show more" rules, etc. It's the kind of thing that would be wildly impractical, if not impossible, for a human engineer to pull off. Except 𝚡𝚎𝚎𝚝 is structured as an "autorepo." An oracle boots up Chrome, and verifies tens of thousands of text layout rules. A CI canary then watches the evolution of the original, and files signed PRs for agents to act on. It was conceived from the ground up around 'verification engineering', and the result speaks for itself. Enjoy!
221
123
42
2,531
181,866
Refine & Render retweeted
Introducing json-render for Swift Generative UI, now native on iOS and macOS → Renders with SwiftUI → Bring your own components → Same JSON specs as the React renderer → State, bindings, actions and visibility rules
67
55
11
1,177
48,762
👀
Introducing iOS for the web. This is Telegram (written in Swift and Objective-C), running fully in a browser on our custom renderer. No emulator, No iPhone required. You can infinitely branch the entire codebase by copy pasting a frame and make changes to each frame. We built a compiler+renderer (in Rust) that allows you to easily design on top of a native iOS codebase. Most edits land in under a second and is much much faster then xcode builds. Our goal is to take any codebase and turn it into a design environment that fully runs in your browser!
10
Turned the sound on. The un-crumple when you hit undo is the best part.
Turn on sound :D
7
The radii scaling with the spring overshoot is the detail. 12 at rest, 20 at the peak, and the bottom curve flips convex on the bounce. Most tab indicators just slide a rectangle and call it done.
Tabs UI design in detail. I'm thinking about a separate post on the scrollable version. When tabs overflow, the list scrolls without a visible scrollbar, and chevron buttons appear only on the sides with hidden tabs. There are a lot of details I didn't cover here.
3
Teenage Engineering energy. Now the real argument starts: should the knobs turn on vertical drag or circular drag.
SPEC-01 just dropped.
3
Filter 2 is doing a lot of work. "Seems trivial" is how a one line CSS fix turns into a layout regression on three other pages. I'd want visual diffs gating that PR.
step one of software factory is in-app "send feedback" dialog. submit -> creates github issue. a bot in a loop looking at only issues 1) from you or your team, 2) that seem trivial to fix, and 3) have enough context for bot to create and land a PR itself
3
Unsubscribe flows are taking notes.
the impossible toggle ┬┴┬┴┤ʕ•ᴥ├┬┴┬┴
3
Agents get you the first draft. Someone still has to care this much about the last one.
Fixing a Claude-generated UI with obsessive attention to detail.
3
Same guarantees, different widgets is the right split. The test I'd run: type 13/45 into whatever the agent drew and see if it still says no.
You and I don’t need the same interfaces. We need the same interface behaviors. Your agent might generate a calendar to pick a date. Mine might generate a simple input. Someone else’s might come up with something completely different. That’s fine. The interfaces can be different. The underlying guarantees should be the same. That’s what we’re building UI SDK for.
3
Put this in your tokens once and you never eyeball a nested card again. calc(outer - padding) is the whole rule.
Design engineering tip: your inner corners bulge out of the card Inner radius is outer minus padding border-radius: calc(28px - 10px)
3
Finally a reason to look at my disk usage on purpose.
storage scanner so good you'll want to fill your disk.
4