Most helpful workflows, ranked by community
Schedule an early Claude Code run so your usage window resets around lunch instead of mid-afternoon.
Proactively run `/compact` with focus instructions so summaries keep the work that matters instead of stale debugging.
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.
Use `claude --worktree` (or git worktrees) so multiple agents edit isolated checkouts without colliding.
Trim project memory to under ~200 lines so Claude follows critical rules instead of drowning them in noise.
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.
Shift specialized playbooks into on-demand skills so every session does not pay for instructions you rarely need.
Save repeatable workflows as SKILL.md (or .claude/commands) so you slash-invoke consistent PR reviews, releases, or checklists.
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.
Check in project settings so every teammate gets the same allow/deny rules, hooks, and env defaults without redoing /permissions.
Add a deterministic PreToolUse hook that rejects destructive shell patterns before Claude can run them.
Create a skill that forces a red→green verification loop so Claude cannot claim done without running the suite.
Use /clear between unrelated tasks so leftover debugging does not bias the next feature.
Add a top-level cache_control ephemeral flag so growing conversation prefixes reuse cached tokens and cut API cost and latency.
Turn off MCP servers unrelated to the current project—their tool schemas still consume context at session start.
Build slash skills that accept issue numbers, branch names, or formats via $ARGUMENTS / $0 so one command covers many cases.
Run /context to break down token consumers—CLAUDE.md, MCP tools, conversation—and prune the expensive ones.
Add the GitHub MCP server so Claude can cross-reference issues, PRs, and repo state without leaving the session.
Define custom subagents with `isolation: worktree` so delegated edits happen on a temporary branch checkout.
Mark deploy/ship/destructive skills so only an explicit /command runs them—Claude cannot auto-trigger them mid-session.
Use /permissions to allowlist read-only and trusted commands so you stop mindlessly clicking Approve.