Add a Stop hook that plays a system sound when Claude completes a response. Kick off a task, switch to something else, and hear a ping when it's done. json { "hooks": { "Stop": [ { "matcher": "", "hooks": [ { "type": "command", "command": "/usr/bin/afplay /System/Library/Sounds/Glass.aiff" } ] } ] } } 49. Fan-out with claude -p for batch operations Loop through a list of files with non-interactive mode. --allowedTools scopes what Claude can do per file. Run them in parallel with & for maximum throughput. bash for file in $(cat files-to-migrate.txt); do claude -p "Migrate $file from class components to hooks" \\\\ --allowedTools "Edit,Bash(git commit )" & done wait This is great for converting file formats, updating imports across a codebase, and running repetitive migrations where each file is independent of the others. 50. Customize the spinner verbs (the fun one) While Claude thinks, the terminal shows a spinner with verbs like "Flibbertigibbeting..." and "Flummoxing...". You can replace them with whatever you want. Tell Claude: Replace my spinner verbs in user settings with these: Hallucinating responsibly, Pretending to think, Confidently guessing, Blaming the context window You don't have to provide a list either. Just tell Claude what vibe you're going for: "Replace my spinner verbs with Harry Potter spells." Claude generates the list. It's a small thing that makes the wait more enjoyable. Wrapping up You don't need all 50. Pick the one that solves the thing that annoyed you most in your last session, and try it tomorrow. One tip that sticks is worth more than fifty you bookmarked. I write about Claude Code regularly. Check out my other Claude Code guides. Want to publish your own Article? Upgrade to Premium 6:29 pm · 19 Mar 2026 · 196K Views