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

Practical Prompt Structure for Claude AI Execution Agents
A developer shares prompt engineering techniques that reduced hallucinations in Claude AI agents performing API calls, data extraction, and multi-step workflows. Key strategies include writing prompts as contracts, dedicating 40% of tokens to error handling, and separating 'wait' from 'stop' conditions.

Running OmniCoder-9B locally with llama.cpp configuration details
A developer achieved 96.7% average HumanEval score with OmniCoder-9B on mid-range hardware using specific llama.cpp flags including --reasoning-budget 0 to disable chain-of-thought output. The setup used a Q6_K quantized model running on an RTX 3080 with 10GB VRAM.

Practical Claude Code Workflow for Development Teams
A Reddit user shares their internal presentation on Claude Code best practices, including model selection, structured workflows, and specific prompt techniques to improve output quality.

Mastering Backup: Safeguarding Your OpenClaw Agent
In an era dominated by automation and AI, ensuring the safety of your OpenClaw agent through robust backup strategies is paramount. Learn the essential steps to secure your digital assistant.