Agentic Workflow

Engineering the Guardrails

Built end-to-end with the assistance of Claude Code (CC❤️). The engineering is in the system that keeps the LLM from drifting the codebase: a thin resident contract, read-on-demand docs, codegen kept in lockstep with schema, and commit-time guards that catch the "forgot to update the other copy" class of error.

  • Platform
  • Product Engineering
  • AI-Assisted Development
  • Developer Tooling
  • System Design
  • CI/CD
  • Technical Leadership

Overview

  • Every feature here was built with a coding agent (Claude Code). An agent has a finite attention budget and no memory between sessions — it'll duplicate a fact, hand-edit a generated file, or drift a doc unless the repository catches those mistakes.

  • So the architecture I'm most proud of isn't a feature, it's the operating contract: a tiny always-resident CLAUDE.md of guardrails plus pointers, the heavy detail pushed into docs the agent reads before risky work, and commit-time hooks that turn a fact-that-drifted into a fact-that-can't-be-committed. The diffs are the evidence — across a run of merges the generated layers stayed in sync while the hand-maintained prose fell out within days. The fix: generate or guard everything that can drift.

  • The other half is process discipline: branch-fresh gitflow, conventional commits, one PR per change, every substantial PR carrying a "Decisions & alternatives considered" section — which is why a content pass like this one can reconstruct the why behind dozens of merges.

System Design