AI-Accelerated Learning

• Asking an LLM for "the 5 core mental models experts share" extracts structural knowledge rather than surface summaries -- it targets the frameworks that take years of domain experience to internalize (from notebooklm accelerated learning)
• The three-prompt learning sequence -- (1) core mental models, (2) fundamental expert disagreements, (3) deep-understanding test questions -- maps an entire field's intellectual landscape in minutes (from notebooklm accelerated learning)
• Uploading massive context (6 textbooks, 15 papers, all lecture transcripts) before querying gives the model enough material to identify cross-source patterns rather than echoing a single author's perspective (from notebooklm accelerated learning)
• Using AI-generated "deep understanding vs. memorization" questions as a self-test forces active recall against the hardest conceptual gaps (from notebooklm accelerated learning)
• The error-driven follow-up loop -- "explain why this is wrong and what I'm missing" after each wrong answer -- turns mistakes into targeted micro-lessons, compressing the feedback cycle from weeks to minutes (from notebooklm accelerated learning)
• Training AI skills on curated reference assets (e.g., from a copywriting resource site) dramatically improves output quality versus generic prompting -- the pattern is encoding domain knowledge into reusable AI configurations rather than relying on zero-shot generation (from ai copywriting skill training)
• A compounding learning loop forms when AI query answers are saved back into the raw/ knowledge folder, so each subsequent answer is better informed than the last -- the knowledge base improves itself through use (from claude personal knowledge base workflow)
• 45 minutes of weekend setup (folder structure + CLAUDE.md schema) becomes a continuously improving company asset through consistent usage and feeding results back -- low upfront cost, compounding return (from claude personal knowledge base workflow)
• Monthly knowledge-base health checks -- asking the AI to flag contradictions, surface unexplored topics, and suggest articles to fill gaps -- turn a static archive into a self-auditing learning system (from claude personal knowledge base workflow)
• claude-smart makes agent learning explicit: it converts session mistakes into reusable, actionable rules across projects, such as learning to avoid a repo's hanging test watch mode, rather than merely remembering that the mistake happened (from claude smart self improving plugin)
• Running an AI prep prompt before 1:1s converts "flying blind" into structured conversations: a 5-minute routine replaces agenda-glancing, surfaces what might be missed, and creates more intentional dialogue (from ai prep one on one meetings)
• OpenAI's Forward Deployed Engineer interview deliberately avoids LeetCode-style problems and tests practicing "the actual loop" of real-world implementation -- signaling that learning the applied workflow now matters more than rehearsing algorithmic puzzles (from openai forward deployed engineer interview process)

LLM Input Optimization

• LLMs natively speak Markdown (trained on vast amounts of it) -- converting files to Markdown before feeding to LLMs gets better extraction, reasoning, and token efficiency than raw text or HTML (from markitdown microsoft file converter)

• Karpathy-style git wikis for knowledge bases can grow to multi-gigabyte sizes (2.3GB+), at which point git's 5GB limit forces a migration to SQLite — plan for database backends early in long-running knowledge projects (from garry tan openclaw git wiki gstack)

• NotebookLM podcast generation combined with a .md analysis file creates a dual-format learning artifact: audio for passive consumption and structured markdown for cross-LLM integration and further querying (from notebook lm podcast markdown analysis)

Prompting Techniques

• "Socratic prompting" -- asking AI questions instead of giving it directives -- is claimed to significantly improve output quality by forcing the model to reason through the problem rather than pattern-match to a response (from socratic prompting technique)
• The technique inverts the typical prompt paradigm: instead of instructing the model, you guide it through questions that may activate deeper reasoning chains (from socratic prompting technique)
• Prompt engineering for domain expertise continues to gain traction -- users want specific, structured prompts tailored to professional workflows (market research, consulting, competitive intel) rather than generic AI interactions (from claude market research prompts)

Research and Analysis

• Claude is being positioned as a market research tool competitive with consulting-grade analysis, with users reverse-engineering prompt strategies from McKinsey and investment bank workflows (from claude market research prompts)
• AI-generated consulting-grade deliverables (McKinsey/BCG-style slides with complex data visualizations) are becoming accessible to individuals, with Kimi generating professional presentations directly from detailed prompts (from kimi mckinsey slide prompt)
• The prompt engineering pattern for high-quality slide generation requires specifying three layers: content structure (frameworks, data types), visual style (typography, color palette), and layout density (from kimi mckinsey slide prompt)

Open-Source Learning

• "GitHub is the new Harvard" frames open-source repos as the primary educational institution for AI practitioners -- credentials matter less than demonstrated learning from public codebases (from most starred ai repos)
• High-star AI repos on GitHub represent a curated, community-validated curriculum -- the engagement signal (stars) acts as a quality filter that traditional education lacks (from most starred ai repos)

Why Coding/Math/Research Outpace General-Use

• Karpathy: the dramatic AI improvements in coding, math, and research come from two properties — these domains offer verifiable rewards (unit tests passed yes/no) for RL, and they concentrate B2B value that justifies prioritization; the goldmines drive the focus (from ai capability gap coding vs general use)

• The free-tier impression of AI is structurally misleading: free/old/deprecated chat models don't reflect $200/month frontier agentic capability — Codex sessions running 1+ hours can restructure entire codebases or find system vulnerabilities (from ai capability gap coding vs general use)

Visual Training Data for Agents

• Refero's 2,000 DESIGN.md files (colors, typography, spacing, layout patterns from top products) directly address why AI agents make ugly UIs: they've never seen good design — exposure-as-training, packaged for in-context learning rather than fine-tuning (from refero design systems ai agents)