Vibe Coding Rules: Build Side Projects from Your Phone Using Claude Code Without Reading Code
An experienced software engineer with a decade of experience posted a detailed workflow for what they call "vibe coding" — building side projects using Claude Code entirely from a phone, without ever reading the generated code. The post outlines a structured process that prioritizes planning and safety checks to make this hands-off approach viable.
Core Workflow
- Start in plan mode. Read the plan, understand it as much as possible. If unclear, ask. The author uses the command
4. Tell Claude what to changerepeatedly to ask questions like "What isabout? What does that mean?" - Go back and forth with the agent. Plan mode is the most important phase — good and bad decisions cascade and multiply.
- Break plans into small chunks. If the plan is too large to comprehend, ask the agent to break it into smaller digestible pieces and process them one at a time.
- Commit everything to git after each plan is complete. The author suggests creating a skill or memory that auto-commits. This enables rollback if something breaks. Note: database backups are separate.
- Generate test cases visible in the plan. You don't need to read test code, but a list like
it checks two positive integers,it checks passing a negative value,it checks not passing any valuegives confidence and prevents regressions.
Advanced Safety: Three Subagents
For complex changes, spin up three subagents to:
- critically review the plan
- do a security review
- do a testing audit
Database Caution
The author advises always doing a database backup (or having scheduled backups) before letting the agent touch prod data. Rollbacks prevent disasters like accidental deletion.
Auto Mode
Once the upfront work (planning, git, tests, reviews) is done, the author enables auto mode and lets the agent run. They also give the agent access to Chrome DevTools MCP (or similar) for end-to-end testing post-deployment.
The result: "You can build something that no one uses."
📖 Read the full source: r/ClaudeAI
👀 See Also
How to Set Up Sub-Agents with Separate Workspaces in OpenClaw
A community solution for configuring multiple sub-agents with isolated workspaces and different models
Local Translation Model Recommendations for 32GB VRAM GPUs
A developer shares tested recommendations for local translation models on a 32GB VRAM setup, highlighting Unsloth Gemma3 27b Instruct UD Q6_K_XL for general languages and Bartowski Utter Project EuroLLM 22B Instruct 2512 Q8_0 for European languages plus Korean.
Practical techniques to reduce state drift in multi-step AI agents
A developer shares concrete methods to fix state drift in multi-agent workflows, including snapshot-based reads, append-only writes, and separating state from context. These approaches made runs reproducible and debugging traceable.
Qwen3.5-397B MoE Runs on 14GB RAM via Paged Expert Loading on M1 Ultra
Paged MoE engine keeps only 20 experts resident and lazy-loads the rest from SSD, running a 209GB 397B model on a 64GB Mac Studio with 1.59 tok/s and 14GB peak RAM. Includes smaller model benchmarks.