Vibe Coding Rules: Build Side Projects from Your Phone Using Claude Code Without Reading Code

✍️ OpenClawRadar📅 Published: May 21, 2026🔗 Source
Vibe Coding Rules: Build Side Projects from Your Phone Using Claude Code Without Reading Code
Ad

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 change repeatedly to ask questions like "What is
    about? 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 value gives confidence and prevents regressions.
Ad

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

Ad

👀 See Also

OpenClaw setup tips from a user's experience: Gmail MCP, profile flags, and networking issues
Guides

OpenClaw setup tips from a user's experience: Gmail MCP, profile flags, and networking issues

A user running OpenClaw on a Mac via UTM with Ubuntu VM shares specific configuration issues encountered: the Gmail MCP server requires html_body instead of body parameter, the --profile prod flag is needed to avoid a hardcoded dev identity, and API keys must be placed in auth-profiles.json via paste-token command.

OpenClawRadar
Fixing Claude Code's KV Cache Invalidation with Local Backends
Guides

Fixing Claude Code's KV Cache Invalidation with Local Backends

Claude Code versions 2.1.36+ inject dynamic telemetry headers and git status updates into every request, breaking prefix matching and forcing full 20K+ token system prompt reprocessing on local backends like llama.cpp. A configuration fix in ~/.claude/settings.json can reduce processing from 60+ seconds to ~4 seconds.

OpenClawRadar
🦀
Guides

OpenClaw 2026.9.1 Migration: Legacy Multi-Agent Upgrade Notes from r/openclaw

A user documents a smooth upgrade from OpenClaw 2026.7.1-2 to 2026.9.1, covering config migrations, schema updates, and multi-agent fixes—done via Codex in about 30 minutes.

OpenClawRadar
Route Claude Code through Ollama and Cut Your Bill ~90%
Guides

Route Claude Code through Ollama and Cut Your Bill ~90%

Pair Claude Desktop with Ollama-backed Claude Code: strategic work stays on Anthropic, heavy tasks run on free open-source models like Gemma, Qwen, DeepSeek. Includes a copy-paste prompt that automates ~98% of the setup.

OpenClawRadar