I develop prototypes using Claude Code. The dead boring stuff.
"Implement JWT token verification and role checking in Spring Boot. Secure some endpoints with Oauth2, some with API key, some public."
C# and Java are so old, whatever solutions you find are 5 years out of date. Having an agent implement and verify the foundation is the perfect fit. There's no design, just ever-chaning framework magic. I'd do the same "Google and debug" cycle, but 10 times slower.
It's kind of funny to see you saying "whatever solution you find are 5 years out of date", while at the same time saying that the tool that was taught using those same 5 years out of date solutions as a part of its training data is actually good.
Terrible idea if you ask me. I'd suggest checking the official docs next time around, or at the very least copying them into the context window.
First, good agents do that themselves. Second, specifying an exact and current version also works. Third, I'm mostly concerned about having a working example. I'm talking about breaking changes and APIs not existing in newer framework version. As long as it compiles, it's clear the approach still works.