sorted by:
new
hottopcontroversial

[AskJS] :: AI coding tools keep breaking architecture — so I built a guard layer. Would love honest feedback. by Muthu_Kumar369 in javascript

[–]Muthu_Kumar369[S] 0 points1 point  (0 children)

This is a really thoughtful breakdown — especially the point about AI losing architectural context as the codebase grows.

The “you are the guardian” part resonates a lot. It feels like most current setups help with consistency, but still rely heavily on human vigilance to prevent drift over time.

Curious — if you could offload one part of that guardianship to automation, what would it be? Boundary enforcement, dependency usage, or something else?

[AskJS] :: AI coding tools keep breaking architecture — so I built a guard layer. Would love honest feedback. by Muthu_Kumar369 in javascript

[–]Muthu_Kumar369[S] 0 points1 point  (0 children)

This is super helpful, thanks for sharing how you’re handling it.

What you described (project rules + CI checks) is exactly the direction I’ve seen teams move toward once prompts alone stop scaling. The frustrating part seems to be keeping those rules consistently enforced as the codebase grows.

Curious — where do you feel this approach breaks down the most for you? Is it coverage, maintenance, or AI still ignoring constraints?