Edit skill

Name *

Slug (leave blank to keep current)

Description *

Category

Author

Tags (comma-separated)

Content *(Markdown)

---
name: elie
description: Explain Like I'm Eivind (/elie). Explain any concept, from any domain, entirely through stock market, trading, and investing analogies. Use this skill whenever the user types /elie, says "explain like I'm Eivind", "ELI Eivind", or otherwise asks for an explanation in Eivind's terms, market terms, or trading terms. Eivind is a 30-something investor who understands the world ONLY through markets — so every explanation must be built from finance concepts. Trigger this even when the user doesn't name the skill explicitly but clearly wants something explained "in stock market terms" or "as if to someone who only understands investing."
---

# Explain Like I'm Eivind (/elie)

## Who Eivind is

Eivind is a 30-something investor. His entire mental model of reality is the market. Order books, positions, dividends, volatility, leverage, portfolio theory — this is the primary vocabulary his brain has referents for. He does not have a working intuition for cooking, biology, plumbing, history, or software *as such*. If you explain something to him in ordinary terms, it does not land. If you explain it as a trade, a position, an asset, or a market mechanism, he understands it instantly and deeply.

Beyond markets, Eivind has a few domains of genuine lived experience he can also reason within: he played **tuba and baritone in a janitsjarkorps** (a Norwegian wind/marching band), so brass technique, embouchure, breath support, ensemble timing, marching formations, and the korps hierarchy are real to him; and he was a **competitive swimmer** whose favorite stroke was **butterfly**, so stroke mechanics, breathing rhythm, drag, streamlining, splits, and race pacing are intuitive to him too. These are secondary — reach for them only when no market analogy works (see the fallback rule).

This is the core design principle of this skill: **the market analogy is not a garnish on top of a "real" explanation — it IS the explanation.** Do not write a plain-language version and then dress it up. Do not append "and in actual terms, this means..." Eivind has no use for the actual terms; he'd stare at them blankly. The analogy must carry 100% of the conceptual load on its own.

## The one hard rule

Explain the concept **entirely** in terms of the stock market, trading, and investing. Every moving part of the thing being explained must map onto a market equivalent — an asset, a position, an order type, a market participant, a mechanism, a risk, a strategy.

Stock market analogies are strongly preferred and should be your default in essentially all cases. Markets are vast: equities, bonds, options, futures, forex, crypto, commodities, ETFs, market microstructure, macro, portfolio construction, risk management — there is almost always a faithful mapping if you think hard enough. Reach for it.

**Fallback (rare):** *Only* if a concept genuinely cannot be mapped to any market phenomenon should you fall back to **Android front-end development** analogies (Activities, Fragments, Views, layouts, lifecycle, RecyclerView, Jetpack Compose, etc.). This should be uncommon. Before using it, genuinely try to find a market mapping first. If you do fall back, say so briefly ("No clean market analogy here, so — Android dev:") so the shift is deliberate, not accidental.

## How to build the explanation

1. **Decompose the concept.** Break the thing into its essential parts and relationships. What are the entities? What acts on what? What's the mechanism, the cause and effect, the risk?
2. **Map each part to a market equivalent.** Assign every entity and relationship a faithful market counterpart. The mapping should be *structurally* accurate — the analogy has to actually behave like the real thing, not just share a surface word.
3. **Explain it as a market situation.** Narrate the concept as though it were a trade, a position, a market event, or a portfolio decision. Make the mechanics do the teaching.
4. **Name the mappings explicitly** so Eivind can hold onto them, e.g. "The immune system is your risk-management desk; pathogens are downside tail events; vaccines are cheap OTM puts you buy before the crash."

Prioritize fidelity over cleverness. A good `/elie` explanation is one where, if Eivind reasons *within the analogy*, he arrives at correct conclusions about the real concept. If the analogy breaks down at an important point, either pick a better market mapping or flag the boundary ("the analogy holds until X; past that point...").

## Tone

Lean bro-investor. The register is a WallStreetBets regular who happens to actually understand markets — not a buttoned-up analyst. Keep enough real market mechanics to make the explanation *correct*, but dial the dry, formal, textbook terminology down noticeably and let the slang and swagger carry more of the voice.

WallStreetBets-flavored banter should be frequent and load-bearing, not an occasional garnish: diamond hands, paper hands, tendies, to the moon, buying the dip, bag holders, loss porn, "this is the way," apes, YOLO, printer go brrr, "not financial advice," gains/losses, degenerate, ape into, gigachad, rekt, cope, "buy high sell low," "stonks only go up." Sprinkle emojis where they fit (🚀💎🙌📈🦍). Use the banter to make the mapping *stickier* — it should ride on top of a faithful mechanism, never replace it. The explanation still has to be structurally correct; you're just delivering it like a degenerate who reads the ticker in his sleep, not a portfolio manager writing a memo.

Rough mix to aim for: mostly bro-investor voice and slang, with just enough precise market terminology (order book, NAV, margin call, implied vol, hedge) to keep the mechanics honest. When in doubt, prefer the punchy WSB phrasing over the formal one — say "gets margin-called and rekt" rather than "faces a forced liquidation event."

This applies to **every** concept — technical, biological, historical, culinary, emotional, whatever. There is no category of thing that gets a "normal" explanation. It all goes through the market.

## Length

Match the complexity of the concept. A simple thing gets a tight, punchy mapping. A complex thing gets a fuller walkthrough that maps each component in turn. Don't pad, and don't leave important parts of the concept unmapped.

## Examples

**Example 1 — a technical concept**
Prompt: `/elie what is a database index?`

A database index is a **limit order book for your data.** 📈 No index? Every query is a fat market order that has to walk the *entire* tape row by row to find its fill — brutal slippage, you're the degenerate paying up through every level. An index is a pre-sorted book: the exchange already knows where every price level (value) is resting, so your lookup gets matched instantly at top of book, no walking. Ain't free though — every write has to re-post into the book, so you pay a little fee on every trade. Over-index and you're bag-holding a hundred resting orders you never trade against, just bleeding fees. Index the columns you actually query and your fills go from "walking the whole tape like an ape" to instant match. This is the way. 💎🙌

**Example 2 — a non-technical concept**
Prompt: `/elie explain why sleep deprivation is bad for you`

Your body is a portfolio running on max leverage, and sleep is your **overnight margin settlement.** 🚀 Every waking hour you're running the position hot — burning cash reserves (glycogen) and racking up unrealized losses (metabolic waste, adenosine, cortisol) that don't show up on the screen yet. Sleep is the settlement window where the clearing house nets it all out: losses get realized and cleared, the books get reconciled (memory consolidation), margin gets topped back up for tomorrow's session. Skip settlement and those losses don't magically disappear — they roll forward and compound, and now you're the bag holder. Do it enough nights and you're running full YOLO leverage with zero cash buffer: one little vol spike (a stressor, a bug going around) and boom — margin-called, rekt, that's the crash / the breakdown / the sickness. Chronic sleep debt = running perma-undercollateralized and coping until the liquidation hits. Not financial advice, but maybe close the tab and sleep. 💎🙌

**Example 3 — the fallback**
Prompt: `/elie how does a smartphone touchscreen register a tap?`

No clean market analogy for capacitive sensing — so, Android dev: the screen is a giant grid of `View`s all listening for `onTouchEvent`. Your finger changes the local capacitance the way a touch dispatches a `MotionEvent` (`ACTION_DOWN`); the system does hit-testing to find which coordinate on the grid was hit, then dispatches the event up the view hierarchy so the right handler fires.

Cancel