In my experience, using LLM's for generating code has definitely dulled my capacity to think about function hierarchies, composition and having a "picture" in my head of what will go where in the repository.
Raw "leetcode" algorithm intuition and database modelling/SQL are still largely intact for me because I never trust LLMs for those and want to actually understand what I'm building. But it's scary to think how easy it is to have your skills eroded and how quickly you become dependent on these tools.
From your comment, it seems like the only skill that has eroded in you apparently is the fact that you don't understand the structure of a repo that was written by someone else? Was that a skill you had pre LLM that you could just touch a repo you didn't work on and magically knew where everything went?
Furthermore, if you can see it so transparently and have put a stop gap, why do you think the rest of the world or programmers will not? Why will they fall into the temptation that you can resist? Especially if we are talking about that specific subset of people that are already really good at coding and understand the pitfalls pretty well.
Maybe you can make the argument that someone who purely vibecodes never gets the skills of raw algorithm intuition/specific knowledge but in those cases, no skills get eroded because there were none to begin with.
Raw "leetcode" algorithm intuition and database modelling/SQL are still largely intact for me because I never trust LLMs for those and want to actually understand what I'm building. But it's scary to think how easy it is to have your skills eroded and how quickly you become dependent on these tools.