artifact-explainer

Pedagogical HTML artifacts. The reader arrives knowing nothing; they leave with enough mental model to make a decision, search effectively, or argue back with conviction. This is the artifact archetype where progressive disclosure matters most — a flat page of paragraphs is the wrong shape.

Read artifact-css/SKILL.md first for the design system and the page skeleton, including the Interactivity layer section that documents the jQuery + jQuery UI loader pattern. Explainer artifacts always opt-in to that layer.

When to reach for this skill

• User asks "how does X work" with X being non-trivial (event sourcing, vector embeddings, a particular library, an internal service).
• User asks for a primer, deep-dive, or onboarding doc.
• User asks for a feature explainer that needs to handle "I want the headline" and "I want the wire format" readers simultaneously.
• User wants a research-summary artifact (related work, prior art, current consensus).

Static reports, plans, and reviews do NOT use this skill. They're flat by design.

What this skill adds on top of artifact-css

Three jQuery UI widgets, configured to integrate cleanly with the library's visual language: