30 Claude Prompts That Build Cheat Sheets

You are a senior engineer who writes calm, practical Git references. <context> I need a Git cheat sheet as a self-contained Markdown document, grouped by workflow, that covers everyday commands and the recovery moves people panic over. </context> <inputs> - Workflow: [SOLO / FEATURE BRANCHES / GITFLOW] - Level: [BASIC / INTERMEDIATE] - Pain points: [E.G. REBASE, MERGE CONFLICTS, UNDOING COMMITS] - Host: [GITHUB / GITLAB / OTHER] </inputs> <task> Build the cheat sheet with tables grouped by: setup and config, staging and committing, branching and switching, merging vs rebasing, pushing and pulling, inspecting history (log, diff, blame), stashing, tagging, and an "undo / oh no" table (amend, reset soft vs hard, revert, restore, recover with reflog). Each row = command, what it does, and a one-line caution where it is destructive. </task> <constraints> - Commands must be correct and current; clearly mark anything that rewrites history. - The undo table is the priority — make it complete and safe. - Dense tables, one command per row, no long tutorials. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line rule for when to rebase versus merge. </format>

You are a DevOps engineer who documents container workflows for developers. <context> I need a Docker cheat sheet as a self-contained Markdown document, grouped by task, covering the daily commands plus cleanup and debugging. </context> <inputs> - Use case: [LOCAL DEV / CI / PRODUCTION] - Compose: [YES / NO] - Level: [BASIC / INTERMEDIATE] - Common tasks: [BUILDING, RUNNING, LOGS, VOLUMES, NETWORKS] </inputs> <task> Build the cheat sheet with tables grouped by: images (build, tag, pull, push, list, remove), containers (run with common flags, exec, stop, rm, logs, inspect), volumes and mounts, networks, an essential Dockerfile instruction reference, docker compose commands if requested, and a cleanup table (prune images, containers, volumes, system). Each row = command with common flags, what it does, and a note. </task> <constraints> - Commands must be current Docker CLI syntax; explain each common flag inline. - Include a safe cleanup section — people fill their disks. - Dense tables, one command per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line warning on which prune commands delete data. </format>

You are a Linux sysadmin who writes practical command references. <context> I need a Linux command-line cheat sheet as a self-contained Markdown document, grouped by task, for everyday shell work. </context> <inputs> - Distro / shell: [E.G. UBUNTU / BASH] - Role: [DEVELOPER / SYSADMIN / DATA] - Level: [BASIC / INTERMEDIATE] - Focus: [FILES, PERMISSIONS, PROCESSES, NETWORKING, TEXT PROCESSING] </inputs> <task> Build the cheat sheet with tables grouped by: navigation and files (ls, cd, cp, mv, rm, find), viewing and searching (cat, less, grep, head/tail), permissions and ownership (chmod, chown, with a permission-bits mini-table), processes (ps, top, kill, jobs), disk and system (df, du, free), networking (curl, ssh, scp, netstat/ss), archives, and text processing (sed, awk, sort, cut, pipes). Each row = command with common flags, what it does, and a tiny example. </task> <constraints> - Commands correct for the stated distro/shell; explain flags inline. - Include a chmod numeric reference table. - Dense tables, one command per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then note the five commands worth memorizing first. </format>

You are a Kubernetes engineer who documents kubectl for teams shipping to clusters. <context> I need a kubectl cheat sheet as a self-contained Markdown document, grouped by task, covering inspection, debugging, and everyday operations. </context> <inputs> - Cluster context: [MANAGED (EKS/GKE/AKS) / SELF-HOSTED / LOCAL] - Level: [BASIC / INTERMEDIATE] - Focus: [DEPLOYMENTS, DEBUGGING PODS, CONFIG, SCALING] - Namespace usage: [SINGLE / MANY] </inputs> <task> Build the cheat sheet with tables grouped by: cluster and context (get contexts, use-context, config), viewing resources (get/describe pods, deployments, services with -o wide and -n), logs and exec (logs, logs -f, exec -it), applying and deleting manifests (apply, delete, diff), debugging (events, describe, port-forward, top), scaling and rollouts (scale, rollout status/undo), and label/selector filtering. Each row = command with common flags, what it does, note. </task> <constraints> - Commands must be current kubectl syntax; show namespace and output flags. - Prioritize the debugging section — that is where on-call time goes. - Dense tables, one command per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line tip for setting up a kubectl alias and namespace shortcut. </format>

You are a JavaScript tooling expert who documents package managers clearly. <context> I need a package-manager cheat sheet as a self-contained Markdown document, grouped by task, so I never mix up install, scripts, and version commands. </context> <inputs> - Manager: [NPM / YARN / PNPM / BUN] - Project: [APP / LIBRARY / MONOREPO] - Level: [BASIC / INTERMEDIATE] - Include a comparison to other managers: [YES / NO] </inputs> <task> Build the cheat sheet with tables grouped by: project setup (init, install all), adding and removing dependencies (regular, dev, global, exact version), running scripts, updating and auditing, versioning and publishing, workspaces/monorepo commands, and cache and lockfile management. Each row = command, what it does, and a note. If requested, add a side-by-side table mapping the same action across npm, yarn, pnpm, and bun. </task> <constraints> - Commands correct for the stated manager; flag anything manager-specific. - The npm-vs-yarn-vs-pnpm-vs-bun mapping table must be accurate if included. - Dense tables, one command per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line note on which command differs most between managers. </format>

You are a React specialist who documents hooks with correct, idiomatic patterns. <context> I need a React hooks cheat sheet as a self-contained Markdown document, one hook per section, with the signature, a minimal example, and the common mistake to avoid. </context> <inputs> - React version: [E.G. 19] - Level: [INTERMEDIATE / ADVANCED] - Focus: [STATE, EFFECTS, PERFORMANCE, CUSTOM HOOKS] - TypeScript: [YES / NO] </inputs> <task> Build the cheat sheet with tables for: useState, useEffect (with the dependency-array rules and cleanup), useRef, useMemo vs useCallback (when each helps), useContext, useReducer, and useState updater patterns; plus a section on writing a custom hook and the rules of hooks. Each row = hook, signature, a minimal example, and the most common mistake. </task> <constraints> - All examples valid for the stated React version; use TS types if requested. - Be explicit about effect dependencies and cleanup — that is where bugs live. - Dense tables, one hook per row, no long essays. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a short decision guide for useMemo vs useCallback vs neither. </format>

You are a front-end developer who documents Tailwind utility classes for fast lookup. <context> I need a Tailwind CSS cheat sheet as a self-contained Markdown document, grouped by property, mapping the utility class to the CSS it produces. </context> <inputs> - Tailwind version: [E.G. 4] - Focus: [LAYOUT, FLEXBOX/GRID, SPACING, TYPOGRAPHY, COLORS, RESPONSIVE] - Level: [BASIC / INTERMEDIATE] - Custom config notes: [OPTIONAL] </inputs> <task> Build the cheat sheet with tables grouped by: layout and display, flexbox and grid, spacing (padding, margin, gap scale), sizing, typography, colors and backgrounds, borders and radius, effects (shadow, opacity), and the responsive and state prefixes (sm/md/lg, hover, focus, dark). Each row = the utility class, the CSS it outputs, and a note. Include the default spacing scale reference. </task> <constraints> - Classes must be valid for the stated Tailwind version; show the exact CSS output. - Include the responsive breakpoint values and the spacing-scale-to-pixels mapping. - Dense tables, one class or group per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then note the classes I will reach for most in everyday layout. </format>

You are a data scientist who documents pandas for daily analysis work. <context> I need a pandas cheat sheet as a self-contained Markdown document, grouped by task, with a tiny code snippet for each operation. </context> <inputs> - Pandas version: [E.G. 2.x] - Work: [DATA CLEANING / ANALYSIS / TIME SERIES] - Level: [BASIC / INTERMEDIATE] - Data shape: [OPTIONAL DESCRIPTION] </inputs> <task> Build the cheat sheet with tables grouped by: creating and reading data (read_csv, DataFrame), inspecting (head, info, describe, dtypes), selecting and filtering (loc, iloc, boolean masks, query), cleaning (dropna, fillna, astype, rename), transforming (apply, map, assign), grouping and aggregation (groupby, agg, pivot_table), merging and concatenating, sorting, and exporting. Each row = task, a minimal snippet, and a note. </task> <constraints> - Snippets valid for the stated pandas version; prefer loc/iloc over chained indexing. - Flag anything that returns a copy vs a view where it matters. - Dense tables, one operation per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line note on the SettingWithCopyWarning and how to avoid it. </format>

You are a Next.js engineer who documents the App Router for teams building production apps. <context> I need a Next.js App Router cheat sheet as a self-contained Markdown document, grouped by concept, covering the file conventions and data patterns. </context> <inputs> - Next.js version: [E.G. 15] - Rendering focus: [SERVER COMPONENTS / STREAMING / CACHING] - Level: [INTERMEDIATE] - Using: [ROUTE HANDLERS / SERVER ACTIONS / BOTH] </inputs> <task> Build the cheat sheet with tables for: the special files and what each does (page, layout, loading, error, not-found, route, template), server vs client components and when to use "use client", data fetching and the caching/revalidation options, dynamic routes and params, route handlers (API), server actions, metadata, and navigation (Link, useRouter, redirect). Each row = the file or API, what it does, a minimal example, and a note. </task> <constraints> - Everything valid for the stated Next.js version; be explicit about server vs client boundaries. - Clarify the caching defaults and how to opt out — that is the biggest source of confusion. - Dense tables, one concept per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a short decision guide for server component vs client component. </format>

You are a Django developer who documents the ORM with correct query patterns. <context> I need a Django ORM cheat sheet as a self-contained Markdown document, grouped by task, with a query snippet for each common operation. </context> <inputs> - Django version: [E.G. 5.x] - Focus: [QUERIES / RELATIONSHIPS / AGGREGATION / PERFORMANCE] - Level: [BASIC / INTERMEDIATE] - Example models: [OPTIONAL] </inputs> <task> Build the cheat sheet with tables grouped by: creating and saving objects, querying (filter, exclude, get, all, order_by), field lookups (__gte, __icontains, __in, __isnull), spanning relationships, aggregation and annotation (Count, Sum, Avg, F and Q objects), select_related vs prefetch_related for the N+1 problem, updating and deleting in bulk, and raw/values queries. Each row = task, a snippet, and a note. </task> <constraints> - Snippets valid for the stated Django version and idiomatic. - Make the select_related vs prefetch_related distinction explicit — it is the main performance trap. - Dense tables, one operation per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line note on spotting and fixing an N+1 query. </format>

You are a study coach who condenses course material into exam-ready one-pagers. <context> I need a one-page exam cram sheet as a self-contained Markdown document that fits my whole topic on a single dense page for last-minute review. </context> <inputs> - Subject and exam: [E.G. INTRO ECONOMICS FINAL] - Topics to cover: [LIST OR PASTE OUTLINE] - What the exam tests most: [OPTIONAL] - Format allowed: [OPEN-NOTE / MEMORIZATION AID] </inputs> <task> Condense the material into one page using compact tables and tight bullet clusters: key definitions, core formulas or rules, the 8-10 most testable facts, common mistakes, and a "if you see X, do Y" quick-decision table. Prioritize ruthlessly — only what is likely to be tested. Group by topic so it maps to how the exam is structured. </task> <constraints> - Must genuinely fit on one page — cut anything low-yield. - Facts must be accurate; no vague summaries, only concrete, testable content. - Dense tables and clusters, minimal prose. </constraints> <format> Return the full cram sheet as a Markdown artifact, then a one-line note on what to cut first if it still runs long. </format>

You are a certification instructor who builds focused review sheets for pro exams. <context> I need a certification-exam cheat sheet as a self-contained Markdown document, organized by exam domain, covering the concepts and gotchas that show up on the test. </context> <inputs> - Certification: [E.G. AWS SOLUTIONS ARCHITECT ASSOCIATE, PMP, CompTIA A+] - Exam domains and weights: [LIST OR PASTE BLUEPRINT] - My weak areas: [OPTIONAL] - Exam date: [OPTIONAL] </inputs> <task> Build the cheat sheet with a table per exam domain: the key services or concepts, when to use each, the most common trap or distractor the exam uses, and any numbers or limits worth memorizing. Add a "decision triggers" table (if the question mentions X, the answer is usually Y) and a short glossary of terms the exam assumes. </task> <constraints> - Map sections to the official exam domains and their weights. - Focus on exam-relevant distinctions and traps, not encyclopedic detail. - Dense tables, one concept per row; flag your weak areas prominently. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line study order based on domain weights and my weak areas. </format>

You are a tutor who builds structured revision sheets that aid recall. <context> I need a subject revision cheat sheet as a self-contained Markdown document that turns a full topic into a compact, recall-friendly reference for review sessions. </context> <inputs> - Subject and topic: [E.G. BIOLOGY: CELL RESPIRATION] - Level: [SCHOOL / UNIVERSITY] - Sub-topics: [LIST] - Include recall questions: [YES / NO] </inputs> <task> Build the cheat sheet with: a key-terms table (term, definition, one example), a core-concepts table (concept, what it means, why it matters), a process or timeline where relevant, a common-confusions table (X vs Y and how to tell them apart), and — if requested — a short set of active-recall questions with answers at the end. Group by sub-topic. </task> <constraints> - Content must be accurate and at the stated level; no oversimplification that misleads. - Structure for recall: comparisons and "X vs Y" tables, not walls of text. - Dense tables, one item per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line note on how to use it for spaced repetition. </format>

You are a language teacher who builds compact grammar and vocabulary reference sheets. <context> I need a language-learning cheat sheet as a self-contained Markdown document that puts the core grammar and high-frequency vocab of a level on one scannable page. </context> <inputs> - Target language: [E.G. SPANISH] - My level: [A1 / A2 / B1 / B2] - Focus: [E.G. PRESENT TENSE, TRAVEL VOCAB, COMMON PHRASES] - Native language: [FOR TRANSLATIONS] </inputs> <task> Build the cheat sheet with tables for: essential grammar (verb conjugation patterns, articles, pronouns, sentence order) with example sentences and translations, high-frequency vocabulary grouped by theme, common phrases and connectors, and a pitfalls table (false friends, gender, tricky prepositions). Each row = the target-language item, its meaning in my native language, and a short usage example. </task> <constraints> - Content must be correct and level-appropriate; include accents and gender markers. - Every vocab and grammar row shows a real example sentence with translation. - Dense tables, one item per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line note on which 20 words to memorize first. </format>

You are an interview coach who builds one-page prep sheets candidates review before a call. <context> I need an interview prep cheat sheet as a self-contained Markdown document that puts my stories, talking points, and likely questions on one scannable page. </context> <inputs> - Role and company: [TITLE AND COMPANY] - Interview type: [BEHAVIORAL / TECHNICAL / MIXED] - My key experiences: [2-4 PROJECTS OR WINS] - Known focus areas: [FROM THE JOB DESCRIPTION] </inputs> <task> Build the cheat sheet with: a table of likely questions and a one-line angle for each, a STAR-stories table (situation, task, action, result) for my key experiences, a "my strengths mapped to their needs" table, smart questions to ask them, and a quick-facts row on the company and role. Keep each cell to phrases and bullet fragments, not paragraphs, so I can glance during the call. </task> <constraints> - Base talking points on the experiences and focus areas I gave; do not invent achievements. - Fragments and phrases only — this is a glance-at reference, not a script. - Dense tables, one item per row. </constraints> <format> Return the full cheat sheet as a Markdown artifact, then a one-line note on the single story to lead with. </format>