Reference Architecture · v1.0

The Agent Development Kit.

5Layers
2Adjacent surfaces
1Runtime

Five composable layers that turn Claude Code from a code assistant into a governed, distributable agent runtime. Memory, knowledge, guardrails, delegation, and distribution — wired together and ready to ship.

01

The Five Layers

Memory · Knowledge · Guardrails · Delegation · Distribution
01Memory

CLAUDE.md Always-on constitution

The agent's persistent context. Loaded on every turn, never forgotten. Defines architecture rules, naming conventions, test expectations, and the repository map. Project scope overrides global scope.

~/.claude/CLAUDE.md .claude/CLAUDE.md always loaded
02Knowledge

Skills On-demand expertise

Modular context packs invoked by description matching. The agent loads only what the current task needs — reference docs, scripts, templates — inside an isolated subagent so the main context stays clean.

SKILL.md description-match auto-invoke isolated fork
03Guardrails

Hooks Deterministic enforcement

Event-driven, non-AI policy enforcement — Git hooks for your agent. Events fire, matchers run, commands execute. No model in the loop, no ambiguity. The compliance layer for production agents.

PreToolUse PostToolUse SessionStart Stop SubagentStop deterministic
04Delegation

Subagents Scoped specialists

Specialised workers with their own context, model, tools, and permissions. The main agent delegates and receives results — no infinite recursion, no context pollution. Code-reviewer, test-runner, explorer, anything you define.

own context own model own tools own permissions no recursion
05Distribution

Plugins Shippable capability bundles

Skills, agents, hooks, and commands packaged as one unit. Install across your team or publish to a marketplace. A package format for agent capabilities — versioned, distributable, reusable.

skills/ agents/ hooks/ commands/ team install
02

Adjacent Surfaces

MCP & Agent Teams
Inbound integration

MCP Servers

The bridge to the outside world. Any tool, any system, exposed to the agent through the Model Context Protocol — one open standard, no glue code per integration.

  • External tools
  • GitHub
  • Databases
  • APIs
  • Custom integrations
Outbound coordination

Agent Teams

Multiple agents working in parallel with shared permissions and message passing. A lead orchestrates, specialists execute. The pattern that scales from prototype to production.

  • Parallel execution
  • Message passing
  • Lead orchestration
  • Shared permissions
03

The Flow

5-step recap · how the layers compose
01 · Rules CLAUDE.md sets the constitution
02 · Expertise Skills add domain knowledge
03 · Quality Hooks enforce the gates
04 · Delegation Subagents do the work
05 · Shipping Plugins ship to the team
04

Verified Resources

Official docs & primitives
MEMBER · FREE

Read the full article or download as PDF

The full article and the PDF are member content. Magic-link login, no credit card, no risk — both available immediately.