Terminal Productivity Tips for Developers (with Sweet! CLI)

1) Make navigation instant

• Use a fuzzy directory jumper (e.g. zoxide) so you can jump between projects fast.
• Keep your repo roots predictable (e.g. ~/code/<project>) so tools and scripts are consistent.
• Prefer absolute paths in automation to reduce “where am I?” errors.

2) Turn command history into a knowledge base

• Aliases for intent: gst, gco, gpf are faster than full commands.
• Use history search (Ctrl+R) aggressively; it’s “documentation” you already trust.
• Capture recurring sequences as scripts in scripts/ (versioned, shareable).

3) Reduce risk with safer defaults

• Dry-run before destructive operations: think --dry-run, or print targets first.
• Prefer explicit globs over broad deletes.
• Keep logs for long-running tasks (redirect output to a file you can inspect).

4) Debug faster with “tight loops”

The fastest debugging loop is: reproduce → isolate → inspect → fix → verify. Sweet! CLI helps in the “inspect” and “fix” steps by exploring code quickly and proposing targeted changes.

• Paste the exact error and the command you ran.
• Link to the file and line number when you have it.
• Ask for the smallest safe change first, then iterate.

5) Pair your shell workflow with Sweet! CLI

• Use /workfor 45m when you want a timeboxed “autopilot” burst.
• Use /todos to track your progress and maintain momentum.
• Use /jobs to keep long tasks running while you stay productive.