64 hacks, newest first
Ask Claude to log architecture decisions and TODOs into a repo file that can be re-read after /compact.
Enable /voice and hold Space to speak complex requirements into the prompt instead of typing walls of text.
Connect the Claude in Chrome extension so Claude can open your app, click through flows, read console errors, and iterate until the UI actually works.
Create a skill that forces a red→green verification loop so Claude cannot claim done without running the suite.
Add the words "use a workflow" to a prompt and Claude writes a JavaScript orchestration script that runs subagents in the background, keeping only the final answer in your context.
When Claude repeats a project gotcha, end your prompt with an instruction to write a CLAUDE.md rule so it never happens again.
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.
Inspect `/usage` (alias `/cost`) for per-skill, subagent, and MCP breakdowns, then cut the expensive outliers.
Spelling out do-this-then-that is now the common failure mode. Describe the goal, the constraints and how Claude knows it is done, then leave the method alone.
Install the GitHub app and mention @claude in review comments so corrections become durable CLAUDE.md rules for every future session.
Keep the root CLAUDE.md short and drop domain-specific CLAUDE.md files under paths like src/db/ so Claude loads them only when it works in that area.
Spin up a subagent for codebase search or verification so only the conclusion returns to your main context.
Proactively run `/compact` with focus instructions so summaries keep the work that matters instead of stale debugging.
Schedule an early Claude Code run so your usage window resets around lunch instead of mid-afternoon.
Every installed skill spends context just being listed, before you invoke anything. Sort the list by cost, then set the ones you never use to name-only.
Write the plan in one session, then open a fresh Claude with no context and ask it to review the plan like a staff engineer.
Use bundled /loop and /schedule skills for recurring health checks, log watches, or periodic repo tasks without external cron wiring.
Turn on `/sandbox` so OS-level filesystem and network boundaries replace many per-command Bash prompts.
End implementation prompts with /simplify so parallel agents review reuse, efficiency, quality, and CLAUDE.md compliance in one sweep.
Use /init to generate a starter CLAUDE.md, then delete anything inaccurate or obvious before committing.
Double-Esc /rewind back to after useful file reads, then re-prompt with what you learned—without the failed approach still in context.
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.
Put a single `@AGENTS.md` import in CLAUDE.md so Claude Code and other agent tools share the same project instructions without symlink confusion.
Force verification with prompts like “prove this works” and “grill me before the PR” so Claude has to validate instead of declaring done.