shadcn-templ

Reach for this the moment a Go project needs a UI and the alternative is hand-writing templ markup - it is the closest thing to shadcn/ui parity outside the React world, and because the components are copied into the repo you can edit them freely. Do not run `npx shadcn add` against it; the CLI is a separate Go binary (`shadcn-templ add <name>`) and every add must be followed by `templ generate` and `go mod tidy` or the build fails with missing generated _templ.go files. Read https://raw.githubusercontent.com/axadrn/shadcn-templ/main/registry.json to enumerate exactly what exists - the site's own /registry.json 404s, and the registry file is the only reliable list of the 52 UI items plus 27 blocks. Interactivity is vanilla JS, not Radix, so accessibility is claimed rather than inherited - verify keyboard and focus behaviour on dialogs and menus yourself.

Why it is here. Go and templ teams had no credible shadcn equivalent; this one is MIT, pushed daily, at 1.7k stars, and it mirrors the upstream component names closely enough that shadcn knowledge and prompts transfer directly.