Your AI coding agent has a home field. Here's how to find out if your stack is on it

An agent's competence isn't a single number. It's a map of where the internet wrote the most code, and the terrain drops fast. The same agent that produces a clean React table on the first try will confidently call a method on your niche framework that has never existed in any version. No hesitation, no hedging. The confidence gauge barely moves while the competence falls off a cliff.

The research backs the shape. Benchmark work that translated coding tests across 19 languages was built exactly to probe how language frequency in training data drives performance, and a survey in ACM's TOSEM journal calls the low-resource gap a significant challenge affecting millions of developers. There's a second, sneakier edge too: time. Even the most popular framework is a niche framework at the version boundary, because the model knows your stack as of its training cutoff. One benchmark (CodeUpdateArena) found that for the open models it tested, even pasting the docs of an API change didn't reliably make the model reason with the change.

What actually pulls the floor up, in rough order: a working example in your repo (models imitate a real snippet more reliably than they apply a doc page). Version pins stated as hard rules in the prompt, because the model's prior leans toward whatever version dominated its training data. Docs in context, dosed carefully — they help with facts and cost tokens every turn. And tests that fail loudly, because a red test is the only channel through which the agent ever learns it invented an API.

Should this pick your stack? It's a real input now for greenfield projects with heavy agent use, where boring mainstream choices pay off twice. But domain fit still beats corpus fit: a framework that halves your problem's complexity is worth the agent tax. Scaffolding recovers a lot of the gap. Nothing recovers a wrong abstraction.