I’ve just found out that once your project grows, the prototyper AI can create duplicate files in your project, so once you request changes, they may not get applied since the a duplicate file is still dominating the changed one. That may cause some many problems and upapplied requests. I recommend to tell the prototyper AI to seek the entire file system of the project and look for duplications.
It’s all about prompting. The more specific the prompt, the better. Specific prompts help to mitigate and reduce how often the AI model will attempt to recreate a file as oppose to add a feature to an existing file.
The model you use will also make a difference.
I’ve been experiencing this lately, it’s not just about the prompting.
The dynamic reduced context size seems to affect its ability to know where files are or where they should be. I’ve seen it create new directories and place config files in them when the configs were already in the root directory. Once I point it out, it fixes it, but I don’t think this can be solved just by prompting, and I don’t think it’s reasonable for a user to say ‘don’t create a duplicate config file that I already have in my project root’ because it’s assumed that even a rookie developer wouldn’t make such a simple mistake.