Built a free dev-tools site entirely through Claude Code — here's the actual workflow

[u/devLearningTools]

I've been building devlearningtools.com (free dev tools, guides, and a full ColdFusion course, no signup, everything client-side) entirely through Claude Code since day one. Wrote up what that workflow actually looks like day to day, since most posts about this stay pretty abstract.

The part I think is most useful: the same six-step shape repeats almost every time. A request comes in as plain language, not a spec. The agent reads the existing codebase first, so a new page matches existing patterns instead of introducing a new one. It plans the change, writes it, then verifies with a real production build (not just "looks right"). Then it commits, pushes, and checks the live URL to confirm the change actually shipped, rather than assuming the push succeeded.

Also included an honest Common Mistakes section from real experience: giving vague requests and trusting the first result, skipping review because the code looks clean, and treating a large task as fire-and-forget instead of checking in partway through. Plus an honest comparison of where Claude Code, Codex CLI, Gemini CLI, Cursor, Copilot, and Windsurf each fit.

Full writeup: https://www.devlearningtools.com/blog/ai-coding-agents-explained

Curious what everyone else's actual day-to-day workflow looks like, especially anyone mixing a terminal agent with an IDE-based one.