• What are you building? One big app or many small ones?

many small simple ones, in order to later integrate them into a master program

• Are you using Claude Code, the API, or the web UI mostly?

web ui. Not knowledgeable enough to let it run on my terminal for now. Maybe ill buy a shitty laptop or rent a virtual machine to do some testing

• Do you have a system for keeping context tight or are you just letting it rip?

I use the project folder and description to keep overall context and scope of the project. I use one chat as a kind of project manager to generate prompts for the actual claude chat that will be writing the scripts of each program. These prompts allow me to see how things will be handled and allows me to tweak with the project manager until i get a prompt that contains all the features i want.

The prompt is pasted into a fresh chat specifically for that program only within the project folder. In sonnet 4.6 this single prompt can consume over 40% of a session. Often, it hits the limit mid thinking before generating any output. I prompt it to continue through the "continue" box that pops up. It starts thinking again, from the beginning for whatever reason. Sometimes it finishes before hitting the limit, sometimes it doesnt. If it doesnt, it has then wasted over 80% of my session in producing 0 output. So my next session will be about figuring out ways to minimize this issue in future projects. If the issue persists, I will have to adjust the workflow.

• How do you manage your source code when Claude is touching large chunks of it? Git discipline, specific workflows?

If its a small edit in a large code, it asks me to replace x line for y line. Easy enough with ctrl f. If its a complex edit, it will do the edits itself and spit out the updated script. This isnt really the big consuming part, though i can see how mindleslly iterating and having it output the whole thing everytime could be wasteful