We used to make libraries and starter apps Now it’s skills and lint rules

i started using effect this week...and i think i'm really enjoying it

i’ve been a fan of szymon + oskar since our open source days. great team that i’m excited to angel invest in

v0 is now model-agnostic. Frontier models, cheap models, open models, and fast models, all from Vercel's AI Gateway. Choose from Claude, GPT, Kimi, GLM, Grok, DeepSeek and more to build your apps.

it took me a while to get used to, but this week i upgraded my wispr flow account. i am finally voice pilled. i love walking around and prompting my agent. just speak for like 15 minutes entirely unfiltered.

if you value your tech stack above all other product qualities, you’re gonna have a bad time

feeling right

GPT-6 Astra is now available on v0. Try it at v0.app

there goes my weekend

react is solved, useEffect is not

v0 is embracing model selection. Soon, every model on Vercel's AI Gateway will be available in v0: open models, cheap models, fast models, frontier models. More choice.

20k followers. Wow. All it took was 11 years.

I’ve been a longtime fan and user of @tan_stack libraries (namely Query). Very excited to partner with them to continue building the open web.

v0 is now available in Claude Design. Send your designs to v0, turn them into full-stack apps, and deploy to production.

Claude Design can now turn prototypes into web apps with v0.

The cool thing about making this is that I originally had no idea what the design should be. “go crazy” has worked v well for exploring new ideas.

The first thing I do before building a feature is design the URL. So I opened @v0 and made the URL visualizer I was always missing. linksy.sh

forever grateful that i never took the time to write lint rules by hand

We recently rewrote v0’s backend API using Elysia. We added typed helpers to consume it internally (𝚞𝚜𝚎𝙰𝙿𝙸, 𝚞𝚜𝚎𝙿𝙾𝚂𝚃, 𝚙𝚛𝚎𝚏𝚎𝚝𝚌𝚑𝙰𝙿𝙸 for RSC, etc.) The overall DX is really nice. We wanted our 𝚘𝚙𝚎𝚗𝚊𝚙𝚒.𝚓𝚜𝚘𝚗 as the source of truth, and Elysia had pretty solid support here. The goal was largely to turn our entire product into a headless SDK, and for our frontends to just be implementations. Our web app, mobile app, MCP, public-facing SDK, AI SDK tools, and Eve integration all derive from the 𝚘𝚙𝚎𝚗𝚊𝚙𝚒.𝚓𝚜𝚘𝚗. Clients within our monorepo use an RPC without a codegen step (though it took some work to fix up our Zod types for TS perf). In addition to creating an /api-v2 skill for new routes, we used agents to build extremely strict lint rules. Every route has consistent file structure and conventions around dependency injection and tests. It looks something like 𝚜𝚌𝚑𝚎𝚖𝚊.𝚝𝚜, 𝚍𝚋.𝚝𝚜, 𝚜𝚎𝚛𝚟𝚒𝚌𝚎.𝚝𝚜, 𝚊𝚙𝚒.𝚝𝚜 in each folder. It’s surprising how much this helped us avoid slop. We invested a good amount of time making our first few routes until the conventions felt right before migrating anything. I highly highly highly recommend sending Sol off to create a bunch of lint rules to enforce your codebase standards. Every human PR review could create a lint rule. To start, we made our rules only apply to touched files to make the migration incremental, but it results in a ton of cleaned up code.