ask an agent to make an app scale and it will happily add caching, queues, autoscaling, the lot. most of it u did not need. the word scale is too vague for it to make a good call.
made a short splitting it in two.
the swing is load going up and down, busy saturdays, quiet tuesdays. thats handled with headroom and servers that join and leave. growth is more users every day, year over year. that needs a back end that can actually spread across more servers.
what worked for me is writing both numbers into CLAUDE.md before any infra work. peak vs normal load, and expected users in a year. with those two lines the agent stops guessing and picks the smallest setup that fits. what do u give ur agent before it touches infra, or do u let it decide.