🦋 Ben

Hell froze over: announcing FormKit for React. Secretly framework-agnostic since inception, today we’re open sourcing the most popular Vue form library…for React. Why is this a big deal? 1. Forms are still hard. We (the creators of FormKit) thought form libraries were no longer necessary, given the trajectory of coding agents. It turns out we were wrong, and we learned this the hard way. Need repeating conditional fields nested 3 layers deep inside a dynamic component, with accessibility, validation, internationalization, and backend error placement? Turns out coding agents aren’t great at that. It’s table stakes for FormKit. 2. Single component. This matters more than you would think, but FormKit doesn’t ship lots of different components each with its own props. Instead, it has a single one: and unified props. This was done to provide a better DX to human engineers. It makes it easy to spot when a given component was part of the form’s data structure vs a presentational component. It turns out this matters even more to coding agents than humans. No matter where your coding agent is, whenever it sees “FormKit” it immediately knows “oh, that’s part of the form’s data”. 3. No plumbing. FormKit doesn’t require any manual data collection, event listening, or state tracking. It does all this for you on a heavily tested, framework agnostic, self-assembling graph. The only code your agent needs to write is declarative templates and submission handlers that respond to the state. 4. Dense colocation. FormKit’s syntax happens to be ideal for coding agents; nearly everything you need to know about a given input is *on* the input: Colocation dramatically improves the efficacy of coding agents. 5. DOM. FormKit, unlike most form frameworks in React, renders the actual DOM. This also increases colocation and best practices, meaning your coding agent is far more likely to produce consistent and high-quality output that looks and acts the way its supposed to. 6. Schema. FormKit’s own inputs are not written using Vue or React — instead, FormKit has its own render schema — think of it like an AST for the DOM — and you can modify it on the fly. It’s not very human-friendly to write, but it turns out most models are already pretty well trained on FormKit’s schema. Want your inputs to look a bit different on one form than another? No problem, your coding agent can easily make those changes *without* modifying the JSX structure at all. Oh, and any inputs you create for Vue work with React and vice versa. 7. Plugins. FormKit leans into the unstructured tree graph hard. The graph doesn’t just collect data, it also passes down configuration and plugins. Want one form to work a bit differently than another one? No problem — just add a plugin to the top of that form or group and its children will all receive that feature. You can even mass assign props and configuration this way. Of course, FormKit has been solving these exact issues for a long time, but it wasn’t until we started using it on our own projects with coding agents that we realized what a huge advantage it is. With so many people using coding agents with React, it made sense to unveil FormKit for what it has always been — a completely framework-agnostic form framework that happens to unlock your coding agents. ➡️ formkit.com

@_pi0_ Did you confirm you and @evanyou aren't doing the same thing? 😅

IT IS SUPER COOL AND FUN

MVP shipped 🚀 A few more days of private beta to iterate fast and dogfood it.

@evanyou @__2024__2025 You should make a paid service to allow viewing your prompts.

@__2024__2025 idea -> discuss -> design doc -> iterate -> plan -> implement

I think I am designing something truly unique right now... I might be too high from the continuous dopamine hit from agents turning my crazy ideas into code in 10 minutes. But like this is genuinely good stuff.

@simeonGriggs Even better🤞 github.com/antfu/skills-n…

@simeonGriggs github.com/antfu/skills Guessing won't align the stack your looking at, but good poc trying to crack this pain point

Can anyone explain why we're not installing skills from npm so we actually get versioning and updates? Downloading plain text files to your project exactly once feels insane.

@wesbos @cdev_h Spooky stories going to be a great one this year! 🍿👻

@cdev_h i dont think you'll need to wait that long

you do you, i'll be just here sipping on my fruit juice waiting for some huge ass security issue to be found in the next month

@stolinski @fahadshahbaz_ Maybe Clawdbot can re-edit it for you?

@fahadshahbaz_ I made one, but I’m not happy with it. Going to redo it this week.

Things my Clawdbot has done. - Re-organized my NAS - Created personalized, custom mediations (think headspace) - Started work on todos that were falling behind. - Cataloging meals and recipes - Adjusted my custom Tonal workouts based on my current physique and goals. - Setup my tailscale serve network - Created a custom, personalized podcast on any topic I tell it I want to learn and have it available to subscribe in all podcast apps via a local rss feed. - Tell me when my air quality is bad in my office. - Prompts me with random questions daily and logs them in a journal, catalogs and pulls nuggets and thoughts out of them. - Checks up on my stock positions and gives me advice. - Fixed several home assistant automations and suggested new ones, cleaned up my home assistant dashboard.

@steveschoger @adamwathan Refactoring AI?

Working on something new with @adamwathan. The last time I was this excited about a project is when we launched Refactoring UI.

@dave_stewart You're absofuckinglutly right! A while back, I set my Cursor rules to "swear like a sailor at any given opportunity during conversations" and have never looked back.

Claude has started swearing in our conversations, and I fucking ❤️ it!

@ryolu_ I use a similar style in my code with bug fixes.

the art of kintsugi fixes broken pottery with gold, highlighting each crack as part of the object's story what fractured and healed carries more beauty than what remained untouched

@DanHollick @drewwilson @jamesm I see a solid blog post here. Perhaps you can mock up some technical diagrams to delve into the secrets of their perfection. The layers, wave formations in the chocolate, the biscuit density, the level of snap to crumble. I'm only left wondering milk vs the elusive dark.

@drewwilson @jamesm Just the most perfect food ever created. I'll bring some to Valiocon

My version of this question is: "What's the single most astonishing modern object you could take back in time and show an Ancient Roman?" I'm convinced it's not some tech, like an iPhone or whatever, but a foodstuff like an Oreo or a chocolate Hobnob. Ground rules: - It's a random Roman, just the first guy you find. - You only have 30 mins. - You don't speak Latin, they don't speak English so you need to demonstrate it's value with that in mind. (90% chance they can't even read) - It has to be able to work there, no power, no signal etc. - You have to be able to operate it yourself.

@MasteringNuxt Big bucks marketing!

Have you started using Nuxt 4? If not, what are you waiting for?

@wesbos Not my first, but an oldie: web.archive.org/web/2009101504…

The first website you ever made. Is it still on the wayback machine? Link me to it! We're doing a video

@ViteConf @nytimes @vercel m.imdb.com/title/tt198509…

Solutions & Hints The emojis in the first post: Cog → The Svelte Compiler, or also Rollup as bundler Ghost → Svelte as “vanishing” and compiling itself away Newspaper → Rich worked at the @nytimes before Triangle → For a while, Rich is part of @vercel And eventually, the link to the first commit: firstcommit.is/rich-harris

Thanks for joining our Guess the Speaker game! We’ve collected all answers across platforms and have chosen a winner, which has been notified. Did not get a DM - or didn’t know who it was eventually? No worries! You now can get 50€ off your ticket with the code richwithrich (valid until the end of the week) Wonder about the solutions for the clues? More info below!

@ViteConf If it looks like a Rich. Talks like a Rich it gotta be a @Rich_Harris

🚨 GUESS THE SPEAKER! FINAL CLUE 🚨 🎟️ Your FINAL chance for a FREE ticket to ViteConf. Guess to enter the raffle. 👤 A new speaker who is not in this year’s lineup on viteconf.amsterdam 🔎 Find out if you were right on Monday. 👇 Drop your guess below!

@biilmann I've had similar wins with Figma plugins. I managed to spin up a plugin for design token for my specific needs. The code isn't very pretty, but it does what I need. The thought of building a Figma plugin from scratch would of previously seemed too much effort to bother starting

AI will make the amount of software we build explode. At Netlify we just switched from Zoom to Google Meets. In general an improvement, except that in Meets you can't share audio from outside the tab you are screen sharing. This means no ability to play a Spotify song during the first few minutes of a townhall or large group meeting while showing the intro slides and messaging. Before AI, I would just have lived with it. Not now. I opened up Claude Code and gave it this prompt: "I want to create a chrome extension that lets me paste a spotify embed block (or similar embed block) and then injects an iframe into the current page with that embed positioned so it's always on top of any other elements and interactive. Make sure there's a little close icon to dismiss the iframe again (should remove the iframe from the DOM)" Now I have a Chrome Extension that lets me play Spotify from within any tab, and I've solved my problem. I've coded Chrome Extensions myself, but it's a long time ago, and I would not have had the time to read up on how they work, figuring out how to start one and do the setup, write UI code for drag'n drop stuff in JavaScript, etc, etc... This is software that would have never been made without AI, and we'll see so much more of this. What's also true is that had I not been an experienced developer, had I not known about the capabilities of Chrome Extensions to inject code into the current tab, or had I not known about iframe's and their ability to run external code safely within a tab, I would not have been able to write a prompt to solve this problem with or without AI. As @KentBeck said in a recent tweet: "The value of 90% of my skills just dropped to $0. The leverage for the remaining 10% went up 1000x."

@adamwathan Nice! Does it put pressure on the figma files needing to be strict with layers and component naming?

Going to keep pushing this a bit more and really refine the rules, then will probably throw them into Tailwind Plus for anyone who wants to try them 👍🏻

Alright, really cooking now… ✅ Pixel-perfect compared to Figma design ✅ Supports light and dark mode ✅ Includes responsive design ✅ Didn't write a single character of code by hand ✅ Was definitely faster than doing it myself Figma MCP server + rules file biggest unlocks.

@pwnies Extended collections - the teaser at 2023 looked so promising 🙏

If you missed it, we've got a ton of small updates for design systems functionality in Figma. We've got some bigger things cooking, but these small changes go a long way to improving the overall experience, so lemme know any pain points your still facing!

@EricSimons @adamwathan I've noticed same on Cursor with Claude it just refuses to believe tailwind 4 was released 😅

@adamwathan hey! lots of folks are reporting tailwind v4 doesn't work in stackblitz/bolt, we'd love to help get that sorted with y'all - could you shoot me a dm? #issuecomment-2744037838" target="_blank" rel="nofollow noopener">github.com/tailwindlabs/t…

@TheAlexLichter @voidzerodev @evanyou @rolldown_rs @vite_js @vitest_dev Congrats!

🎉 Excited to announce that I'm joining @voidzerodev as DevRel! As I was following the project from early on, I couldn't say no to the chance when @evanyou reached out. I can't wait to share all the incredible things lined up for @rolldown_rs, OXC, @vite_js, and @vitest_dev 👀