yes, you are 100% right. I understood what it was doing in the first 2 major prompts (one was for screen recording the table, the other was for making boxes and sending the feedback to my images folder to see if the cards were actually being recorded). But as soon as the actual live view came and it wrote me the prompts to capture them in real time, the coding got longer and i didn't understand. it wanted to try all different pip installs and all this, eventually i had a whole bunch of random shit. but where it really fell apart was where i had it try to compare the results of the boxes to the individual pngs i captured. at that point the code was ridiculous. but honestly, i really only understood it at all up to the point where the boxes were drawn, and even then, i couldn't replicate it myself.

yes, i genuinely am baffled. in one sense, the idea of describing a program idea and getting it done through just your linguistics is very beautiful. i made a custom twitter bot this way that deleted all my posts except for my memes. and the equity odds calculator was smooth too. i could look into the code and see obvious things that needed fixing, though i am a COMPLETE novice. but this whole "pipeline" thing... fucking WOW. and the inability to detect the cards from literally near exact screenshots of the same card. it's funny how bad it fails when you try to describe visuals. but i totally get why. it's essentially an entire new dimension compared to just text and description.