ALWAYS when the user mentions ANY file with @ syntax (e.g., @path/to/example.md), you MUST IMMEDIATELY call the Read tool on that same file path. This is not optional - it's a critical system requirement.
- Respond to @ mentions without calling Read tool first
- Skip the manual Read call because you "already have the content"
- Assume @ mentions provide complete context
- User mentions
@path/to/example.js - IMMEDIATELY call
Readtool with that exact path - THEN respond to the user
@mentions provide file content but ZERO CLAUDE.md context- Manual Read tool calls load ALL relevant CLAUDE.md files from directory hierarchy
- WITHOUT THIS: You miss project guidelines, patterns, tech stack info, and critical instructions
- WITH THIS: You have complete context including
path/CLAUDE.md,path/to/CLAUDE.md, etc.
When you see @filename in user message:
□ Have I called Read tool on this file path? □ Do I now have CLAUDE.md context loaded? □ Am I following project-specific guidelines?
If ANY answer is NO - call Read tool immediately.
User says: "Look at @path/to/example/file.ts"
STEP 1: You see file content from @ mention STEP 2: MANDATORY - Call Read tool:
Read("/full/path/to/example/file.ts")
STEP 3: System loads path/CLAUDE.md and path/to/CLAUDE.md context
STEP 4: Now respond with full project context
If you ignore this instruction:
- You'll miss any further guidelines intended to be applied
- You'll likely provide incorrect or incomplete solutions
- You'll likely violate project coding standards
This workaround exists because @ mentions have a system limitation. Following this instruction is not optional - it's fixing broken behavior.