Match code investigation questions to the appropriate tldr command. Find ways to inspect files, function calls, branching, variable flow, and line dependencies, helping you explore a project or investigate a bug.
Maps questions to the optimal tldr command. Use this to pick the right layer
Review the instructions the agent will receive before you install.
Maps questions to the optimal tldr command. Use this to pick the right layer.
tldr tree . --ext .py # File overview
tldr structure src/ --lang python # Function/class overview
Use: Starting exploration, orientation
tldr context <function> --project . --depth 2
tldr calls src/
Use: Understanding architecture, finding entry points
tldr cfg <file> <function>
Use: Identifying refactoring candidates, understanding difficulty
tldr dfg <file> <function>
Use: Debugging, understanding data flow
tldr slice <file> <function> <line>
Use: Impact analysis, safe refactoring
tldr search "pattern" src/
Use: Finding code, structural search
START
│
├─► "What exists?" ──► tree / structure
│
├─► "How does X connect?" ──► context / calls
│
├─► "Why is X complex?" ──► cfg
│
├─► "Where does Y flow?" ──► dfg
│
├─► "What depends on Z?" ──► slice
│
└─► "Find something" ──► search
| 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 |
The tldr-read-enforcer and tldr-context-inject hooks automatically:
You don't need to manually run these commands - the hooks do it for you.
If you need a specific layer the hooks didn't provide:
# Force specific analysis
tldr cfg path/to/file.py function_name
tldr dfg path/to/file.py function_name
tldr slice path/to/file.py function_name 42
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate background agents through saved files, keeping lengthy work transcripts out of the main conversation. It defines how to pass results between agents, monitor progress, and verify completed work with tests.
Delegate implementation, file reading, and testing to separate agents, then bring concise summaries back to the main conversation. The rules explain when delegation helps and when a small edit is better handled directly.
Organize implementation work across research, planning, validation, implementation, and review agents. Each stage passes files to the next, while implementation starts with failing tests and the main conversation coordinates the workflow.
Connect Agentica SDK agents to Claude Code CLI through a proxy, an intermediary server. Use setup and debugging guidance to address file permissions, streamed responses, result formatting, and agents reporting success without performing the requested operations.
Consult Agentica APIs when building workflows where multiple AI agents cooperate. This reference covers eleven coordination patterns, agent tracking, shared state, handoffs, and ways to combine results, with pointers to detailed API specifications.
Write clearer instructions for Agentica and REPL agents by specifying roles, file operations, and output formats. Includes templates for dividing research, coordinating specialists, reviewing solutions, and passing results between agents through files.