"Built to be written by agents"? To me that would mean to drop the framework altogether: they've always just been an abstraction to bridge knowledge gaps in bigger teams and enforce coding patterns. But now that's just the job of the agents, and instead you can prompt it to set up a proper server in any language you want.
I'm working on something right now it's called ReactiveScript which takes Solid's constraints and makes them in the compiled language. Its still WIP but early results are promising. It can do better than vanillaJS because async bugs are compiler error by construction etc. It's a bit like the Rust mentality. If the agent can't write bad code if it won't compile.
I think we will see more of this. Frameworks have been "languages" for years. Rich Harris of Svelte saw that. This is exactly the remaining gap right now. Peeling away the layers is also peeling away the guard rails. You can add those back with rigor of testing. But huge benefits to just encoding our learnings in the language itself.
It’s November 2026. I haven’t written more than 2 lines of code in a day since January 2026.
So if a framework is made so that coding agents can use it well, why is it a negative?
I’m not going to be writing SolidJS by hand.
If anything, I think attention limits, token costs, and declining performance as size/complexity increase means good abstractions are more necessary than ever.
Ask Claude to write a SaaS landing page for you in React/Next.js
Then ask Claude to write a SaaS landing page for you in assembly.
Then compare the results.
So you want knowledge gaps between agents and the team.
You could say that about some libraries, but LLMs haven't made reactive frameworks obsolete; on the contrary, they're very effective at using them, and they write better, more maintainable, and more consistent code with them than when they try to hand-write JS that renders to the DOM. Anything that can "bridge knowledge gaps in bigger teams and enforce coding patterns" can also help write code with agents!