Tags › #Claude Code 6 posts
-
Building a Self-Improving Personal Knowledge Base Powered by LLM
Inspired by Andrej Karpathy's post on LLM knowledge bases, I built a system where Claude Code skills manage a personal wiki end-to-end — ingesting raw content, compiling concept articles, synthesizing connections, and answering questions. You never touch the wiki. The LLM owns it.
-
Multi-Agent Patterns: Swarm, Teammates, and the Coordinator
Claude Code can run multiple Claude instances in parallel within the same process. Here's how in-process teammates, permission sync, and coordinator mode work — and what it means for building your own multi-agent system.
-
Designing for Extensibility: How Claude Code's Plugin and Skill System Works
Claude Code has two extension points: skills (slash commands that inject prompt content) and plugins (packages that contribute commands, MCP servers, and hooks). Here's how each works and why they're designed differently.
-
Security Without a Sandbox: How Claude Code Decides What It's Allowed to Do
Claude Code runs shell commands, edits files, and makes network requests on your machine — without a kernel sandbox. Here's the permission model that makes this safe enough to ship.
-
The Tool Use Loop: How Claude Code Executes Code, Edits Files, and Talks Back
A tool call is a structured JSON request from the LLM to run a named function. Here's exactly how Claude Code handles the full lifecycle — from API call to file edit to loop continuation.
-
Demystifying Claude Code: Inside the Architecture of a CLI Code Agent
Claude Code is one of the most widely used AI coding tools and one of the least understood. We read the source so you don't have to.