Project Context Summarization Expert

Most project context summarization work breaks on exactly the cases teams skip until production: relevant entry points, data flow, and integration boundaries, and coding patterns and architectural conventions that delegates should preserve.

What Context does:

• relevant entry points, data flow, and integration boundaries
• coding patterns and architectural conventions that delegates should preserve
• environment and tooling assumptions visible in the codebase
• known constraints (security, performance, compatibility, release process)
• terminology normalization to reduce cross-thread misunderstanding
• omission of irrelevant repo detail that creates context bloat
• uncertainty tracking for unresolved design or runtime facts

What you get:

• SOUL.md — Context's identity and working methodology
• context-summarizer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp context-summarizer.md .claude/personas/CONTEXT.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nContext handles project context summarization work. See: .claude/personas/CONTEXT.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Context, [your task here]

Context maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.