What's your go-to coding agent? We've released Flutter AI plugins for Antigravity, Claude Code, Cursor, Codex, and more 🚀
These plugins bundle the tools and knowledge an AI assistant needs to understand and modify your Flutter codebase.
Get started: https://t.co/DOXkb5bvPe
Flutter had zero iPhone Duo support. Now it has a package. 🥳
foldable: hinge angle, fold posture, crease geometry and size classes, straight from iOS 27.1 to Dart. Safe on every non-foldable device too.
https://t.co/zD2R8ddYoG
#Flutter#iPhoneDuo#FlutterDev
open-sourced this!
225 icons + agent mds and the generator js files to make more
contribute back to the repo if you expand it :)
https://t.co/4wefrhL9Pc
One year ago, @Wealthsimple acquired Fey.
Here's what it's actually been like as founders: what we built, what surprised us, and what's next.
https://t.co/nEYaSSgbaS
About 7 months ago, I started designing a WebGPU library to ship performant shaders at Vercel.
Today, we are announcing vgpu: a minimal WebGPU library designed for agents.
But what does "designed for agents" mean? 🧵
Opus 5 is so good at creating these exploded-view and wireframe three.js product sites.
Give it a video reference and it can build the experience directly in three.js or Blender. Then keep improving the details, textures, and lighting with follow-up prompts.
I got our entire design team to turn landing pages built around images and video into three.js sites. They're lighter and easier to prompt. Since everything is code, AI can make more precise changes with fewer iterations.
The difference between the old image-based sites and the new three.js versions is staggering. I can also jump in after the team finishes and help refine the details.
Btw, https://t.co/25OYbxZ62e is getting 100K views a day, which is absolutely nuts. The repo reached 3.8K GitHub stars in 4 days. It's my fastest-growing open-source project by far.
So I added 60 more components. I'm also looking for sponsors to help fund ThreeUI long-term so I can keep adding to it.
Introducing a new skill:
/explain-interface
When I'm curious how something was built on the web, I often use DevTools to try to figure it out. Now you can use this skill instead.
Try something like:
/explain-interface how is the gradient on interfere . com built?
https://t.co/lcR4NU8I1p
Origin, our code hosting platform, is now live.
It's fast, easy to use, and deeply integrated with Cursor.
Get started by syncing your repos from GitHub.
Omarchy Quattro is out!! This is one of the greatest software releases in my professional career. I hope you enjoy using it just as much as I did building it ✌️ https://t.co/81wLStgH7P
pstack now includes 2 skills i recommend everyone use or copy:
/create-verification-skill
https://t.co/xYQArsuVWR
/maintain-verification-skill
https://t.co/J5s8WL1itT
if you don't already have one, /create-verification-skill creates a skill that teaches your agent how to run, control, and debug your app.
it also creates something i call the feature map: a map of all the features in your app and how to get to it and use it from a user's pov. it allows agents to navigate and use the app just like a real user which greatly increases its ability to verify its own work. but of course, this feature map goes out of date very quickly.
run /maintain-verification-skill as a daily automation with cursor cloud agents. this skill will check your app for changes and keep your feature map up to date.
having a strong verification skill will end up becoming critical infra for your team and become the foundation of boosting everyone's productivity and quality and also enable more interesting automations to be built.
install https://t.co/WDB4U1rwmu and you'll get auto updates for my skills. enjoy!
Introducing Canvas UI, the first ever html-in-canvas component library.
Your DOM is the render target now. Real-time shaders over real, interactive UI.
24 components. React, Vue, Svelte, vanilla TS.
Free. Open source. 🧵
https://t.co/Y5ZZDNxPUX
Some observations on Kimi:
1. It's a very good model! I don't think its performance can be explained away by distillation or anything like that. In agentic coding sessions, it seems pretty much on par with the best public models of Q1 2026. In my fairly limited use, it also seemed very token hungry. It's not obvious to me that this model is actually that cheap to run.
2. I am personally surprised the Chinese state continues to allow the open sourcing of models this good, given potential risks. To be clear, I *myself* might be fine with models presenting this level of marginal risk being open weight, but I am surprised that China is fine with it. I suspect the reason they are is 75% explained by strategic blindness/lack of AGI-pilledness (the CCP is very Yann Lecun-y in its views of AI). The other 25% or so is their lack of compute for customer inference (making China's open-weight strategy an unintended byproduct of US export controls) and the normal Chinese strategy of aggressive exports. For the companies, as opposed to the government, the decision to open source is partially ideological and partially because they are behind, and they know that very few people would pay for sub-frontier models from China.
3. Open-weight models are inherently decelerationist, and I'm continually surprised to see the so-called "accelerationists" so excited about open-weight models. I suspect the reason they are is that they know open-weight models are effectively ungovernable, and they simply like the overall cloak of ungovernability open-weight models create over the whole of AI. It's not a bad strategy; it reminds me of James Scott's recounting of the hill people in "the art of not being governed." Still, in the end, open-weight models deter further AI capex.
4. One probable outcome of an open-weight-model-dominant world is full AI communism, which is precisely what China proposes: rather than a market product, AI is a "public good" which will ultimately be provided by the state as a kind of "digital public infrastructure." This future strikes me as a dystopian hellscape, but I've never met an open-weight models advocate who doesn't ultimately concede this is where things end. You'd be surprised how many 'accelerationists' lobbied me, while I was in government, to support an eleven or twelve-figure federally funded data center so that startups could train models at a subsidy and then give them away for free. There was no other way for AI to progress, they said. Perhaps this is the logical end state of things. Nonetheless, I find myself surprised to see supposed accelerationists excited about such an outcome. I think many of them just don't know what they're doing. Many accelerationists do not view the creation and serving of frontier models as a legitimate business.
5. I would guess that the Trump Administration will at some point realize that their best strategy here would be to create large amounts of regulatory risk around the use of open-weight Chinese models. You don't need to "ban open source" (one of the dumber motifs of AI policy discussion). You just need to direct every agency to issue soft law that creates FUD. "A Federal Reserve Advisory Bulletin found that there may be backdoors in Chinese AI models." It needn't be that well justified. You just create enough regulatory risk that every regulated enterprise backs off. You probably don't want to create so much regulatory risk that you scare off the hyperscalers from serving Chinese models; this will just drive startups to sketchier providers. There's a happy middle ground here. I'd assume they will do some version of this.
6. It's probably true that open-weight models of this capability make the world a bit more dangerous, but not so much more that you'll really notice. At some point the models will be capable enough that you will notice. "A nonliving, invisible, dangerous, and infinitely self-replicating agent escaped from a Chinese lab," you say? Color me shocked.
I’ve been asked several times whether Zhilin Yang, the founder of @Kimi_Moonshot was my PhD student. The answer is yes and he is absolutely brilliant.
But I’ve been incredibly fortunate to work with so many outstanding PhD students over the years. So I thought I’d brag a little about them and their career paths (of course there are also many MSc and undergraduate students, sorry if I missed anyone):
Founders / Founding Team Members
Devendra Chaplot @dchaplot PhD, Founding Member Thinking Machines / Mistral
Zhilin Yang PhD, Founder & CEO, Moonshot AI
Jimmy Ba @jimmybajimmyba MSc/PhD, Co-founder xAI
Hubert Tsai PhD, Co-founder Spuree, Apple
Nitish Srivastava @nitishsr PhD, Co-founder Perceptual Machines; Co-founder Vayu Robotics
Charlie Tang PhD, Co-founder Perceptual Machines, DE Shaw.
Professors
Paul Liang @pliang279 PhD, MIT
Ben Eysenbach @ben_eysenbach PhD, Princeton University
Ruosong Wang @RuosongW PhD, Peking University
Bhuwan Dhingra @bhuwandhingra PhD, Duke University
Roger Grosse @RogerGrosse Postdoc, University of Toronto
Alexander Schwing Postdoc, UIUC
Research Scientists
Shuyan Zhou @shuyanzh36, Postdoc, Meta Superintelligence Lab
Tiffany Min @SoYeonTiffMin PhD, Microsoft AI
Murtaza Dalal @mihdalal PhD, Tesla AI
Minji Yoon @MinjiYoon90 , PhD, Microsoft AI
Shrimai Prabhumoye PhD, NVIDIA AI, Mistral
Haitian Sun @sun_haitian PhD, Google DeepMind
Emilio Parisotto PhD, Google DeepMind
Lisa Lee PhD @rl_agent, Google DeepMind
Manzil Zaheer @ManzilZaheer PhD, Google DeepMind
Jamie Kiros PhD, Google Brain, OpenAI
Yuri Burda PhD, OpenAI, Anthropic
Cody Severinski PhD, Amazon