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
- The most valuable spec-kit command is the optional one
After running spec-driven development across several projects, the step that pays for the whole workflow is the one the docs mark optional: clarify.
- framesmith 1.9: built for product screens
Charts as a first-class node type, reusable components, bulk edits, and an evaluator that knows a dashboard isn't a landing page. framesmith 1.9.0 is out.
- Your subagents are zombie processes
Orphaned subagents keep running and billing after their parent moves on. The fix isn't a smarter model — it's a lifecycle contract Unix shipped in 1985.
- framesmith 1.8: click the design, tell the agent
framesmith 1.8 makes human design feedback structured — click any element, type a note, and the agent gets it anchored to the exact node it belongs to.
- framesmith 1.7: teaching an agent when a design is done
framesmith 1.7 adds a vetted pattern library and a machine-readable 'done' contract, so an agent crafts a good UI and won't hand you a half-finished one.
- 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.
📖 The Agentic Engineer (book in review) · 🛠 Projects · GitHub · X · LinkedIn