This project uses a token-saving strategy to optimize Claude Code sessions. Follow these guidelines to minimize unnecessary context usage.
PRIMARY CONTEXT - Always available and relevant:
/lib/**- Core application code (shell scripts)/bin-edit/**- Binary editing utilities/completions/**- Shell completion scripts- Root-level essential docs:
README.md- Project overviewQUICKSTART.md- Getting started guideQUICK_REFERENCE.md- Command reference
MAIN EXECUTABLES:
aiwb- Main application binaryinstall.sh- Installation scriptuninstall.sh- Uninstallation script
DO NOT read these folders unless specifically asked:
Contains comprehensive documentation excluded by default:
- Legal files (LICENSE, CODE_OF_CONDUCT)
- Contributor guides (CONTRIBUTING, DEVELOPER_GUIDE)
- Architecture docs, audit reports, roadmaps
- Platform-specific guides (Termux documentation)
- Exception: Only read if user explicitly requests (e.g., "Read the audit report", "Show me CONTRIBUTING.md")
Contains test, debug, and utility scripts:
- Test suites (
test_*.sh) - Debug utilities (
debug_*.sh) - Platform installers (
install-termux.sh) - Exception: Only read when debugging or explicitly requested
Example configurations and usage demos.
Prompt templates and boilerplate files.
**/*.pdf- PDF documentation**/*.docx- Word documents**/*.png,**/*.jpg,**/*.jpeg,**/*.gif- Image files (unless debugging UI)- Generated HTML files
If you need something from an ignored folder:
-
User explicitly names a file:
- "Read docs/DEVELOPER_GUIDE.md" β Ask if they want to lift the restriction or proceed
-
Temporary access needed:
- Ask: "Would you like me to access the docs folder for this? It's normally excluded to save tokens."
-
Permanent changes needed:
- Edit
.claude/settings.jsonto remove ignore patterns
- Edit
For most coding sessions, focus on:
- Understanding the codebase in
/lib - Modifying core functionality
- Adding new features to existing modules
- Bug fixes and improvements
- Testing with the main
aiwbexecutable
Only expand context when:
- User asks for documentation updates
- Debugging requires reading test scripts
- Contributing guidelines are needed
- Architecture review is requested
- Start minimal: Begin with just the files you need
- Expand gradually: Add context only when necessary
- Ask before reading: If unsure about reading ignored content, ask the user first
- Respect the structure: The ignore patterns exist for a reason - to keep sessions efficient
Note: This configuration is enforced by .claude/settings.json. Modify that file to change ignore patterns permanently.