{"slug": "vibe-coding-my-daily-workflow-with-claude-code", "title": "Vibe Coding: My Daily Workflow with Claude Code", "summary": "A developer outlines a practical workflow for \"vibe coding\" with Claude Code, emphasizing that initial project setup is too critical to delegate to AI. The engineer writes their own plan first, then debates it with Claude before proceeding, staying hands-on to question every change and prevent sloppy code.", "body_md": "This isn't a tutorial or hype piece. These are insights into how I use vibe coding efficiently in my actual work.\n\nIf you are using a local LLM, go ahead. If you're using commercial tools like Claude or Codex, check first, whether this project can be developed with vibe coding. It's upto client's call.\n\nNo approval? Build it yourself.\n\nClient approves? Then you're good to proceed.\n\nI'll break this into three scenarios:\n\n*I'm assuming Claude Code for vibe coding throughout.*\n\nMy standard approach:\n\nMost people say: *\"Use AI for planning from the start because initial setup is critical.\"*\n\n**I disagree. Initial setup is too critical to skip.**\n\nI write my own plan first, based on the requirements. I also document the requirements it in `claude.md`\n\nor a separate skill depending on what I need. Then I ask Claude to create a plan in plan mode, and we compare.\n\nI research the AI's suggestions, question them, and decide to go with either mine, theirs, or merge both.\n\nSame process. plan debate with Claude, create a new skill for the output.\n\nI use separate skills to save tokens and avoid hallucination.\n\nOnce we agree on the plan, I tell Claude to proceed, but I stay hands-on. I interrupt and ask why before accepting any change which I don't fully understand. If I disagree, I propose my approach instead.\n\nThis prevents sloppy code and keeps token usage down\n\nIt depends on the bug.\n\nThat's it. No magic, no shortcuts. just staying in control while letting AI handle the heavy lifting", "url": "https://wpnews.pro/news/vibe-coding-my-daily-workflow-with-claude-code", "canonical_source": "https://dev.to/buvanesh/vibe-coding-my-daily-workflow-with-claude-code-2pkg", "published_at": "2026-05-26 06:42:11+00:00", "updated_at": "2026-05-26 07:03:36.948239+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "large-language-models", "generative-ai", "ai-products"], "entities": ["Claude Code", "Claude", "Codex"], "alternates": {"html": "https://wpnews.pro/news/vibe-coding-my-daily-workflow-with-claude-code", "markdown": "https://wpnews.pro/news/vibe-coding-my-daily-workflow-with-claude-code.md", "text": "https://wpnews.pro/news/vibe-coding-my-daily-workflow-with-claude-code.txt", "jsonld": "https://wpnews.pro/news/vibe-coding-my-daily-workflow-with-claude-code.jsonld"}}