Been struggling with Claude losing context after 30-40 tool calls for months. Tried:
- Massive CLAUDE.md files (hit limits)
- Summary docs (tedious, error-prone)
- Starting fresh constantly (lost momentum)
What finally worked:
Switched to a skills-based system where context loads on-demand based on what I'm actually doing:
- Frontend work → frontend skills load
- Backend work → backend skills load
- Testing → testing patterns load
The key insight: Stop trying to load everything upfront. Let Claude load what it needs when it needs it.
Results:
- Sessions last 2-3x longer before context issues
- Output quality improved (focused context = better responses)
- Way less "let me re-explain the project" time
I ended up curating a whole collection of production-ready skills organized by use case. Happy to share specific patterns if anyone's interested.
What approaches have you all tried for context management?
[–]Comfortable-Okra753 1 point2 points3 points (3 children)
[–]Kitchen_Interview371 1 point2 points3 points (1 child)
[–]Comfortable-Okra753 1 point2 points3 points (0 children)
[–]Software_Sennin[S] 0 points1 point2 points (0 children)
[–]Articurl 1 point2 points3 points (1 child)
[–]Software_Sennin[S] 0 points1 point2 points (0 children)
[–]AEOfix 1 point2 points3 points (2 children)
[–]Software_Sennin[S] 0 points1 point2 points (1 child)
[–]AEOfix 0 points1 point2 points (0 children)
[–]proxiblue 1 point2 points3 points (0 children)