// found 318 tips
The /add-dir command lets you expand Claude's file access to additional directories mid-session — essential for monorepos and shared libraries.
Ask Claude to write a git bisect test script, then paste the identified bad commit's diff for an instant explanation of what broke and why.
Configure a Stop hook to play a system sound the moment Claude finishes, so you can step away without constantly checking the terminal.
Open multiple terminal windows and run separate Claude Code sessions simultaneously to work on several tasks at once.
Ask Claude to add a rule to CLAUDE.md whenever you correct it, so the same mistake never happens twice.
Feed your PRD into Taskmaster to get a structured task list before writing any code — then work through it with Claude one task at a time.
Unused functions, unreferenced exports, and orphaned CSS classes accumulate silently — ask Claude to track them down before they become a maintenance burden.
Stop updating CHANGELOG.md by hand — pipe your git log to Claude and get a properly formatted Keep a Changelog entry appended in seconds.
When a problem is genuinely hard, the word "ultrathink" pushes Claude to allocate its maximum reasoning budget before responding.
The Postgres MCP server gives Claude read access to your real schema and data — so it writes SQL against your actual tables, not imaginary ones.
Jumping into an unfamiliar repo is painful — ask Claude to be your tour guide before you start making changes.
Paste a sluggish query and Claude will explain what's wrong, suggest indexes, and rewrite it — no DBA required.