64 practical Claude and Claude Code workflows, ranked by the people who use them. Every hack cites its source and gets re-verified.
Schedule an early Claude Code run so your usage window resets around lunch instead of mid-afternoon.
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.
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.
Most CLAUDE.md lines exist to correct a model that no longer makes that mistake. Delete them after an upgrade and re-add only the ones a failure proves you need.
Proactively run `/compact` with focus instructions so summaries keep the work that matters instead of stale debugging.
Enable auto mode so a classifier approves safe tool calls and blocks destructive ones — fewer prompts without a full permission bypass.
When Claude repeats a project gotcha, end your prompt with an instruction to write a CLAUDE.md rule so it never happens again.
Spin up a subagent for codebase search or verification so only the conclusion returns to your main context.
Enable /memory auto-memory so Claude writes durable notes about build commands, corrections, and patterns that reload on every new session.
End implementation prompts with /simplify so parallel agents review reuse, efficiency, quality, and CLAUDE.md compliance in one sweep.
Use `claude --worktree` (or git worktrees) so multiple agents edit isolated checkouts without colliding.
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.
Trim project memory to under ~200 lines so Claude follows critical rules instead of drowning them in noise.
Use /btw for single-turn clarifications that share full context but never enter conversation history or burn future tokens.
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.
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.
Double-Esc /rewind back to after useful file reads, then re-prompt with what you learned—without the failed approach still in context.
Claude Code re-reads your whole conversation at the cached rate. Come back after a long lunch and the first message reprocesses all of it at full price.
Force verification with prompts like “prove this works” and “grill me before the PR” so Claude has to validate instead of declaring done.
Shift specialized playbooks into on-demand skills so every session does not pay for instructions you rarely need.
Write the tests first, then set the goal to making them pass. Claude keeps working across turns until the condition is met instead of stopping after each reply.
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.
Put a single `@AGENTS.md` import in CLAUDE.md so Claude Code and other agent tools share the same project instructions without symlink confusion.
Save repeatable workflows as SKILL.md (or .claude/commands) so you slash-invoke consistent PR reviews, releases, or checklists.
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.
Use /init to generate a starter CLAUDE.md, then delete anything inaccurate or obvious before committing.
Cycle into plan mode (Shift+Tab) so Claude explores and proposes an approach for approval before editing.
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.
Declare a Compact Instructions section in CLAUDE.md so both manual /compact and autocompact preserve the project’s critical decisions by default.
Check in project settings so every teammate gets the same allow/deny rules, hooks, and env defaults without redoing /permissions.