TLDR Smart Router Maps questions to the optimal tldr command. Use this to pick the right layer. Question → Command Mapping "What files/functions exist?" Use: Starting exploration, orientation "What does X call / who calls X?" Use: Understanding architecture, finding entry points "How complex is X?" Use: Identifying refactoring candidates, understanding difficulty "Where does variable Y come from?" Use: Debugging, understanding data flow "What affects line Z?" Use: Impact analysis, safe refactoring "Search for pattern P" Use: Finding code, structural search Decision Tree Intent Detection Keywords Intent Keywords Layer Navigation "what", "where", "find", "exists" tree, structure, search Architecture "calls", "uses", "connects", "depends" context, calls Complexity "complex", "refactor", "branches", "paths" cfg Data Flow "variable", "value", "assigned", "comes from" dfg Impact "affects", "changes", "slice", "dependencies" slice/pdg Debug "bug", "error", "investigate", "broken" cfg + dfg + context Automatic Hook Integration The tldr read enforcer and tldr context inject hooks automatically: 1. Detect intent from your messages 2. Route to appropriate layers 3. Inject context into tool calls You don't need to manually run these commands the hooks do it for you. Manual Override If you need a specific layer the hooks didn't provide:

tldr-router