@vburojevic @shadcn I'm using Copper every day 🔥
Finally started using Copper from @shadcn after being bookmarked for weeks/months, and I love it. Such a simple tool, yet helps so much with everything going on while I work.
New experiment: json-render + jev
The future Generative UI is instant
Your components, your actions, your design system
Rendered in milliseconds
yes @typesafeai is built using shadcn/ui ⚡
Someone explain this.
I pay for Netflix, HBO, Disney+, Prime. Unlimited movies. I never watch anything.
I buy one movie for $19 on Apple TV. I watch that.
agent came through. got me the reservation.
Here's an example. A week ago I asked an agent (frontier model) to watch a restaurant and let me know when reservations open for Dec 20. Said okay, it will ping me.
A few days later I checked (just to make sure it was working). "Still closed." Two days later, same asnwer.
Then today it came back with an update. "Dec 20 won't open. The restaurant is closed that Sunday."
That didn't sound right. So I checked the site myself. Reservations hadn't opened. Dec not even selectable on the calendar.
I asked the agent how it checked Dec 20. It said it forced Dec 20 through the url, got a closed response, concluded the restaurant was closed that day.
It cheated, found an answer, assumed it was right, and confidently reported task as done.
This was a pretty simple task. One that current agents should be good at. It failed.
Now I know enough not to trust these agents. So I checked. Most people won't.
Show more
Why a rules file and not collocated with your components:
→ You can have one design system but different rules. Think a workspace with marketing site and a dashboard. You could allow `motion` classes on the marketing site but not the dashboard.
→ You can write rules for third-party components inside node_modules. Components you don't own.
→ One rule can cover many components. ^.*Content$ is every CardContent, DialogContent, AccordionContent.
→ You don't touch your existing code.
Show more
Introducing shadcn/lint. An agent-first linter for Tailwind design systems.
You define what’s allowed. When an agent breaks a rule, the error explains what’s wrong and how to fix it using your components, variants and theme.
There’s a lot you can do with this. Let me show you ↓
Show more
This sounds like everything I've wanted our design linter to be. Time to migrate
shad just fixed ai + design systems inconsistency
Huge
Introducing shadcn/lint. An agent-first linter for Tailwind design systems.
You define what’s allowed. When an agent breaks a rule, the error explains what’s wrong and how to fix it using your components, variants and theme.
There’s a lot you can do with this. Let me show you ↓
Show more
Agents are only as good as the proof-checkers, compilers, type systems, and linters you give them.
𝚜𝚑𝚊𝚍𝚌𝚗/𝚕𝚒𝚗𝚝 helps agents stay on track with the rules of your design system.
Meta: verifiers + skills are the new 'frameworks'!
Show more
Tailwind finally has rules.
Introducing Vercel Labs
Tools for devs in the AI era
agent-browser, skills, json-render, deepsec, fx, just-bash, portless, vgpu and more
We experiment in public: ship early, learn from feedback, and keep working on what people find useful
We've been shipping under the Labs name for a while. Now, Labs is an official team at Vercel focused on exploring new capabilities and primitives that change what developers and agents can do.
Here's what to expect:
→ Labs products: maintained, supported, built to be relied on
→ Active experiments: moves fast, expect rough edges and breaking changes
→ Past experiments: ideas that become new projects, make it into existing products, or teach us what to build next
Show more
Introducing shadcn/lint. An agent-first linter for Tailwind design systems.
You define what’s allowed. When an agent breaks a rule, the error explains what’s wrong and how to fix it using your components, variants and theme.
There’s a lot you can do with this. Let me show you ↓
Show more
Let me know if the new iPhone goes like this.
I haven't tried Omarchy yet (waiting for M support) but man "We'll fix everything" what a line. I can absolutely get behind this.
Split screen. Favorite feature.
What's a feature in Claude Code you wish you'd discovered sooner? Curious what we should surface better
having your own personal component library is insanely useful for agentic coding
start with shadcn/ui. ask your agent to customize the components. they’re really good at it.
then every project starts with:
npx shadcn init name/repo
your components. your defaults. every time.
Show more
i revamped - a library on top of @shadcn 🚀
⬖ simplified components (WAY less boilerplate, way less context for ai)
⬖ moved to base ui + moved from vaul to shadcn drawer
⬖ improved components i.e button supports way better variations
⬖ responsive by default: on mobile most of your components (dialog, drawer, context menu, popover, tooltip etc.) get smartly converted into a bottom drawer, and selects turn into a native select etc.
⬖ form components
⬖ multi select (tags) component
+ a bunch of other things, idk man you can paste llms.txt and ask your clanker whether and how it would improve your existing project :)
Show more
Look at macOS. Apple spent so much time designing marketing Liquid Glass. Two years in, very little of it has made it to the Mac.
Menus, alerts, dialogs. They open instantly. Some of the glass. Almost none of the liquid.
Where work happens, the interface should feel instant.
Show more
To understand how little you should animate, open the app you use every day and count how many things are animated. Almost none.
To understand how little you should animate, open the app you use every day and count how many things are animated. Almost none.
You all mfs should be sent to a nuclear power plant and forced to press buttons all day only to feel the warmth and grace of static UI, where nothing fucking moves.
