Hooks, skills, and MCP as a build system
How do you extend Claude Code with hooks, skills, and MCP servers?
Claude Code gives you three extension points and they do different jobs: hooks fire on the agent's lifecycle so you can gate what it is about to do, skills carry the procedure you want followed instead of whatever it remembers, and an MCP server hands it tools and resources it could not otherwise reach. Guardian Kane uses all three, a Stop hook that grew into a twelve phase loop, a skill holding the procedure, and a kane-cli underneath, with a four tab dashboard showing the code graph, memory graph, PRD graph, and live activity. I have written up what the second build taught me about how much of it is wiring.
- Sep 21, 2026
8 min readThe Second Build Was Mostly Wiring
GuardianKane started as a PRD-to-task tool, became a Stop-hook gate, and then got rebuilt across twelve numbered phases. The lesson of the rebuild: most of it was connecting data that Kane CLI or my own hooks already produced, and the first phase fixed a bug that broke every fresh install.
- Sep 21, 2026
11 min readMaking Verification Visible
A pass or fail line at the end of a turn is not enough to trust an agent's build. A tour of GuardianKane's dashboard: the code, memory, and PRD graphs, the Kane activity feed, a chat panel wired into the live Claude Code session through an undocumented socket, and the bugs the dashboard exposed in the gate itself.