AiDD (Dev Workflows)▌

33:T433,Build a structural map of source code files in a directory. This tool analyzes code structure to identify classes, functions, and methods. WHEN TO USE: When you need to understand the structure of a codebase, discover classes and functions across multiple files, identify inheritance relationships, or get a high-level overview of code organization without reading every file individually. WHEN NOT TO USE: When you need to search for specific text patterns (use search_files instead), when you need to analyze a single known file (use read_file instead), or when you're working with non-code files. SUPPORTED LANGUAGES: Python (.py), JavaScript (.js/.jsx), TypeScript (.ts/.tsx), Java (.java), C++ (.cpp), Ruby (.rb), Go (.go), Rust (.rs), PHP (.php), C# (.cs), Kotlin (.kt). RETURNS: A text-based tree structure showing classes and functions in the codebase, along with statistics about found elements. Only analyzes files within the allowed directory. Example: Enter '.' to analyze all source files in current directory, or 'src' to analyze all files in the src directory.34:T4e1,Execute multiple tool invocations in parallel or serially. WHEN TO USE: When you need to run multiple operations efficiently in a single request, combine related operations, or gather results from different tools. Useful for bulk operations, coordinated tasks, or performing multiple queries simultaneously. WHEN NOT TO USE: When operations need to be performed strictly in sequence where each step depends on the previous step's result, when performing simple operations that don't benefit from batching, or when you need fine-grained error handling. RETURNS: Results from all tool invocations grouped together. Each result includes the tool name and its output. If any individual tool fails, its error is included but other tools continue execution. Parallelizable tools are executed concurrently for performance. Each tool's output is presented in a structured format along with the description you provided. IMPORTANT NOTE: All tools in the batch execute in the same working directory context. If a tool creates a directory and a subsequent tool needs to work inside that directory, you must either use paths relative to the current working directory or include an explicit tool invocation to change directories (e.g., update_allowed_directory).35:T426,Capture a screenshot of the current screen and save it to a file. This tool allows capturing the entire screen, the active window, or a specific named window. The screenshot will be saved to the specified output path or to a default location if not provided. WHEN TO USE: When you need to visually document what's on screen, capture a specific application window, create visual references for troubleshooting, or gather visual information about the user's environment. Useful for documenting issues, creating tutorials, or assisting with visual tasks. WHEN NOT TO USE: When you need information about windows without capturing them (use get_available_windows instead). RETURNS: A JSON object containing success status, file path where the screenshot was saved, and a message. On failure, includes a detailed error message. If debug mode is enabled, also includes debug information about the attempted capture. Windows can be captured in the background without bringing them to the front. Works on macOS, Windows, and Linux with platform-specific implementations.36:T41f,Get detailed system information about the host computer. WHEN TO USE: When you need to understand the system environment, diagnose performance issues, verify hardware specifications, check resource availability, or determine the operating environment for compatibility reasons. Useful for system analysis, troubleshooting, environment verification, and providing context-aware assistance. WHEN NOT TO USE: When you only need the current working directory (use get_allowed_directory instead), when specific file information is needed (use get_file_info instead), or when you need to interact with applications rather than system information (use get_active_apps instead). RETURNS