← ClaudeAtlas

visual-artifactslisted

Use whenever building an HTML page or Artifact: an interactive way to learn a concept (3D, simulation, chart, data visualization), a product prototype with no backend, a learning guide or report, or a development plan page (architecture map, decisions, call trees, task graph). Picks one format (Quick, Guide, Learn, Explorable, Prototype, Plan) and publishes an Artifact. Use even for a bare "make an html", "visualize this", "3D", "chart this", "let me try it", "mock up the app", "walk me through", "homework solutions", "step by step", "quick overview", "explain X so I can teach it", "write up the design", "make the plan page" or "architecture doc". Offer (do not build) a step-through when a chat explanation has not landed after two rounds, and a Plan page when a plan has three or more tasks. A learning request that names no medium comes here. Not for markdown docs, notes, repo files or vault notes (writing-markdown-docs), nor for a decision brief or a short report with a Copy response button (brief-artifact).
SeanoChang/seanock · ★ 0 · Data & Documents · score 70
Install: claude install-skill SeanoChang/seanock
# Visual artifacts Sean learns by watching a mechanism move, and by reading from the simple version down to the deep one. He asks for the depth he wants before the page is built. Every page has one job: give him that format and nothing else. A Plan page does the same for a piece of work: the whole change on one screen, then the claims and decisions, then tasks an agent can pick up. ## Non-negotiables - **The look is the Claude docs, and it comes from `assets/claude.css`**, the one theme for every page (section 4, "Theme"). Sans body text, serif headings only, a near-white page, hairlines, grey pills for the current item. Do not invent a palette, font set or component style per page. Page CSS only arranges. - **Colour: blue, orange, purple and gray only.** Sean is red–green colour-blind. Data colours come from `--s1`…`--s6`; lines and scatter use `--s1`–`--s4`. Every colour is paired with a text label or a pattern, so state never depends on colour alone. Status always has an icon and a word. - **One worked example first, then the parts.** The first screen plays one real case end to end (a request, a task, a proof). Quick pages skip this: they state the answer and stop. Every later section zooms into one part of that example and reuses its numbers (section 2). - **Pick the representation for each idea before writing about it** (section 2a). Text explains a picture; it is never the picture. A section that is mostly prose is a failure (`no-visual`). - **T