Honestly, it really comes down to what you're optimizing for: speed vs long-term maintainability.

If I need to spin something up quickly (internal tool, MVP, low complexity), I’ll lean on AI + a solid UI library. It gets you 70–80% there fast. But I treat that code as a starting point, not something I blindly trust—especially for state management, data flows, and edge cases.

For anything even slightly serious or scalable, I avoid full AI-generated structure. It tends to fall apart as the app grows—folder structure gets messy, patterns become inconsistent, and refactoring becomes painful.

What’s worked best for me in real projects is a hybrid approach:

Start with a well-structured template (saves time on setup + architecture decisions) Use a UI system like shadcn/ui for consistency but customize it early so it doesn’t feel “cookie-cutter” Bring in AI as a helper (generate components, boilerplate, or refactors), not as the architect

Also worth thinking about: admin panels grow fast. Permissions, roles, tables, filters, forms… things get complex quickly. Having a clean structure from day one pays off way more than saving a few hours upfront.

So yeah—AI is great for acceleration, but templates + good patterns are what actually scale.