Fixing my messy terminal workflow w

Context switching between a messy terminal, a documentation tab, and a code editor is a productivity killer, especially when you're fighting with obscure awk or sed syntax. I spent way too long manually searching StackOverflow for one-liners that barely worked, so I built a "Terminal Command Architect" prompt to turn the LLM into a precise CLI consultant rather than a generic chat bot.

The goal here isn't just to get a command, but to get a safe and explainable one. Most AI-generated shell commands are risky because they lack context about the current environment or ignore edge cases (like filenames with spaces).

Here is the prompt I'm using:

Act as a Senior DevOps Engineer and Shell Scripting Expert. Your goal is to provide the most efficient, POSIX-compliant terminal command for a specific task.

Follow these strict output constraints:
1. **Command**: Provide the exact command in a single code block. Use placeholders like `<file_path>` for user-defined variables.
2. **Breakdown**: Explain every flag and pipe used. If you use `grep -r`, explain exactly what `-r` does in this context.
3. **Safety Check**: Identify any destructive actions (e.g., `rm`, `>`) and provide a "Dry Run" version of the command using `echo` or a similar non-destructive method.
4. **Alternative**: Provide a faster or more modern alternative (e.g., using `ripgrep` instead of `grep` or `fd` instead of `find`) if it's significantly better.

Context: [Insert your OS, Shell (zsh/bash), and specific goal here]

The magic here is the Safety Check and the Breakdown. By forcing the AI to provide a "Dry Run" version, I stop myself from accidentally nuking a directory because I missed a slash in a find -exec rm command. Also, forcing a breakdown of every flag prevents the "black box" effect—I actually learn the syntax instead of just copy-pasting.

For example, I recently had to find all .log files larger than 50MB modified in the last 3 days and move them to an archive folder. Instead of guessing the find syntax, I fed this into the prompt.

The output looked like this:

Command:

find <search_directory> -type f -name "*.log" -size +50M -mtime -3 -exec mv {} <archive_directory>/ \;

Breakdown:
-type f: Look for files only.
-name "*.log": Filter by extension.
-size +50M: Files larger than 50 Megabytes.
-mtime -3: Modified within the last 3 days.
-exec mv {} ... \;: Executes the move command on every match.

Safety Check:
Run this first to see which files will be moved:

find <search_directory> -type f -name "*.log" -size +50M -mtime -3

Alternative:
If you have fd installed, this is much faster:

fd -e log --size +50M --changed-within 3d -x mv {} <archive_directory>/

This structure removes the fluff. I don't need the AI to tell me "Sure, I can help you with that!" or "Here is a helpful command." I just need the syntax, the risk assessment, and the modern alternative. It turns the terminal from a place of anxiety into a streamlined tool.