tribeca18

this looks so cool! I wish it told me if the levels found for tested products were good/bad - I have no prior reference so the numbers meant nothing to me

https://www.repoprompt.com is better. You need more granular control if you're planning to use this in real large codebases.

I use Cursor and Composer in agent mode on a daily basis, and this is basically exactly what happened to me.

After about 3 weeks, things were looking great - but lots of spagetti code was put together, and it never told me what I didn't know. The data & state management architecture I had written was simply just not maintainable (tons of prop drilling, etc). Over time, I basically learned common practices/etc and I'm finding that I have to deal with these problems myself. (how it used to be!)

We're getting close - the best thing I've done is create documentation files with lots of descriptions about the architecture/file structure/state management/packages/etc, but it only goes so far.

We're getting closer, but for right now - we're not there and you have to be really careful with looking over all the changes.

Damn this is me to a T.

Ahh just our luck with a untimely GraphQL issue - we just fixed!!

What's something you wish existed/suggest?

Makes me think of http://waldo.io, but for web apps! Really excited about the new wave of no-code test automation tools - definitely helps semi-technical team members take on more responsibility on the testing side vs. just writing specs.

Oddly specific, but this is such a great plausible example that I'm going to use from now on.

This is really cool! The inspiration behind creating this reminds me of another app too: https://getstack.app