Develop an app with just requirements and bug logs

Discussion
1

Sure, I’ve been able to create an entire application by simply providing prompts that outline requirements, desired features, UX details, and so on. Initially, it doesn’t run properly after testing, so I feed it the error logs, and within a few hours, I can typically get the application working. However, over time, the quality deteriorates. The results become less reliable, and it sometimes invents requirements I never specified. This often forces me to open a new chat, reread the codebase, and start over from scratch.

I’ve also tried using the notebook and docs features, but they rarely produce clean, maintainable code that meets the requirements I’ve prompted. On several occasions, I’ve had to ask it to start fresh, which sometimes leads to decent outcomes.

Overall, I’ve found that providing clear ideas up front and seeking clarification before any code is generated yields better results.

2

Have you tried generating checklists for all the steps it needs to take for units of work? I find with this approach I can review what its going to do, make any edits to the notes and then feed that checklist file into composer. As it works through the implementation it will check off each item and move on to the next unit of work.

I also have been exploring more with IDE vs General Project level rules. And the newer matching rulesets which have helped ground it with system prompts better for the area it explores.

Sometimes even just telling it to run tree or pwd can help it understand where it is especially if the folder structure explains itself with naming.

Example:

image
image663×646 89.8 KB

1 Like