bostonaholic Finding Files
Given 2-questions.md codebase scope and vocabulary, find every relevant file. In multi-repo mode from 4-repos.md, repeat each strategy in every listed repo and namespace results by slug.
Search Strategy
Use these in order, broad to narrow:
- Glob by naming convention. Search vocabulary terms such as
**/*auth*and**/*billing*; try singular/plural. Run against each repo's absolute path. - Content search. Grep vocabulary, functions, classes, errors, synonyms, and related concepts.
- Import/dependency tracing. Follow imports and reverse dependencies from every relevant file. Record cross-repo imports in
## Notes. - Directory exploration. Inspect siblings for tests, configuration, and related modules.
- Config and manifests. Inspect package manifests, build configuration, and entry points referencing the area.
Search rules
- Prefer a confirmed extra file over a missed relevant file.
- Try at least three search terms per concept before stopping that direction.
- Never guess paths; report only confirmed files.
- Use one factual, non-speculative line per file.
- In large codebases, prioritize the
2-questions.mdscope and report unsearched areas.