← ClaudeAtlas

cafleet-create-figurelisted

Create data visualizations and charts using matplotlib. Triggered when user asks to create a chart, plot, graph, or visualize data. Do NOT use plt.show() — always save to PNG files.
himkt/cafleet · ★ 27 · Data & Documents · score 83
Install: claude install-skill himkt/cafleet
# Create Figure Generate matplotlib charts. Scripts, outputs, and data go in separate subdirectories under `figures/`. The skill writes a self-contained Python script that imports matplotlib. The run command is host-project-specific — refer to your project's `.claude/rules/` for the canonical Python invocation. Any environment that provides matplotlib will run the script. **Before writing any script, read the Chart Type Selection and Color Rules sections.** All charts in a deck share the same `C_BAR` / `C_BAR_SEC` palette regardless of data topic. ## Procedure ### 0. Resolve directories **CRITICAL — placeholder convention.** `${FIGURE_BASE}`, `${BASE}`, `${SRC_DIR}`, `${OUTPUT_DIR}`, and `${DATA_DIR}` in this document are **template placeholders, NOT shell environment variables**. You must mentally resolve each one to a concrete absolute path and write that literal path into the script file via the Write tool. **Do NOT** run `export FIGURE_BASE=...`, `FIGURE_BASE=... uv run ...`, or any other shell variable assignment. Bash calls in Claude Code are ephemeral — values set in one call do not persist to the next. The placeholders are resolved entirely in your head, not in the shell. **Resolve `${BASE}` in this order:** 1. **Calling-context override**: If a parent skill's spawn prompt told you the figure base directory (e.g., the `cafleet-research-presentation` skill passes its research folder as the figure base), use that path literally as `${BASE}`. Skip base-dir resolu