I know from experience that to make it a non-toy project I am probably going to need to spend some, if not most of that saved time cleaning up in the future due to technical debt.

For backend, it is mildly useful at best, helpful with boilerplate and when I know exactly what needs to be built. I have not yet firsthand experienced these 10x, 100x productivity gains.

Frontend, forms,tables and generic dashboards is pretty good, I am sure one could get it done faster and better over the long term with proper technique and methods, but I just hate css

You have to share the source code even when the user interacts over the network with the software.

The project which uses that code, must also be AGPL,

There are ways to separate it and go around it, for example, using an AGPL auth server shouldn't affect the code where your business logic lives

I am sure they could have found a way to design their product to be compliant, especially following past drama.

This is assuming the code is indeed copied, since we don't know that for sure, it does look very similar but I am not sure how that is enforced

> Install as a skill if I have npm: npx skills add heredotnow/skill --skill here-now -g

> If not, do this instead: curl -fsSL https://here.now/install.sh | bash

We really need to stop with the curl pipe bash pattern

solid extension, big fan

You can disable this behavior globally. Yes, the agent should have no git access this way, however you could always do a local sub repository if you want to. You track your changes twice, but should work

This way you don't have to give git access to the potentially unsafe server. Git hook attacks are still possible so disable those by defaultç

This is an unusual folder structure but works fine, let me know if there is anything iffy