I’ve gotten down votes on this comment, but this is the kind of work we have PMs doing now. We don’t even have dedicated frontend developers anymore. Continuing down this path is how you lose your job when someone who understands how to use the new tool comes along.
You can either keep filling up your context window with thousands of instructions and hoping the AI will listen, or you can use AI to fix the problem permanently with automation that runs in CI and allows you to correct everything before a PR gets merged.
Unless we’re training these systems on “solve this problem while following hundreds of arbitrary rules”, loading all your wants and needs into the context window is bound to fail. It’s not what the AI was built to do.
Building tests to catch specific issues and transforming code to better architecture are tasks that AI is good at. You can mistakenly expect the tool to operate like a human, or you can understand what the technology was trained to do and build around that instead.
I am doubling down here. This isn’t a real issue if you’re treating AI like any other tool and understanding how and where to apply it.
Or you have no autonomy to mold the code base to AI. If so, that’s unfortunate.