For dummies

Skill muhibwqr/fordummies/skills/for-dummies

Explains any concept from first principles: Big Picture, Real-World Analogy, Technical Stuff, one-sentence REMEMBER. Use when user presses "?" on a flashcard, sends bare "?", or asks for a simplified breakdown, ELI5, "explain like I'm five", "break this down", "I don't get it", "dumb it down", "what does this actually mean".From its SKILL.md

Install

npx -y skills add muhibwqr/fordummies --skill for-dummies

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, as published. Nobody here has run it

Spec compressed. Output is not. Here clarity beat brevity — full sentences, warm tone, no jargon before defined. Overrides caveman-architect voice completely.

Trigger

? on flashcard. Bare ? in chat. "ELI5" / "break this down" / "I don't get it" / "dumb it down".

Format

Emit these four. This order. These headers. Nothing before 💡, nothing after 📌.

### 💡 The Big Picture (In Plain English)
[2-3 sentences. What it is, why anyone care. Zero jargon — unavoidable term gets
defined inline same breath.]

### 🍕 The Real-World Analogy
[ONE physical scenario reader personally lived. Kitchen, mail, traffic, restaurant,
library, apartment. Map parts explicitly — say which is which.]

### 🛠️ Technical Stuff
- [Mechanism]
- [Key term or API, named precisely]
- [Tradeoff, cost, or failure mode]
- [Optional: when to reach for it vs not]

### 📌 REMEMBER
[Exactly one sentence. Under ~20 words. The thing to keep if all else forgotten.]

Rules

3-4 bullets under Technical Stuff. Not 2. Not 7.

ONE analogy carried through. Never stack three half-analogies.

Analogy must map: "Waiter is load balancer. Kitchen is worker pool."

Technical Stuff is where real terms live. code format for identifiers, flags, commands.

REMEMBER — one sentence, no semicolon stacking two ideas.

No preamble. No closing offer. Four sections are whole reply.

Never claim certainty about user's specific codebase without reading it first.

Example

💡 The Big Picture (In Plain English)

A database index is a pre-sorted lookup table the database keeps on the side so it can jump straight to the rows you asked for. Without one, it has to read every single row and check each one.

🍕 The Real-World Analogy

A cookbook with 800 recipes. Finding "every recipe using saffron" means flipping through all 800 pages — that's a full table scan. The index at the back, listing ingredients alphabetically with page numbers, is the database index: you look up "saffron," get pages 44 and 312, and go directly there. The cost is that the index pages take up extra paper, and every time you add a recipe you must also update the back of the book.

🛠️ Technical Stuff

Most SQL indexes are B-trees: a balanced tree giving O(log n) lookup instead of O(n).
You create one with CREATE INDEX idx_users_email ON users(email);.
Indexes cost you on writes — every INSERT/UPDATE/DELETE must maintain them, and they consume disk.
Check whether one is actually used with EXPLAIN ANALYZE; look for Index Scan instead of Seq Scan.

📌 REMEMBER

Indexes trade slower writes and extra disk for dramatically faster reads.