one shotting/"context engineering" larger apps or bigger code changes with claude code gives me fragile results. common issues:

- too much code gets generated. flows might work, but the code is slop.
- many UI/UX bugs. every iterative fix dirties the code further.
- claude invents new features/abstractions that I never asked for

what's working better for me is acting as the architect. I break down the task myself into what would usually be 15-30 minute sessions if I were to write the code manually.

- I ask claude to implement each increment
- I test it and give feedback to claude
- I then review the code and ask for any necessary refactors
- git commit -m "checkpoint"
- rinse and repeat

this places me in the role of PM/tech lead on a team. results in better UX and more resilient code.

"hell no, I don't vibecode! I take pride in my craft and write things myself" said a devrel at cannes. I'm at the opposite end of the spectrum using LLMs all day and almost don't look at code anymore. here's what I do

hellno vibe coding snapshot july 2025
· use subtasks in parallel: overall speedup and LLMs are good at deciding what should be done in sequence vs at the same time in different processes

· get context and write lean PRDs: force the LLM to think longer improves everything. I was hesitant to do this after seeing @jc4p and @stephancill casting about it. turns out they are so right! taking time before writing code increases output quality A LOT and saves time to not get stuck in bug fix-vibe debugging loops later. 

· increase input speed
A) use snippets to replace keywords into expanded prompts. tiny example: /par → continue, execute subtasks in parallel if possible 
B) speech to text is fun and much faster. might require setting up some dictionary to recognize some words, but overall fast and easy

I had some success with forcing it to think through PRDs and iterating to not get too much code and no hallucination. from there it can one-shot big features pretty well

exploring. prev: @clankfun, improbable, github. https://ntik.me

I had some success with forcing it to think through PRDs and iterating to not get too much code and no hallucination. from there it can one-shot big features pretty well https://farcaster.xyz/hellno.eth/0x124d02cb