Hi, I'm Victor.
COO at MagmaLabs · Builder · Author of The Agentic Engineer.
I write about three things, usually overlapping: agentic engineering (what actually works when you build production software with Claude Code, MCP, and AI agents you can't fully predict), Ruby on Rails at production scale, and the leadership side of running an engineering team that uses AI seriously.
Most of it comes from shipping Forge (Rails 8 + production AI agents) at MagmaLabs, a handful of open-source MCP servers I've built along the way, and ten-plus years of figuring out how to ship good software without burning the team out.
Latest writing
- Loop engineering, after the noise
Loop engineering means designing the system that prompts your agent instead of doing it by hand — with a concrete RSpec loop you can run on a Rails app today.
- A wrong reconstruction is worse than an honest stack
Building framesmith v1.5's UI importer taught me the rule for any tool an agent consumes: be honest about your confidence, not just your output.
- MCP tool descriptions are the API: lessons from a Rails server
An agent disqualified a sales deal that should have been marked lost. The MCP server did exactly what it was told. Here's what I learned shipping a Rails MCP server an agent could actually use right.
- Inheriting a legacy Rails app in 2026: do this, not that
You just got onboarded to an 8-year-old Rails monolith. AI agents change the speed of the audit, not the work of understanding. Sixteen recommendations from a decade of watching engineers onboard.
- AI is a force multiplier for whatever habit you bring to it
Two engineers, same Claude Code, same task. Wildly different outcomes. AI doesn't make you better. It amplifies the habits you already had.
- Why I renamed canvas-mcp to framesmith
Why I rebranded canvas-mcp three weeks after shipping it — and a 5-question naming checklist I now run on every OSS project.
📖 The Agentic Engineer (book in review) · 🛠 Projects · GitHub · X · LinkedIn