<< All versions

Skill v1.0.0

currentLLM-judged scan90/100
senweaver/senweavercoding/d3-visualization
──Details
PublishedOctober 22, 2026 at 06:52 AM
Content Hashsha256:f590dcefc0f71e7f...
Git SHAb0d86079461b
──Files
Files (1 file, 3.2 KB)
SKILL.md3.2 KBactive
SKILL.md · 80 lines · 3.2 KB

version: "1.0.0" name: d3-visualization description: | Teaches the agent to produce D3 charts and interactive data visualizations. A comprehensive D3.js skill with examples across chart types and techniques giving the agent expert-level knowledge to generate complex, interactive visualizations. Useful for editorial dashboards, reports, data-rich prototypes, and explanatory graphics. triggers:

  • "d3"
  • "d3.js"
  • "interactive chart"
  • "data visualization"
  • "editorial chart"
  • "d3 bar chart"
  • "d3 line chart"
  • "d3 map"
  • "d3 force graph"
  • "d3 sankey"
  • "d3 treemap"
  • "d3 sunburst"
  • "d3 choropleth"
  • "d3 animation"
  • "d3 scroll"
  • "snow-d3"

od: mode: prototype category: diagrams


d3-visualization

What it does

Teaches the agent to produce D3 charts and interactive data visualizations. A comprehensive D3.js skill with examples across chart types and techniques giving the agent expert-level knowledge to generate complex, interactive visualizations. Useful for editorial dashboards, reports, data-rich prototypes, and explanatory graphics.

Metadata

  • Category: diagrams

How to use in SenWeaverCoding

This skill is embedded in SenWeaverCoding and injected into the Designer system prompt when it matches the active sub-mode. Invoke it by name (d3-visualization) or via one of its trigger phrases. Its bundled templates, checklists, and reference files are read on demand with the designer_skill_read tool (id: d3-visualization, path: <relative file>) — call designer_skill_read with path: SKILL.md first if you need the full body, then pull only the side files a given step requires.

Production flow:

  1. Discovery — restate the brief, target platform, and the single

primary action of the screen.

  1. Plan — choose the active design system and name the one dominant

entry point; list required states (loading/empty/error/populated/edge).

  1. Generate — emit a self-contained HTML artifact into the session's

designer directory (one file, inline CSS, no external CDNs) so the canvas can render it immediately.

  1. Critique — render it, screenshot it, and self-check the P0

anti-ai-slop rules before declaring it done.

SenWeaverCoding strengthening

Hard requirements for every artifact this skill produces inside Designer mode, regardless of the workflow above:

  • Bind to the active design system. Pull palette, type, spacing, and

radius from the selected DESIGN.md / tokens.css; never hardcode an off-token palette or invent a second accent.

  • Apply the craft layer. Honour the injected craft references

(typography, color, anti-ai-slop, state-coverage, accessibility) — they are P0 self-checks at the critique stage, not suggestions.

  • Write into the session directory so the artifact appears in the

per-session canvas; keep files self-contained (inline assets, no external CDNs that break in the sandboxed iframe).

  • Use real content, never filler. No Lorem Ipsum, no invented metrics,

no placeholder copy — compose to fill empty space.

  • Ship every interactive state, not just the populated one, and make

the design responsive and keyboard-operable.

<!-- swc-strengthened -->

All versions