Skip to content

Keyboard

Shortcuts

Everyone learns Esc. These are the rest — all checked against Claude Code itself, not copied off a blog.

The three to learn first

If you remember nothing else.

  • Esc Esc
    Stop Claude mid-action The moment Claude starts doing something you did not intend.
  • Esc thenEsc Esc thenEsc
    Clear the input box Your half-written prompt has turned into a mess and you want a clean line.
  • Shift +Tab Shift +Tab
    Cycle permission mode Starting an exploration (plan) or letting an agreed plan run (accept edits). On older Windows setups without VT mode, this is Meta+M instead.

Writing the prompt

Composing, searching, pasting.

  • Ctrl +J Ctrl +J
    Start a new line without sending Any prompt longer than one sentence.
  • Ctrl +R Ctrl +R
    Search your prompt history "What did I type last week that worked?" Inside the search, Ctrl+S cycles the scope: this session → this project → everywhere.
  • Ctrl +S Ctrl +S
    Park the half-written prompt You are three sentences into a prompt and need to go check something.
  • Ctrl +G Ctrl +G
    Edit the prompt in your real editor Writing anything long or carefully structured.
  • Ctrl +V Alt +V
    Paste an image Anything visual. Annotate the screenshot first and it works even better. Ctrl+V, not Cmd+V — macOS keeps Cmd+V for its own paste. Windows and WSL use Alt+V. On WSL both Ctrl+V and Alt+V work.
  • Option +T Alt +T
    Toggle thinking for the next turn One hard question in the middle of otherwise simple work.
  • Ctrl +_ Ctrl +_
    Undo in the input box You deleted half a prompt by accident.

Seeing what happened

What Claude did and what it plans to do.

  • Ctrl +O Ctrl +O
    Toggle the full transcript You want to know what it actually did, not the summary.
  • Ctrl +T Ctrl +T
    Toggle the task checklist Any multi-step task, before it gets far.

Running the session

Long jobs, models, the terminal.

  • Ctrl +B Ctrl +B
    Send the running job to the background A long build, test run, or search you do not want to sit and watch.
  • Option +P Alt +P
    Switch model Between tasks — rarely a good idea mid-task.
  • Option +O Alt +O
    Toggle fast mode Straightforward work where you would rather have speed than depth.
  • Ctrl +Z Ctrl +Z
    Step out to the shell without quitting You need the terminal for one command and do not want to lose the session. Terminal-level shortcut (Unix SIGTSTP), not a Claude Code binding. Windows has no direct equivalent.

The keys are the same on both systems — only the modifier's name changes (macOS calls Alt Option). Run /keybindings in any session to see exactly what is bound on your machine.

gsd-* — Get Shit Done framework family

← Skills From the community

Slash command /gsd-*

Get Shit Done framework family

A light-weight meta-, context-engineering and spec-driven development system for . A family of commands (`:new-`, `gsd:plan-phase`, `gsd:execute-phase`, `gsd:progress`, etc.) for managing multi-week projects with persistent `.planning/` state and per-phase artefacts.

advanced ⏱ ~half a day per phase on multi-week projects View source ↗

The gsd-* family is the heaviest workflow option in the team’s toolbox — for that genuinely span weeks or months, not one sitting.

What you get: a persistent .planning/ folder with roadmap, milestones, per-phase artefacts (discuss / spec / plan / execute / verify / secure), and an audit trail. Pick it up next week and Claude remembers exactly where you left off.

When it’s right:

  • Long horizon (weeks/months)
  • Multiple collaborators
  • Traceability matters
  • You’ll pause and resume

When it’s overkill: one-off scripts, single-sitting prototypes — use plain or /team instead.

Common entry points: /gsd:new-project, /gsd:plan-phase, /gsd:execute-phase, /gsd:progress, /gsd:help. See /hub-glossary gsd for the broader framework explanation.

Access

Public — no access request needed. The canonical upstream is gsd-build/get-shit-done by TÂCHES.

Next skill →

/handoff — end a session so the next one starts sharp

Compresses the live conversation into a handoff document a fresh can act on — written for the next , not as a summary for you. Plain , saved to a temp directory, and it names which the next session should reach for.

Open it → Back to all skills