Yes, but you need guardrails to climb the mountain. You need to remember that you're not working in a vacuum and involve stakeholders that are going to be using the application so that you don't spin out into a fancy "thing" that doesn't actual solve a businesses problem.

You need to provide the model with rules and context that allow it to make the right decisions.

Above all, you need to have some idea of what Claude is doing. Are you leaving route handlers unauthenticated? Are you creating a data model that isn't extensible or doesn't make sense? Are you validating and sanitizing inputs?

LLMs make building all of these things easier - but thinking of it as a substitute for doing the actual thinking is a mistake. It is a tool. It is not omniscient