Easy Context Executor

Load project context files (README, architecture docs, CLAUDE.md) into the conversation so Claude has full awareness of your project before executing subsequent tasks.

When to Use This Command

Run this command when...

• You are starting a new conversation and want Claude to understand your project immediately
• You want Claude to follow project-specific conventions documented in CLAUDE.md
• You need Claude to be aware of your tech stack, coding standards, and directory layout

Avoid this command when...

• Claude already has sufficient context from earlier messages in the conversation
• You are working on an isolated task that does not require broad project awareness

Quick Start

Copy
# .claude/commands/easy-context-executor.md
---
allowed-tools: ["Read", "Glob", "Grep"]
---
Find and read all project context files: CLAUDE.md, README.md,
ARCHITECTURE.md, .claude/settings.json, package.json.
Summarize the project structure and conventions.

Example usage:

/easy-context-executor

Example output:

Project Context Loaded
======================
Project: MyApp (Next.js 14 + TypeScript)
Stack: React, Tailwind CSS, Prisma, PostgreSQL

Conventions (from CLAUDE.md):
  - Use server components by default
  - API routes in app/api/ with Route Handlers
  - Tests: Vitest for unit, Playwright for e2e

Structure:
  src/app/        Pages and layouts
  src/components/ Shared UI components
  src/lib/        Utilities and helpers
  prisma/         Database schema and migrations

Core Concepts

Concept	Description
Context files	CLAUDE.md, README.md, ARCHITECTURE.md, package.json
Convention loading	Reads project-specific rules and coding standards
Stack detection	Identifies frameworks, languages, and tools from config files
Persistent context	Loaded information stays available for the rest of the session

Project Root --> Scan for Context Files
                      |
        +-------------+-------------+
        |             |             |
    CLAUDE.md    README.md    package.json
        |             |             |
        +--- Parse & Summarize -----+
                      |
              Context Available

Configuration

Option	Default	Description
files	auto	Specific context files to load by path
depth	2	Directory depth for the structure summary
include-deps	true	Parse package.json or requirements.txt dependencies
include-scripts	true	List available npm scripts or Makefile targets
summary	true	Print a summary after loading context

Best Practices

1. Create a CLAUDE.md -- this is the single most impactful context file. Document conventions, patterns, and gotchas.
2. Run at the start of sessions -- context loaded early prevents Claude from making wrong assumptions later.
3. Keep context files updated -- stale documentation leads to stale assumptions and wrong patterns.
4. Include architecture decisions -- link to ADRs so Claude understands why design choices were made.
5. Keep it concise -- a 200-line CLAUDE.md is more useful than a 2000-line information dump.

Common Issues

1. No context files found -- create at least a CLAUDE.md at the project root with basic conventions and project structure.
2. Context too large for token limit -- if files exceed token limits, the command summarizes. Put the most critical info in CLAUDE.md.
3. Stale information loaded -- outdated conventions cause Claude to use deprecated patterns. Review context files quarterly.