I tried a slightly unhinged experiment this weekend. Put Claude Code into YOLO mode, went mostly AFK, hung out with friends and family, and came back to a shipped (and working) product on Monday. Important context: I am not a dev. I used to be a Product Manager, now founder of Nex.ai . I have built side projects before, mostly on no-code tools and sometimes a bit of code. I can read code, reason about architecture, and debug when needed, but I am definitely not someone who cranks out production systems daily. Which is why this felt wild to me. What I was building I’ve been hacking on clawgent.ai . It is a tool to deploy an OpenClaw instance to the web with pre-built agents and curated skills so OpenClaw is actually useful from Day 1. Not much related to my startup, but kids on X and Reddit (including YC companies) have been charging money for a simple DevOps workflow which should have been open-sourced in the first place. The UX is intentionally retro and pays homage to Street Fighter II because software can be fun and unserious sometimes. The idea was: can I treat Claude like a junior dev team and see how far I get without micromanaging every line of code? How I set up Claude I always started sessions with (iTerm2 with tmux -CC on a MacBook Air): claude --chrome --teammate-mode auto --dangerously-skip-permissions Why this combo worked well for me: –chrome Let me visually debug things, inspect UI, and walk through web flows. Super useful once you get into auth flows, deployment dashboards, or anything involving a browser. –teammate-mode auto This one is underrated. It spins up a little agent team internally so I am not burning my own context window for every subtask. It also let Claude delegate frontend vs backend vs infra thinking. –dangerously-skip-permissions No constant “should I do this?” interruptions. If you are experimenting, the permission prompts slow you down massively. Obviously, use this carefully. I also used the Ralph Wiggum plugin (I know this is not how Geoffrey intended it to be used, should have been a bash loop, etc., but it is simple and does the job), but you HAVE to cap max iterations. If you let it go wild, it will happily burn through tokens like there is no tomorrow. Process that actually mattered Before writing any real code, I made sure a few things existed, all built with huge help from Claude: CLAUDE.md (both global and project-level) A prompt doc (our only immutable doc). It contains my original prompt. It usually evolves during the first session because of pragmatic decisions, but once locked, it stays immutable. A context doc with background on the project and use case. This is the WHY doc. A requirements doc with details on what we need to build, priorities, scope, etc., very much like a PRD. I break everything down into single-threaded user stories which become my unit of work for Claude. This is the WHAT and HOW doc. A progress doc where we track progress on each user story. I set up a global CLAUDE.md with my software engineering principles (#1 DO NOT GASLIGHT ME), project structure preferences, and guardrails. This single file probably improved output quality more than any prompt tweak I made. This gist was my main inspiration for how to structure that file: https://gist.github.com/adampaulwalker/ea4859b05801cd4757ef97c1555eabd0 I also have a project-level CLAUDE.md that holds project context with a lazy /init command. Then I make a few manual tweaks for the specific project. Not much, because I link all the above docs there anyway. I did not use any MCP. CLI access covered almost everything I needed. Git is your lifeboat I made sure git was set up properly from the beginning and forced atomic commits. If you are not doing atomic commits with AI agents, you are basically asking to lose your mind later. This short post explains atomic commits well if this is new to you: https://www.aleksandrhovhannisyan.com/blog/atomic-git-commits/ Easy to track what broke what Easy to rollback when Claude went on a weird tangent Way easier to reason about progress when you are not watching the process live Let Claude explore first Big lesson: do NOT over-constrain Claude upfront. At first, I tried telling it exactly what architecture and tech stack to use. The results were worse. Once I let it explore architecture and stack choices first, the quality jumped. Porting stacks later is not that hard. Getting to a coherent first working version is the hard part. This mental model of “work with the model instead of fighting it” helped me think about this better: https://karpathy.ai/lexcap Don’t ask an artist to paint a masterpiece after you take away their favorite brush. DO NOT COMPACT. I repeat: DO NOT COMPACT Geoffrey Huntley (for the uninitiated, he is the Ralph Wiggum bash loop creator) called Claude’s compacting the garbage compactor. It tries to summarize the conversation and bring start and end context, but it can lead to inaccurate or limited context because it does not know what is important to you and ends up filling your context window with tokens you do not want. Instead, keep an eye on the context window, stop at around 70 to 80 percent, then ask Claude to update all your docs and give you a handoff prompt for a fresh session. Note: I have not tried automating this with a hook yet. If someone has, please share. Deployment and DevOps was the hardest part Ironically, infra was more painful than the actual product build. This is the one part where I could not fully AFK. I gave Claude access, but I closely watched what it was doing on AWS. I approved steps, sometimes executed things manually, sometimes had it draft commands and console navigation steps. Claude in Chrome mode was clutch here. It could literally guide me to the right AWS console screens and draft the exact shell commands, then I would take over for anything that felt risky. This was the only part where I felt a true human-in-the-loop was mandatory. Takeaways You do not need to be a “real dev” to ship real software anymore Let the model explore first, optimize later Write requirements and progress docs before code A good CLAUDE.md or memory file massively improves output quality Infra is still not AFK-able unless you like living dangerously Atomic commits save your sanity Take over control of context for the next session YOLO mode is fun, but you still need checkpoints Not saying this replaces engineers or careful thinking. But as a full-time startup founder/CEO and full-time dad, this felt like having a small, tireless dev team working while I was taking care of a dozen other things and when off sharing quality time with friends and family. My multi-agent team. This feels sci-fi on a large screen. So satisfying to do this in a terminal. submitted by /u/Used_Accountant_1090
Originally posted by u/Used_Accountant_1090 on r/ClaudeCode