My most-used keystroke isn't Command-C. It's Command-Shift-1, my screenshot shortcut.
None of my go-to Claude Code habits are AI skills. They're Mac skills, and every Mac already has them built in.
A lot of working with Claude Code is getting what's in your head over to Claude: your idea, your problem, your preferences, and the assumptions behind them. The more clearly and quickly you can do that, the better Claude understands what you're actually asking for. These three shortcuts are how I do it, and I wish I'd known them on day one.
One note on my setup: I use Claude Code in the Claude desktop app on a Mac (the Code tab). Not a PC, and not Claude Code in the Terminal window, where some of these steps work differently.
1. Screenshot straight to your clipboard
I'm constantly screenshotting problems into the chat. A huge error message another program gave me. A section of my webpage whose layout I don't like. An image I don't recognize, with "what is this?"
Instead of describing the problem, I paste it.
Typing out an error code by hand is miserable, and you'll get a character wrongError messages are full of strings like ERR_MODULE_NOT_FOUND and file paths. One typo and Claude goes looking for the wrong problem.. A screenshot shows Claude exactly what you're seeing.
ERR_MODULE_NOT_FOUND and file paths. One typo and Claude goes looking for the wrong problem.The Mac's built-in shortcut is Control-Shift-Command-4. Drag a box around anything on your screen, and the picture goes to your clipboard instead of a file. Click into the Claude chat box and press Command-V.
That's four keys at once. Too awkward for something I do all day, so I changed mine to Command-Shift-1:
- Open System Settings → Keyboard.
- Click Keyboard Shortcuts, then Screenshots.
- Find Copy picture of selected area to the clipboard.
- Double-click its shortcut and press the keys you want.
The other win: no more Desktop covered in one-time screenshots named "Screenshot 2026-10-24 at 9.14.02 PM." I hate clutter.A clipboard screenshot never becomes a file, so there's nothing to clean up later.
2. A hotkey for voice dictation
Mine is the fn key (the one with the globe icon on newer Macs), pressed twice. I start talking, and the words show up wherever my cursor is, including the Claude chat box.
To set yours up, open System Settings → Keyboard → Dictation, turn it on, and pick a shortcut.
The Claude app has its own microphone button, but to me it feels a bit laggy. You'll also see a lot of hype about third-party dictation apps like Wispr Flow. I'd skip those, at least to start, because the dictation built into your Mac works well and costs nothing.
Dictation matters because you'll say far more than you'd ever type, and that extra detail is what helps Claude understand you.
Here's a good first session to try. Ask Claude Code to interview you: who you are, what you do, your projects, your priorities, anything else it should know. Then answer out loud. It doesn't have to be pretty. Ramble.Your dictation doesn't need to be perfect. It's OK to say “um, well, actually no, I meant...”
The conversation gets better when you stop typing and start talking.
3. Copy a file's path
A path is a file's address on your Mac. Something like /Users/michelle/Desktop/report.pdf.
To copy one, find the file or folder in Finder. Hold Option, click with two fingers on the trackpad (or right-click), and choose Copy as Pathname. Then paste it into Claude with Command-V.
Why do I need to know this?
Because sometimes Claude has to find the folder without you. I built a routine that watches my Downloads folder, sorts new files, and asks me where each one should go or whether to delete it. It runs on its own, so there's no one there to drag a folder in. The address has to be written into its instructions, and Copy as Pathname is how I got it. More on that one later.It's a bigger project than a 101 post.
Start with the screenshot
If you only learn one, make it the first. The next time something on your screen confuses you, don't type out what you're seeing.
Screenshot it, paste it, and ask.