Claude is limited by your own knowledge and skills. It will only do as much it has been asked to do, for it to go beyond that and produce work like a cracked dev, you need to know what you want it to do.
I was working on a component that had a state machine. Claude wrote a bunch of tests but i wasn't feeling confident about it.
I realised you can use property-based testing to test such rule based state machines. The advantage is that based on the rules, PBT will generate random sequence of states, and it can surface bugs that you may not imagine. So, I asked Claude to use it and it happily wrote exhaustive PBT tests which even found a few bugs.
My belief is that if i didn't know about PBT, i wouldn't even know to ask Claude to use it here.
This is one example but applies in design and implementation too where you are limited by your knowledge, and ability to ask the right questions.
So investing in learning is still paramount.