14 hacks
Enable /voice and hold Space to speak complex requirements into the prompt instead of typing walls of text.
Use /effort (low→max) or CLAUDE_CODE_EFFORT_LEVEL so simple edits stay cheap and hard debugging gets deeper reasoning without paying max on every prompt.
Turn on `/sandbox` so OS-level filesystem and network boundaries replace many per-command Bash prompts.
Run claude remote-control on your machine, then connect from the Claude mobile app to approve builds, poke CI failures, and keep coding with full local tools.
Instruct Claude (and yourself) to search with rg/Glob first so giant file reads do not blow the context window.
Enable auto mode so a classifier approves safe tool calls and blocks destructive ones — fewer prompts without a full permission bypass.
Cycle into plan mode (Shift+Tab) so Claude explores and proposes an approach for approval before editing.
Build slash skills that accept issue numbers, branch names, or formats via $ARGUMENTS / $0 so one command covers many cases.
Add a Notification hook that plays a short sound when Claude is idle or waiting on permission so you can multitask without staring at the terminal.
Shift specialized playbooks into on-demand skills so every session does not pay for instructions you rarely need.
Use /config to set Explanatory or Learning output style so Claude explains the why behind changes — not just the diff.
Mark deploy/ship/destructive skills so only an explicit /command runs them—Claude cannot auto-trigger them mid-session.
Save repeatable workflows as SKILL.md (or .claude/commands) so you slash-invoke consistent PR reviews, releases, or checklists.
Use /permissions to allowlist read-only and trusted commands so you stop mindlessly clicking Approve.