Cheat sheets
Status: π© COMPLETE Last updated: 2026-06-21 Plain-English tagline: Quick reference cards for the CLI tools you use every day. The textbook entries explain why; the cheat sheets give you what to type.
What these are
A cheat sheet is the commands grouped by what youβre trying to do, with a one-liner each. No long prose. No deep theory. The mental model already lives in the corresponding textbook entry; this is the daily-use surface.
Reach for a cheat sheet when:
- You know what you want to do but forgot the exact command
- You want a one-screen reference open while you work
- Youβre teaching someone else and want a printable handout
Reach for the textbook entry when:
- You want to understand why a thing works the way it does
- You hit a gotcha that needs context
- Youβre learning the tool for the first time
The sheets
| Tool | Cheat sheet | Textbook entry |
|---|---|---|
| Git | Git cheat sheet π© | Git basics π© |
| npm | npm cheat sheet π© | npm & package managers π© |
| Vercel CLI | Vercel CLI cheat sheet π© π¦ | Vercel π© π¦ |
| gh CLI (GitHub) | gh CLI cheat sheet π© π¦ | GitHub π© π¦ |
| Supabase CLI | Supabase CLI cheat sheet π© π¦ | Supabase π© π¦ |
| PowerShell | PowerShell cheat sheet π© | PowerShell vs Bash π© |
| AI vendor reference | AI vendor cheat sheet π© π¦ | AI landscape π© π¦ |
| AI prompting | AI prompting cheat sheet π© π¦ | Prompt engineering π© |
| AI APIs (developer) | AI API cheat sheet π© π¦ | AI vendor entries π© π¦ |
| AI safety | AI safety cheat sheet π© π¦ | AI safety primer π© π¦ |
| AI for daily life | AI for daily life cheat sheet π© π¦ | AI vendor entries π© π¦ |
| AI prompts library | AI prompts library π© π¦ | Prompting cheat sheet π© π¦ |
| AI ethics | AI ethics cheat sheet π© π¦ | AI safety primer π© π¦ |
How to use these
Skim, then keep one open. A cheat sheet is most useful as a side panel while you work, not something you read end-to-end. Bookmark the one for the tool you use most.
Pair with the textbook. If a command surprises you (βwait, why does it do that?β), click through to the textbook entry. The cheat sheet gives you the trigger; the textbook gives you the reason.
Trust the gotchas. Each sheet has a short gotchas section near the end. These are the genuinely surprising things β read them once, save yourself time later.
Whatβs NOT here
The cheat sheets cover command-line tools. Thereβs no cheat sheet for:
- React / Next.js / Tailwind syntax β these arenβt really cheat-sheet-shaped (theyβre whole programming languages, not lookup tables). The textbook entries cover them properly.
- SQL syntax β covered in SQL the language π©.
- Claude Code slash commands β your installed plugins decide whatβs available; check
/helpin a live session.
See also
- Reading path: I want to build my first webapp π© β where these tools come together
- Reading path: Master Claude Code π© β Claude Codeβs own quick references
- How-to library β step-by-step procedures (different format, often referenced from these sheets)