Building software with agentic AI development
Agentic development is a genuine step-change in how software gets built — but only if it is driven, not trusted blindly. I run AI coding agents as fast, tireless pair-programmers inside a workflow with real guardrails, so you get the speed without the mess.
Agents driven by rules, hooks and context
The difference between an agent that helps and one that thrashes is the setup. I configure Claude Code with custom rules and hooks, pull live library docs through Context7/MCP, and give agents the project conventions up front — so they produce code that matches the codebase instead of generic boilerplate. Codex and Cursor fill the same role where they fit better.
Spec-first, small steps, always reviewable
I work spec-first: agree the change, let the agent implement it in small, reviewable increments, and keep a human in the loop at every step. That keeps the work legible and lets me catch a wrong turn in seconds rather than after a thousand lines.
Guardrails so speed never costs quality
Every agent output goes through the same gates as any code: type-checking, tests (Jest, Vitest, Playwright) and automated review with CodeRabbit before merge. The result is the throughput of agentic development with the reliability your product needs — I built an internal Rust CLI and standardised tooling across projects exactly this way.
- Agents configured with custom rules, hooks and live context (Context7/MCP).
- Spec-first, small increments, human-in-the-loop at every step.
- Type-checks, tests and CodeRabbit review gate every change.