Tagged “Claude Code”

• ADRs for AI coding agents: how to make every agent read architecture decisions

  Architecture decision records only help AI coding agents when the right record enters context at the right time. Use this setup for Cursor, Claude Code, and other agents.

• CLAUDE.md vs agent memory: what each should store

  CLAUDE.md, auto memory, task handoffs, and shared team decisions solve different context problems. Use this guide to decide what belongs where.

• How to share memory between Cursor and Claude Code

  Cursor and Claude Code keep different personal context. Use repo rules, task handoffs, live tools, and shared team decisions so work can move between them without a fresh explanation.

• Why Claude Code forgets architecture decisions - and how teams stop re-explaining them

  Claude Code can understand a codebase and still lose the reasoning behind architecture decisions. Here is what to save, where to save it, and how to keep every agent aligned.

• How cross-vendor agent capture works: hooks, MCP, and instruction files

  Every major coding agent exposes the same three surfaces. How Lockstep uses lifecycle hooks, an MCP server, and instruction files to capture agent work.