data-visualization
Skill3 starsChanged 23 days agoMITView on GitHub
ALWAYS use before building or changing ANY chart, graph, KPI-tile, dashboard widget or visualization (Vue/SVG/Recharts/ECharts/Chart.js/D3/Python). The Chart Selection Guide picks the chart type from the data relationship (trend, composition, ranking, flow, delta) BEFORE any code is written; also fires on reviewing an existing visual for interpretation, added value or anti-patterns (pie, dual-axis, drowned small series).
48 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- dmoreq/agent-grimoiretheir own version, first seen Nov 8, 2026
- soilmass/motion-design-agenttheir own version, first seen Nov 8, 2026
- OugeX/dsh-web-dev-modetheir own version, first seen Nov 1, 2026
- BuildHarbor/sciagent-skillstheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- shipiit/shipit-ui-designtheir own version, first seen Oct 20, 2026
Used with
Projects with it also use case-study-writing, loading-states and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CAPP-FinancialsSkillcase-study-writing
Client case study with challenge-approach-solution-impact structure and quantified outcomes
Also in 3 projects that use this
soilmassSkillloading-states
Animation patterns for loading, progress, and waiting states. Use for skeleton screens, progress indicators, optimistic UI, and content placeholder transitions. Keeps users informed and engaged during async operations.
Also in 3 projects that use this
nddqSkilldashboard-design
Also in 4 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 3 projects that use this
nandanosqlSkillswot-analysis
Conduct a structured SWOT analysis — Strengths, Weaknesses, Opportunities, Threats — that connects internal capabilities to external forces for strategic decision-making.
Also in 3 projects that use this
abinauvSkillchange-management
Comprehensive change management consulting toolkit — stakeholder mapping, ADKAR framework, Kotter's 8-Step Model, communication planning, resistance analysis, cultural assessment, readiness assessment, training needs analysis, impact assessment, and transition planning.
Also in 3 projects that use this
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 7
- anthropics/knowledge-work-plugins★ 35k97% same
- didixuxu/didi-skills★ 8370% same
- miptah21/skills★ 297% same
- kongaharsha/claude-skills★ 197% same
- UtkarshDubeyGIT/agent-skills★ 197% same
- edu6565/claude-skills★ 097% same
- jmolz/m0lz.01★ 097% same
Wrote their own version · 41
- langchain-ai/deepagents★ 31ksame name
- openai/plugins★ 7.8ksame name
- vivy-yi/xiaohongshu-skills★ 455same name
- NTCoding/claude-skillz★ 342same name
- launchapp-dev/animus-cli★ 39same name
- xjtulyc/awesome-rosetta-skills★ 34same name
- kensaurus/cursor-kenji★ 9same name
- kensaurus/skills★ 9same name
- rade-nugroho/Agentic-Enteprises-Skill★ 9same name
- daemon-blockint-tech/Agentic-Enteprises-Skill★ 8same name
31 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- guidelines/CLAUDE.mdCLAUDE.md
- animate-expoSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- ask-sonnerSkill
- batch-grill-meSkill
- bi-dashboardsSkill
- bouw-loopSkill
- brandkitSkill
- code-auditSkill
- commit-disciplineSkill
- councilSkill
- createlooppromptSkill
- design-taste-frontendSkill
- diagram-designSkill
- dicht-loopSkill
- e2e-rulesSkill
- e2eSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- find-bugsSkill
- fixing-accessibilitySkill
- fix-loopSkill
- frontend-gotchasSkill
- goalSkill
- improve-animationsSkill
- keten-loopSkill
- make-interfaces-feel-betterSkill
- mobile-nativeSkill
- office-docsSkill
- pick-ui-librarySkill
- polijst-loopSkill
- polpohire-designSkill
- pre-pr-gatesSkill
- projectstructuurSkill
- prototypeSkill
- readmeSkill
- reaSkill
- redesign-existing-projectsSkill
- render-proofSkill
- repo-hygieneSkill
- review-animationsSkill
- skill-finderSkill
- speur-loopSkill
- supergoalSkill
- systematic-debuggingSkill
- theme-selectorSkill
- transitions-devSkill
- ux-heuristicsSkill
- waak-loopSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 23 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
23
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Pie charts: Avoid unless <6 categories and exact proportions matter less than rough comparison.
- Distinctive: line 34
3D charts: Never. They distort perception and add no information.
- Distinctive: line 35
Dual-axis charts: Use cautiously. They can mislead by implying correlation.
- Distinctive: line 246
Highlight the story: Use a bright accent color for the key insight.
- Distinctive: line 247
Sequential data: Use a single-hue gradient (light to dark) for ordered values
- Distinctive: line 248
Diverging data: Use a two-hue gradient with neutral midpoint for data with a meaningful center
- Distinctive: line 249
Categorical data: Use distinct hues, maximum 6-8 before it gets confusing
- Distinctive: line 256
Axis labels are readable: Never rotated 90 degrees if avoidable.
- Distinctive: line 257
Data labels add precision: Use on key points, not every single bar
- Distinctive: line 258
Annotation highlights: Call out specific points with text annotations
- Distinctive: line 262
Reduce chart junk: Remove gridlines, borders, backgrounds that don't carry information
- Distinctive: line 265
White space is good: Don't cram charts together.
- Distinctive: line 269
Bar charts start at zero: Always. A bar from 95 to 100 exaggerates a 5% difference
- Distinctive: line 270
Line charts can have non-zero baselines: When the range of variation is meaningful
- Distinctive: line 271
Consistent scales across panels: When comparing multiple charts, use the same axis range
- Distinctive: line 273
Label your axes: Never make the reader guess what the numbers mean
- Distinctive: line 279
Never rely on color alone to distinguish data series
- Distinctive: line 280
Add pattern fills, different line styles (solid, dashed, dotted), or direct labels
- Distinctive: line 281
Test with a colorblind simulator (e.g., Coblis, Sim Daltonism)
- Very specific: line 282
Use the colorblind-friendly palette: sns.color_palette("colorblind")
- Distinctive: line 288
Use semantic titles and labels
- Distinctive: line 294
Avoid conveying information only through spatial position (add labels)
- Distinctive: line 295
Consider printing: does the chart work in black and white?
- Distinctive: line 299
Before sharing a visualization:
“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Visualization Skill
Chart selection guidance, Python visualization code patterns, design principles, and accessibility considerations for creating effective data visualizations.
Chart Selection Guide
Choose by Data Relationship
| What You're Showing | Best Chart | Alternatives |
| Trend over time | Line chart | Area chart (if showing cumulative or composition) |
| Comparison across categories | Vertical bar chart | Horizontal bar (many categories), lollipop chart |
| Ranking | Horizontal bar chart | Dot plot, slope chart (comparing two periods) |
| Part-to-whole composition | Stacked bar chart | Treemap (hierarchical), waffle chart |
| Composition over time | Stacked area chart | 100% stacked bar (for proportion focus) |
| Distribution | Histogram | Box plot (comparing groups), violin plot, strip plot |
| Correlation (2 variables) | Scatter plot | Bubble chart (add 3rd variable as size) |
| Correlation (many variables) | Heatmap (correlation matrix) | Pair plot |
| Geographic patterns | Choropleth map | Bubble map, hex map |
| Flow / process | Sankey diagram | Funnel chart (sequential stages) |
| Relationship network | Network graph | Chord diagram |
| Performance vs. target | Bullet chart | Gauge (single KPI only) |
| Multiple KPIs at once | Small multiples | Dashboard with separate charts |
When NOT to Use Certain Charts
- Pie charts: Avoid unless <6 categories and exact proportions matter less than rough comparison. Humans are bad at comparing angles. Use bar charts instead.
- 3D charts: Never. They distort perception and add no information.
- Dual-axis charts: Use cautiously. They can mislead by implying correlation. Clearly label both axes if used.
- Stacked bar (many categories): Hard to compare middle segments. Use small multiples or grouped bars instead.
- Donut charts: Slightly better than pie charts but same fundamental issues. Use for single KPI display at most.
Python Visualization Code Patterns
Setup and Style
import matplotlib.pyplot as plt
import matplotlib.ticker as mticker
import seaborn as sns
import pandas as pd
import numpy as np
# Professional style setup
plt.style.use('seaborn-v0_8-whitegrid')
plt.rcParams.update({
'figure.figsize': (10, 6),
'figure.dpi': 150,
'font.size': 11,
'axes.titlesize': 14,
'axes.titleweight': 'bold',
'axes.labelsize': 11,
'xtick.labelsize': 10,
'ytick.labelsize': 10,
'legend.fontsize': 10,
'figure.titlesize': 16,
})
# Colorblind-friendly palettes
PALETTE_CATEGORICAL = ['#4C72B0', '#DD8452', '#55A868', '#C44E52', '#8172B3', '#937860']
PALETTE_SEQUENTIAL = 'YlOrRd'
PALETTE_DIVERGING = 'RdBu_r'Line Chart (Time Series)
fig, ax = plt.subplots(figsize=(10, 6))
for label, group in df.groupby('category'):
ax.plot(group['date'], group['value'], label=label, linewidth=2)
ax.set_title('Metric Trend by Category', fontweight='bold')
ax.set_xlabel('Date')
ax.set_ylabel('Value')
ax.legend(loc='upper left', frameon=True)
ax.spines['top'].set_visible(False)
ax.spines['right'].set_visible(False)
# Format dates on x-axis
fig.autofmt_xdate()
plt.tight_layout()
plt.savefig('trend_chart.png', dpi=150, bbox_inches='tight')Bar Chart (Comparison)
fig, ax = plt.subplots(figsize=(10, 6))
# Sort by value for easy reading
df_sorted = df.sort_values('metric', ascending=True)
bars = ax.barh(df_sorted['category'], df_sorted['metric'], color=PALETTE_CATEGORICAL[0])
# Add value labels
for bar in bars:
width = bar.get_width()
ax.text(width + 0.5, bar.get_y() + bar.get_height()/2,
f'{width:,.0f}', ha='left', va='center', fontsize=10)
ax.set_title('Metric by Category (Ranked)', fontweight='bold')
ax.set_xlabel('Metric Value')
ax.spines['top'].set_visible(False)
ax.spines['right'].set_visible(False)
plt.tight_layout()
plt.savefig('bar_chart.png', dpi=150, bbox_inches='tight')Histogram (Distribution)
fig, ax = plt.subplots(figsize=(10, 6))
ax.hist(df['value'], bins=30, color=PALETTE_CATEGORICAL[0], edgecolor='white', alpha=0.8)
# Add mean and median lines
mean_val = df['value'].mean()
median_val = df['value'].median()
ax.axvline(mean_val, color='red', linestyle='--', linewidth=1.5, label=f'Mean: {mean_val:,.1f}')
ax.axvline(median_val, color='green', linestyle='--', linewidth=1.5, label=f'Median: {median_val:,.1f}')
ax.set_title('Distribution of Values', fontweight='bold')
ax.set_xlabel('Value')
ax.set_ylabel('Frequency')
ax.legend()
ax.spines['top'].set_visible(False)
ax.spines['right'].set_visible(False)
plt.tight_layout()
plt.savefig('histogram.png', dpi=150, bbox_inches='tight')Heatmap
fig, ax = plt.subplots(figsize=(10, 8))
# Pivot data for heatmap format
pivot = df.pivot_table(index='row_dim', columns='col_dim', values='metric', aggfunc='sum')
sns.heatmap(pivot, annot=True, fmt=',.0f', cmap='YlOrRd',
linewidths=0.5, ax=ax, cbar_kws={'label': 'Metric Value'})
ax.set_title('Metric by Row Dimension and Column Dimension', fontweight='bold')
ax.set_xlabel('Column Dimension')
ax.set_ylabel('Row Dimension')
plt.tight_layout()
plt.savefig('heatmap.png', dpi=150, bbox_inches='tight')Small Multiples
categories = df['category'].unique()
n_cats = len(categories)
n_cols = min(3, n_cats)
n_rows = (n_cats + n_cols - 1) // n_cols
fig, axes = plt.subplots(n_rows, n_cols, figsize=(5*n_cols, 4*n_rows), sharex=True, sharey=True)
axes = axes.flatten() if n_cats > 1 else [axes]
for i, cat in enumerate(categories):
ax = axes[i]
subset = df[df['category'] == cat]
ax.plot(subset['date'], subset['value'], color=PALETTE_CATEGORICAL[i % len(PALETTE_CATEGORICAL)])
ax.set_title(cat, fontsize=12)
ax.spines['top'].set_visible(False)
ax.spines['right'].set_visible(False)
# Hide empty subplots
for j in range(i+1, len(axes)):
axes[j].set_visible(False)
fig.suptitle('Trends by Category', fontsize=14, fontweight='bold', y=1.02)
plt.tight_layout()
plt.savefig('small_multiples.png', dpi=150, bbox_inches='tight')Number Formatting Helpers
def format_number(val, format_type='number'):
"""Format numbers for chart labels."""
if format_type == 'currency':
if abs(val) >= 1e9:
return f'${val/1e9:.1f}B'
elif abs(val) >= 1e6:
return f'${val/1e6:.1f}M'
elif abs(val) >= 1e3:
return f'${val/1e3:.1f}K'
else:
return f'${val:,.0f}'
elif format_type == 'percent':
return f'{val:.1f}%'
elif format_type == 'number':
if abs(val) >= 1e9:
return f'{val/1e9:.1f}B'
elif abs(val) >= 1e6:
return f'{val/1e6:.1f}M'
elif abs(val) >= 1e3:
return f'{val/1e3:.1f}K'
else:
return f'{val:,.0f}'
return str(val)
# Usage with axis formatter
ax.yaxis.set_major_formatter(mticker.FuncFormatter(lambda x, p: format_number(x, 'currency')))Interactive Charts with Plotly
import plotly.express as px
import plotly.graph_objects as go
# Simple interactive line chart
fig = px.line(df, x='date', y='value', color='category',
title='Interactive Metric Trend',
labels={'value': 'Metric Value', 'date': 'Date'})
fig.update_layout(hovermode='x unified')
fig.write_html('interactive_chart.html')
fig.show()
# Interactive scatter with hover data
fig = px.scatter(df, x='metric_a', y='metric_b', color='category',
size='size_metric', hover_data=['name', 'detail_field'],
title='Correlation Analysis')
fig.show()Design Principles
Color
- Use color purposefully: Color should encode data, not decorate
- Highlight the story: Use a bright accent color for the key insight; grey everything else
- Sequential data: Use a single-hue gradient (light to dark) for ordered values
- Diverging data: Use a two-hue gradient with neutral midpoint for data with a meaningful center
- Categorical data: Use distinct hues, maximum 6-8 before it gets confusing
- Avoid red/green only: 8% of men are red-green colorblind. Use blue/orange as primary pair
Typography
- Title states the insight: "Revenue grew 23% YoY" beats "Revenue by Month"
- Subtitle adds context: Date range, filters applied, data source
- Axis labels are readable: Never rotated 90 degrees if avoidable. Shorten or wrap instead
- Data labels add precision: Use on key points, not every single bar
- Annotation highlights: Call out specific points with text annotations
Layout
- Reduce chart junk: Remove gridlines, borders, backgrounds that don't carry information
- Sort meaningfully: Categories sorted by value (not alphabetically) unless there's a natural order (months, stages)
- Appropriate aspect ratio: Time series wider than tall (3:1 to 2:1); comparisons can be squarer
- White space is good: Don't cram charts together. Give each visualization room to breathe
Accuracy
- Bar charts start at zero: Always. A bar from 95 to 100 exaggerates a 5% difference
- Line charts can have non-zero baselines: When the range of variation is meaningful
- Consistent scales across panels: When comparing multiple charts, use the same axis range
- Show uncertainty: Error bars, confidence intervals, or ranges when data is uncertain
- Label your axes: Never make the reader guess what the numbers mean
Accessibility Considerations
Color Blindness
- Never rely on color alone to distinguish data series
- Add pattern fills, different line styles (solid, dashed, dotted), or direct labels
- Test with a colorblind simulator (e.g., Coblis, Sim Daltonism)
- Use the colorblind-friendly palette:
sns.color_palette("colorblind")
Screen Readers
- Include alt text describing the chart's key finding
- Provide a data table alternative alongside the visualization
- Use semantic titles and labels
General Accessibility
- Sufficient contrast between data elements and background
- Text size minimum 10pt for labels, 12pt for titles
- Avoid conveying information only through spatial position (add labels)
- Consider printing: does the chart work in black and white?
Accessibility Checklist
Before sharing a visualization:
- Chart works without color (patterns, labels, or line styles differentiate series)
- Text is readable at standard zoom level
- Title describes the insight, not just the data
- Axes are labeled with units
- Legend is clear and positioned without obscuring data
- Data source and date range are noted
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
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.

