菜单
Use to intuitively, memorably explain abstract, complex, unfamiliar concepts. NOT for code generation, data retrieval, or when user just needs execution.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | memorable-explanations |
| description | Use to intuitively, memorably explain abstract, complex, unfamiliar concepts. NOT for code generation, data retrieval, or when user just needs execution. |
Your brain evolved for a physical, social world — not abstractions. Every good explanation translates back into that format. Here are 8 translators, in two groups of four:
Face, Place, Tale, Scale. → Structure (who, where, what happened, compared to what) Touch, Feel, Chunk, Beat. → Landing (tangible, emotional, holdable, sticky)
| Anchor | Mechanism | Watch out for |
|---|---|---|
| Face | Theory of mind + self-reference | Anthropomorphizing non-agents |
| Place | Spatial memory | Not all structures are spatial |
| Tale | Causal chain from sequence | False causation from mere order |
| Scale | Relative judgment | Anchoring bias from first number |
| Touch | Embodied cognition | Concreteness as permanent crutch |
| Feel | Amygdala tagging | Arousal narrows complex reasoning |
| Chunk | Working memory ~4 | Over-chunking hides connections |
| Beat | Rhythmic encoding | Stickiness ≠ understanding |
Without anchors: "DNS resolution translates domain names into IP addresses via hierarchical nameserver queries."
With anchors:
Imagine you type "google.com." [Face] Your computer doesn't know where Google lives — it only knows a local guide, the resolver. [Face: agent]
Think: asking for directions in an unfamiliar city. [Place + Touch] You ask a local, who asks the main information desk (root server), who says: ".com? Down that hall." The TLD server says: "Google? Here's their nameserver." Google's nameserver hands back 142.250.80.46 — the street address. [Tale: journey, Place: directions]
Total time: ~50ms — faster than a blink. [Scale] If it breaks, you get the most frustrating error on the internet. [Feel]
Four characters, one journey, one emotional beat. [Chunk + Beat]
To write in Anand's style for blog posts, emails, talk summaries, interview questions, conversations, ...
Run this by default as the final step after any non-trivial workflow — analysis, code, data work, a plan, a factual answer, a deliverable — before presenting it, even when not explicitly asked to verify. Skip it for trivial lookups, chitchat, and pure-tone tasks where there is nothing to be wrong about.
The user's question may be a DRAFT of their real need. For substantive requests, check if a better question changes what's solved and serves them better. If so, reframe, explain why (in 1 line), THEN answer. Most questions need no reframe; skip precise, mechanical, tightly specified, or already-sharp requests and simply answer.
Apply to any substantive answer for Anand - strategy, design, build, analysis, teaching, writing, research - to steer it toward his goals (compounding assets, durable skills, the surprising read). Skip for trivial lookups, mechanical edits, focused tasks. Shapes HOW to answer, never overrides WHAT was asked.
Automatically compress broad answers into the decision, recommendation, rationale, tradeoff, and next action. Use for recommendations, prioritization, research synthesis, strategy, planning, reviews, rankings, and large-context requests.
Brainstorm creative, novel, non-obvious ideas or options for an open-ended problem and narrow them to a recommendation. Not for writing prose, research, explanation, summaries, or questions with one right answer.
