Cheat Sheet: Creating a Cheat Sheet

A cheat sheet is a concise summary of essential information, designed for quick reference and efficient learning. It prioritizes core concepts and actionable steps to maximize understanding with minimal content.

Core Principles

Specificity: Use concrete details like numbers, names, and dates from the source.
Actionability: Ensure every point can be acted upon immediately.
Depth: Surface non-obvious insights that surprise even knowledgeable readers.
Precision: One dense, precise sentence is better than three vague ones.
Voice: Use active voice and strong verbs.

Action Steps

Identify the single most important insight (bigIdea).
Extract the core principles that support the big idea.
List key actionable steps (actionSteps) in imperative mood with outcomes.
Surface proTips with embedded 'why' or 'because' explanations.
Name the specific cost of pitfalls (e.g., 'Skipping X causes Y, wasting Z').
Define keyTerms crisply, focusing on their application.
Debunk myths with surprising and specific realities.
Include statistics with context (source, year, relevance) and meaningful numbers.
Extract profound and memorable quotes.
Create a timeline showing causal connections.
Provide real-worldExamples with exact scenarios and applications.
Design decisionTree steps with clear decision points and divergent outcomes.
Formulate deep reflection questions that challenge assumptions.
List resources with descriptions of what they are best for.
Extract ALL relevant formulas in proper LaTeX syntax if applicable.
Generate diagrams (pie, bar, line) proactively whenever quantitative data, proportions, comparisons, or trends are present.

Key Terms

Specificity: Using concrete details like numbers, names, and dates directly from the source, avoiding vague generalities.
Actionability: Ensuring every tip, step, or principle is directly usable immediately by the reader.
Depth: Surfacing non-obvious insights that even knowledgeable individuals might miss.
Precision: Crafting one dense, precise sentence that conveys more value than multiple vague ones.
Voice: Employing active voice and strong verbs for direct and impactful communication.

Pro Tips

For bigIdea, aim for a quotable 1-2 sentence summary.
For corePrinciples, lead with the key concept (e.g., '80/20 Rule: ...').
For actionSteps, number them strictly.
For proTips, each tip MUST embed a 'why' or 'because'.
For pitfalls, be ruthlessly specific about the cost of the mistake.
For keyTerms, focus on HOW the term is used, not just WHAT it is.
For mythBuster, the myth must be widely believed, and the reality surprising and specific with evidence.
For statistics, make numbers meaningful, not just decorative.
For quotes, skip generic inspiration and focus on profound, memorable statements.
For timeline, show cause-and-effect where possible.
For realWorldExamples, use the EXACT scenario from the source.
For decisionTree, each step must be a real decision point with clearly divergent outcomes.
For reflection, ask deep, thought-provoking questions that challenge assumptions.
For resources, specify what each resource is best FOR (e.g., 'Best for beginners needing X').
For formulas, include ALL relevant formulas in proper LaTeX syntax.
For diagrams, be proactive: if statistics, metrics, percentages, or timelines are mentioned, generate at least 1 diagram with a specific title.

Pitfalls to Avoid

Vague generalities like 'it's important to...' or 'one should consider...' lack specificity and actionability.
Forgetting to include the 'why' or 'because' in proTips diminishes their value.
Being vague about the cost of a mistake in pitfalls reduces their impact.
Defining keyTerms without explaining their application makes them less useful.
Presenting myths without surprising or specific realities fails the mythBuster criteria.
Listing statistics without context or meaning makes them decorative rather than informative.
Including generic inspirational quotes instead of profound, illuminating ones misses the mark for the quotes module.
Creating timelines without causal connections or in strict chronological order fails the timeline module.
Using generic scenarios or applications in realWorldExamples reduces their immediate obviousness.
DecisionTree steps that aren't real decision points with divergent outcomes are not functional.
Reflection questions that are surface-level rather than challenging assumptions fail the reflection module.
Listing resources without specifying their use case makes them less helpful.
Omitting formulas or using incorrect LaTeX syntax will break the formulas module.
Generating generic diagram titles (e.g., 'Growth') instead of specific ones (e.g., 'Revenue Growth 2019-2024') fails the diagram module.