The standard models are pretty bad a zig right now since the language is so new and changes so fast. The entire language spec is available in one html file though so you can have a little better success feeding that for context.

> The entire language spec is available in one html file though so you can have a little better success feeding that for context.

This is what I've started doing for every library I use. I go to their Github, download their docs, and drop the whole thing into my project. Then whenever the AI gets confused, I say "consult docs/somelib/"

Just use gh_grep mcp and the model will fetch what it needs if you tell it to, no need to download from GitHub manually like this

that's what context7 mcp is for!

I on the other hand see most languages become superfluous, as coding agents keep improving.

During the last year I have been observing how MCP, tools and agents, have reduced the amount of language specific code we used to write.