trvux
- 6 skills
- 0 followers
- 7 hours ago last updated
- ▌ Feynman Eli5 · trvux bundleExplain a concept, theorem, or piece of code using the Feynman Technique — a layered explanation that starts with a plain-language everyday analogy (no jargon), then adds technical precision in successive layers, ends with the real motivating "why does this matter" reasoning, and closes with a self-test question the user must answer in their own words. Use whenever the user asks to explain something "like I'm 5", "ELI5", "Feynman style", "simply", "in plain English", or wants to build intuition for a concept rather than just read a definition. Trigger this proactively whenever a concept is genuinely hard to build intuition for (recursion, gradient descent, dependency injection, statistical concepts, etc.) even if the user just asks "explain X" without naming the technique.
- ▌ Cornell Notes · trvux bundlePresent an explanation as Cornell-style study notes -- a cue-question column paired with a notes/evidence column, followed by a fill-in-yourself summary prompt and self-test recall questions. Use whenever the user asks for "Cornell notes", "study notes", "notes format", or wants material formatted for spaced-repetition style review and active recall rather than a linear explanation. Especially good for exam prep, onboarding docs, or any material the user will need to review more than once.
- ▌ Worked Example · trvux bundleTeach a concept by walking through one realistic, continuous scenario from a naive first attempt through the wrong turns, the moment the real problem is discovered, the fix, and a payoff that proves the fix was worth it -- ending with a generalized heuristic. Use whenever the user asks for a "worked example", "case study", "walk me through it", "show me step by step with a real example", or is trying to understand WHY a pattern/technique exists rather than just what it is. Especially good for design patterns, refactoring techniques, debugging methodology, and any "best practice" that sounds arbitrary until you've hit the problem it solves yourself.
- ▌ Ieee Paper Format · trvux bundleWrite any explanation, tutorial, or answer as a formal academic paper in IEEE conference format (Abstract, Index Terms, numbered Roman-numeral sections, figures/tables, references). Use whenever the user asks for "academic paper style", "IEEE format", "two column format", "research paper style", or wants a topic explained the way a conference paper would present it. Also trigger when the user says things like "make this into a paper" or "give me the academic version" of an explanation. Defaults to a Markdown deliverable (no toolchain required); produces a compiled two-column PDF only when the user explicitly asks for "PDF" or "compiled".
- ▌ Socratic Dialogue · trvux bundleExplain a concept as a Socratic dialogue between a curious learner (Q) and an expert (A), where the learner keeps pushing with "but why" until the expert's underlying tacit reasoning surfaces -- rather than presenting the conclusion directly. Use whenever the user asks for "Socratic method", "Q&A style", "dialogue format", or wants to see the reasoning process behind a conclusion rather than just the conclusion itself. Especially effective for surfacing the tacit, hard-to-articulate judgment that experts use but rarely write down explicitly.
- ▌ Zettelkasten Notes · trvux bundleBreak an explanation into small, independently-readable, cross-linked notes (a Zettelkasten-style knowledge graph) instead of one linear document -- each note has an ID, a single focused idea, and explicit links to related notes, plus a link map showing the overall network. Use whenever the user asks for "zettelkasten", "linked notes", "note graph", "progressive disclosure", or wants a non-linear reference they can browse by following connections rather than reading top to bottom. Also offer this format when explaining a topic with many interrelated sub-concepts where a single linear document would force an arbitrary reading order.