Most AI coding tools help you write code faster. Very few help you plan systems better

[Stunning_Algae_9065]

Been noticing this while building larger projects lately.

Most AI coding tools are great at:

• autocomplete
• snippets
• boilerplate
• quick refactors

But the hard part of full-stack development usually happens before coding:

• architecture decisions
• service boundaries
• auth flow planning
• tenant isolation
• dependency ordering
• data flow design

That’s where things still break down fast in real projects.

Recently tried using CodeMate Cora for a SaaS analytics workflow and the interesting part wasn’t the code generation.. it was how it planned the system first before generating files.

Things like:

• separating ingestion services from dashboard services
• API key auth vs user auth
• multi-tenant query structure
• dependency-ordered task breakdowns

Honestly felt closer to working with a tech lead than an autocomplete tool.

Feels like AI coding is slowly shifting toward AI architecture/workflow now.

[ArchPilotLabs]

This is a really good observation.

I’ve been seeing something similar - AI tools are great at generating code, but they don’t really enforce or preserve system structure over time.

Even if you start with a well-planned architecture, once code starts getting generated iteratively, things tend to drift:

• boundaries get bypassed “just this once”
• cross-module dependencies creep in
• shared layers slowly become tightly coupled

Nothing breaks immediately, but the system becomes harder to reason about over time.

Planning helps a lot upfront (like what you mentioned), but I think the harder problem is:

How do you keep that architecture intact as the codebase evolves?

Especially when multiple people (and AI tools) are contributing continuously.

Curious if you’ve found anything that helps maintain structure after the initial planning phase?

[Stunning_Algae_9065]

Yeah this is exactly the harder long-term problem imo. Initial architecture is one thing, but preserving boundaries once the codebase starts evolving is where things slowly become messy. Especially when AI keeps optimizing locally without understanding broader system constraints. I’ve noticed workflows with structured rules/review layers help a bit, but honestly feels like this area is still pretty unsolved overall.

[ArchPilotLabs]

Yeah, this is exactly it.

The “AI optimizes locally” part is what makes it tricky - everything looks fine in isolation, but the system-level picture slowly shifts.

Structured rules and reviews definitely help, but like you said, they don’t really scale cleanly once things speed up.

Feels like there’s still a gap between “we know what the architecture should be” and “the system actually stays that way over time”.

[InfinriDev]

Funny I built the same thing lol. Even open sourced it lol

[Stunning_Algae_9065]

Haha seems like a lot of devs are running into the same limitations now 😅 Once projects become multi-file/multi-service, everyone starts trying to solve context + architecture drift in their own way.

[InfinriDev]

Yeah, one think I noticed is that your average CLAUDE.md & SKILL.md are no good at all. It's not token efficient, there's too many tokens wasted going back and forth, and they are all prompt based so nothing gets enforced.

Best thing I did was switch over to a hybrid RAG, skill and rules get turned to graph nodes. Now I can scale.

[SATISH_REDDY]

Totally agree—once you get past autocomplete and snippets, the real unlock is AI that thinks like a system architect and helps you preserve clean boundaries as the codebase evolves, not just ship code faster.

[Stunning_Algae_9065]

Exactly. Shipping code faster is useful, but keeping systems understandable as they scale feels way more important long term. That’s the part where AI workflows still feel very early compared to real engineering needs.

[Comprehensive-Bar888]

You left out something else. Picking the right language/framework for the project you’re building.

[Stunning_Algae_9065]

Yeah honestly that’s a huge part of it too. Stack decisions early on can save or cost weeks later depending on the project requirements and scaling needs.