agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/claud3/SKILL.md

claud3

Skill32 starsChanged 6 months agoMITView on GitHub

D3.js data visualization skill based on Edward Tufte principles. Selects the right chart type from a large catalogue by analyzing the data question, then generates single-file HTML with D3 v7, dark theme, responsive layout, direct labels, and annotations.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    License: no LICENSE file in the repo

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

claud3

Catalogue stub — full skill: dtran320/claud3 (the repo and plugin are called claud3; the skill it installs is d3-viz)

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed? Upstream names this skill d3-viz, so it installs next to this pointer (the pointer is not replaced).
    • Global: f=~/.agents/skills/d3-viz/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/d3-viz/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as d3-viz, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/claud3 ] && echo "global" || echo "project"

    Global:

    npx skills add dtran320/claud3 --skill d3-viz -g -y

    Project:

    npx skills add dtran320/claud3 --skill d3-viz -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add dtran320/claud3
/plugin install d3-viz@claud3

Heads-up

  • License: no LICENSE file in the repo
  • Name collision: d3-viz is also written by d3js-skill (its install or its catalogue pointer); installing both overwrites the earlier one.
<!-- das:install:end -->

Invoke after install

  • Skill name: d3-viz
  • Via the Claude Code plugin it is also available as the /d3-viz command.
  • Trigger phrases: "claud3", "D3 Tufte", "80 chart types", "D3 dark theme"

What it does

Applies Edward Tufte's data visualization principles to D3.js chart generation. Analyzes the underlying data question ("how does X change over time?", "how is X spread?") to select the most appropriate chart type from a large catalogue organized by question type (temporal, comparison, distribution, correlation, composition, flow, spatial), then produces self-contained single-file HTML using D3 v7 with a dark theme, responsive SVG, direct data labels (no separate legend), and contextual annotations. Each chart is checked against a Tufte design checklist before output. A playground mode ("explore this data") gives an interactive page for trying chart types and refining.

When NOT to use

  • Multi-library visualization work (D3, Chart.js, Plotly) — use data-viz-agent or antvis-chart-skills instead
  • AntV/G2 charts — use antvis-chart-skills instead
  • Quick single charts without Tufte constraints — use d3js-skill instead (note: d3js-skill also installs a directory named d3-viz; install only one of the two in a project)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free