Map
Claude Code for the Rest of Us
The Ultimate Playbook for Non-Coding Tasks and Workflows
by Krishna Veera Vanamali Y
Map Starter Kit
ESC
Start typing to search across all chapters
3 min read

Appendix F: Cheat Sheet

Getting Started

In your terminal:

# Mac / Linux / WSL (recommended — auto-updates in background):
curl -fsSL https://claude.ai/install.sh | bash

# Or with Homebrew (no auto-updates):
brew install --cask claude-code

# Windows PowerShell:
irm https://claude.ai/install.ps1 | iex

cd ~/Desktop/Your-Project                      # Navigate to project folder
claude                                         # Launch Claude Code

Essential Commands

Command What It Does
claude Start Claude Code
/compact Compress conversation to free up context
/commit-commands:commit Save your work to git (commit-commands plugin)
/commit-commands:commit-push-pr Commit, push, and open a pull request
Shift+Tab Cycle permission modes (Default → Accept Edits → Plan, plus Bypass / Auto if enabled; dontAsk is flag-only via --permission-mode dontAsk)
/init Create a starter CLAUDE.md for your project
/claude-md-management:revise-claude-md Update CLAUDE.md with session learnings
Ctrl+V (Mac) / Alt+V (Windows) Paste a screenshot from clipboard into the conversation
Ctrl+S (Mac) Stash your in-progress prompt (save without sending)
Esc Pause Claude mid-task
Ctrl+C Cancel current operation
/rewind (or Esc Esc) Open the rewind menu — restore your files, the conversation, or both to an earlier checkpoint
/loop [interval] [prompt] Schedule a recurring prompt (e.g., /loop 5m check the build)
/remote-control or /rc Continue this session from your phone or another browser
/insights Generate an HTML report analyzing your usage patterns from the last 30 days
/usage Break down what is driving your plan limits — by skill, subagent, plugin, and MCP server
/statusline [description] Configure the persistent status bar (e.g., /statusline show model and context %)
/plugin Open the plugin manager (Discover / Installed / Marketplaces / Errors tabs)
/plugin install [name]@[marketplace] Install a plugin (e.g., /plugin install frontend-design@claude-plugins-official)
/reload-plugins Activate newly installed plugins or skills without restarting the session
! [command] Run a terminal command inside Claude Code — Claude sees the output and responds to it
/cd [folder] Move the session to a different folder without restarting (loads that folder’s CLAUDE.md)
/copy Copy Claude’s last response to your clipboard
/export Save the whole conversation as a text file
/subtask [task] Send a sub-agent off with your context; the result comes back into your session
/config Open the tabbed settings interface (change model, toggle thinking, etc.)
/help Show available commands

The Five-Second Workflow Checklist

  1. Am I in the right folder? (pwd)
  2. Is my CLAUDE.md up to date?
  3. Have I provided file paths, not vague references?
  4. For complex tasks: should I use plan mode first?
  5. Am I giving a task instruction, not starting a conversation?

Quick Prompt Patterns

Download video: “Download this YouTube video in highest quality: [URL]”

Analyze data: “Read [FILE PATH] and [specific analysis]. Create a chart showing [what]. Save as PNG at 300 DPI.”

Write content: “Read [SOURCE FILE]. Write a LinkedIn post about [topic] with 3 hook options. Save as RTF.”

Build website: “Build a [type] website with [pages]. Use the frontend-design skill. [Design direction].”

Process document: “Read [FILE PATH]. [Extract/summarize/convert]. Save to [OUTPUT PATH].”

Research: “Research [topic]. Search the web for [specific questions]. Save findings to [FOLDER].”

The Power User’s Daily Habits

  1. Start every project in its own folder
  2. Launch Claude Code from the project folder
  3. Keep CLAUDE.md updated after every significant session
  4. Use plan mode before complex tasks
  5. Give file paths, not descriptions
  6. Chain tasks into workflows
  7. Save outputs as RTF for content, PNG at 300 DPI for charts
  8. /commit-commands:commit after every meaningful change
  9. Use /compact during long sessions
  10. End sessions by updating CLAUDE.md

This playbook is based on thousands of real sessions across hundreds of projects over nearly a year of intensive daily use. Every workflow, every prompt pattern, and every recommendation comes from actual practice. The tools evolve quickly — when in doubt, ask Claude Code itself how to do something. That is, after all, the whole point.

The Non-Technical Power User’s Playbook for Claude Code By Krishna Veera Vanamali First Edition, 2026

← Appendix E: Glossary