Topic: #claude-code

I built Daytripper and RepoFinder entirely with OpenAI Codex, then turned my Claude Code tooling loose on the results. The QA and design findings are numbered in the git history, one regression test cites the report that found the bug, and both products came out better than either agent would have produced alone.

Anthropic ships cookbooks for financial workflows. I did not see one for the problem I actually have: taking over a codebase with no docs, no tests, and no author. So I wrote it. This is the whole thing, top to bottom - the recipe, the building blocks (commands vs skills), the guardrails (ask vs enforce, hooks and all), and why Claude Code is the tool for a regulated fintech with three teams to serve.

Rocket Mortgage put Claude Code in front of the engineers who own their mortgage origination platform. A migration that had dragged for nearly 3 years shipped in 4 months, senior engineer throughput went up 145%, and client-impacting incidents after the cutover: zero.

I caught myself confidently misremembering my own architecture, so I asked Claude Code to read the code and tell me the straight truth. It corrected three things I believed, found an MCP server I forgot I shipped, and left me with a mental model worth sharing: southbound REST, northbound MCP.

RepoRadar was vibe-coded in four hours. Repo Recommender is the follow-up, built slowly and in the open with Claude Code: plan mode, CLAUDE.md, custom skills, a commit-blocking hook, an MCP server, and a 23-lesson book documenting every step.

My friend Vic is a C++ programmer who teaches people how to maximize credit card points. He had an idea. We sketched it on paper for ten minutes, then built the prototype in thirty-five.