Learn

Please make me a rich, interactive explanation of the topic or question I asked about.

Explaining a diff is easy mode: a diff is a bounded artifact, and the answer is sitting in the repo. A general question has no such anchor, so the research step below is the part that makes this skill worth running. Skip it and you produce a beautiful page full of plausible-sounding details recalled from memory.

Research first — mandatory, not a tip

Before writing a single line of HTML, establish where each claim will come from. Every factual claim in the explanation must have one of these provenances:

• Library / framework / browser / platform API → look it up with Context7. Use WebSearch / WebFetch for spec-level detail (MDN, WHATWG, RFCs, release notes) that Context7 doesn't cover. Your training data may be stale or subtly wrong about ordering, defaults, and deprecations — exactly the details a reader will act on.
• Anything empirically checkable → measure it, don't recall it. Run the snippet, drive the browser, print the event order, check the actual output. A measured fact outranks a documented one when they disagree; if they disagree, say so in the page, that contradiction is usually the most interesting thing you'll find.
• Anything about the user's codebase → grep and read the real usages before claiming what the code does.

Anything you could not verify gets flagged inline in the HTML — a visible "unverified" callout naming what you'd need to check it. Never smooth an uncertain claim into confident prose.

Sections