In light of what happened, I'm doubling down on skills like /improve. A frontier model got pulled. If it happened once, it's gonna happen again. Fable today. 4.9 tomorrow or maybe gpt 6 one day. So, treat intelligence as borrowed. Drain intelligence when it's available. Build a catalog of plans today. Then implement later with a cheaper, open source, or a model you control. Build the backlog now. github.com/shadcn/improve

The collaboration with shadcn goes to the next level 🙏! We work on Base UI to provide the ultimate unstyled foundation for UI. Seeing it power shadcn/ui by default feels like a great win for the community. It's also an important milestone for the team, a testament to their incredible work: @colmtuite, @michaldudak, @atomiksdev, @aarongarciah, @jjenzz, and others 🖤

OH: "Instead of AI taking my job, I now work two jobs to pay for Fable" 🙃

Woah thank you for the incredible video @_remocn and @kapish_dima. Amazing project.

If Cape Verde almost took me out, I am not going to survive another Argentina-France…

The Shadcn ecosystem is one of the best things happening in the dev world. So many incredible builders. So many amazing open source projects. Proud to be a small part of it. 💚⚔️

A year ago we wrote: "The component library is just one layer of shadcn/ui. And if it ever comes to it, a swappable one." We are here. Read the changelog. ui.shadcn.com/docs/changelog

We spent a lot of time working on this skill. It handles your custom variants, your changed classes, your added props. Your agent is given a radix-to-base mapping. It reads your code, figures out what you changed and carries it over. And when it's done, it produces a migration report for each component: what changed, what was not and how to verify. All in your git history, so any agent can pick up any day and continue.

When you're ready to migrate, we built a skill for you. ~ npx skills add shadcn/ui Then ask your coding agent: "migrate alert-dialog to base ui" It's progressive: migrate one component at a time while your project stays green. Stop halfway, ship, come back next week. It picks up where you left off.

What this means for you? Radix is not being deprecated. We still support it, and every update and new component will ship for both libraries (unless a component only exists in Base UI). You do not need to migrate. Radix is a mature, tested library. We still run it in production today. If your app works, keep it.

What's changed? - New projects with shadcn init now default to Base UI. - shadcn/create shows Base UI as the default option. - Docs default to Base UI. Radix docs are one click away.

Everything we were waiting on happened. Base UI is stable. It's at 1.6.0 with 6M weekly downloads. It keeps getting better. The team ships new and useful components regularly. We use it. Every new project we've started runs on Base UI. You use it. Projects created on shadcn/create now pick Base UI over Radix 2 to 1. The community made the call. We're making it official.

When Base UI hit beta, a lot of you asked if we'd replace Radix. We said not yet. Then 1.0. Still not yet. Instead, we did the shadcn thing: we shipped shadcn/create with Base UI support, recreated every component, rewrote all the docs and let you choose: Radix or Base. And we watched what you did.

Starting today, we are making @base_ui the default component library in shadcn/ui. First, a bit of history. When shadcn/ui launched in 2023, it was built on Radix. At the time, nothing else came close. Headless. Accessible. Composable. Fast forward a few years and the team who built Radix are building something new: Base UI.

tech bro you haven't heard from in months

We are going to make one big change to shadcn/ui this week.

Thank you to all my GitHub sponsors.

If you want to add a navigation trail to your own chat app, the new MessageScroller component has the hooks you need out of the box. Look for: const { currentAnchorId, visibleMessageIds } = useMessageScrollerVisibility()

Sometimes I leave out context and just sit and watch the agents struggle. Reminds them who's still in charge.

I didn't expect this tweet to be controversial. But here we are. Okay so look at the most popular apps you use every day. Now think about what they looked like two years ago vs today. They're all converging on the same three panels. An explorer on the left. A chat in the middle. A preview on the right. Look at the new apps being built. Same shape. That's Slack. Now think about how your team actually works. Work starts and happens in Slack. You only tab away for two things: context and ui. Context, because the data you need lives somewhere else. UI, because some things need buttons. Different buttons. An agent collapses both into one app. Context, it's already good at, it goes and gets whatever you need. UI, it's getting there. Soon it'll build the buttons right where you work. Whoever nails this shape owns where work happens next. The 2030 Microsoft Office.

I like how the commentator went: “Messi couldn’t have done it better” Messi: “Hold me mate bobo” 😂