[brunooliv]

Am I the only one who uses CC in a one-shot fashion? I rely on what has been generated by the init slash command at the root of my monorepo and then when I have a complex task I manually create a md file called CONTEXT.md inside the package/area where I want to implement the new task. I try to be as detailed as possible, think like writing a ticket for a junior dev. Then my only command for CC is something like: “Focus on the project structure described in CLAUDE.md and work through the task planned in CONTEXT.md. Follow current codebase standards, keep code reusable and easy to follow and modify.”

This is like 99% of my CC interactions working on top of a well structured codebase and it just works perfectly for almost any task I throw at it.

[chrisvalleybay]

I mostly do the same. My workflow is usually like this: 1. Supply CC with a simple user story with light spec / business logic, asking it to write a specification for the feature and ask me any questions that need to be answered to make it complete. 2. Build up the context with all relevant files that I want to use. In Ruby on Rails it means refercing models, views and controllers that show the structure we are going to use. 3. Write the code and tests.

[brunooliv]

Nice to see!! I wrote a longer post about this: https://open.substack.com/pub/boliv/p/claude-code-usage-patt...

[sabrina_ramonov]

Not sure the complexity of your app but mine's pretty complex with many daily active users. One-shot rarely works unless it's a simple feature/chore and I tell CC exactly what to do, which functions to touch, and how (which defeats the purpose).