ClaudeHack

Terminal / Productivity / Cost Optimization

16 hacks

  1. 1.

    Enable /voice and hold Space to speak complex requirements into the prompt instead of typing walls of text.

    0.00 points·1 month ago·easy·discuss
  2. 2.

    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.

    0.00 points·1 month ago·easy·discuss
  3. 3.

    Turn on `/sandbox` so OS-level filesystem and network boundaries replace many per-command Bash prompts.

    0.00 points·1 month ago·medium·discuss
  4. 4.

    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.

    0.00 points·1 month ago·easy·discuss
  5. 5.

    Instruct Claude (and yourself) to search with rg/Glob first so giant file reads do not blow the context window.

    0.00 points·1 month ago·easy·discuss
  6. 6.

    Enable auto mode so a classifier approves safe tool calls and blocks destructive ones — fewer prompts without a full permission bypass.

    0.00 points·1 month ago·easy·discuss
  7. 7.

    Cycle into plan mode (Shift+Tab) so Claude explores and proposes an approach for approval before editing.

    0.00 points·1 month ago·easy·discuss
  8. 8.

    Build slash skills that accept issue numbers, branch names, or formats via $ARGUMENTS / $0 so one command covers many cases.

    0.00 points·1 month ago·easy·discuss
  9. 9.

    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.

    0.00 points·1 month ago·easy·discuss
  10. 10.

    Shift specialized playbooks into on-demand skills so every session does not pay for instructions you rarely need.

    0.00 points·1 month ago·medium·discuss
  11. 11.

    Instead of guessing which commands to allowlist or giving up and skipping permissions entirely, let Claude read your past sessions and propose the rules you have already been approving.

    0.00 points·1 month ago·easy·discuss
  12. 12.

    Use /config to set Explanatory or Learning output style so Claude explains the why behind changes — not just the diff.

    0.00 points·1 month ago·easy·discuss
  13. 13.

    Mark deploy/ship/destructive skills so only an explicit /command runs them—Claude cannot auto-trigger them mid-session.

    0.00 points·1 month ago·easy·discuss
  14. 14.

    Save repeatable workflows as SKILL.md (or .claude/commands) so you slash-invoke consistent PR reviews, releases, or checklists.

    0.00 points·1 month ago·medium·discuss
  15. 15.

    Claude Code deletes session files older than 30 days at startup. If you have ever gone looking for a session you know you had, this setting is why it was gone.

    0.00 points·1 month ago·easy·discuss
  16. 16.

    Use /permissions to allowlist read-only and trusted commands so you stop mindlessly clicking Approve.

    0.00 points·1 month ago·medium·discuss