data-visualization
Skill9 starsChanged 42 days agoMITView on GitHub
Build interactive, accessible charts and dashboards with Recharts, D3, or Victory. Use when "chart", "graph", "data visualization", "analytics dashboard", "metrics display", "time-series", "D3", or "Recharts".
48 other projects use a version of this, 1 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 · 1
- kensaurus/skills★ 932% same
Wrote their own version · 47
- anthropics/knowledge-work-plugins★ 35ksame name
- langchain-ai/deepagents★ 31ksame name
- openai/plugins★ 7.8ksame name
- vivy-yi/xiaohongshu-skills★ 455same name
- NTCoding/claude-skillz★ 342same name
- didixuxu/didi-skills★ 83same name
- launchapp-dev/animus-cli★ 39same name
- xjtulyc/awesome-rosetta-skills★ 34same name
- rade-nugroho/Agentic-Enteprises-Skill★ 9same name
- daemon-blockint-tech/Agentic-Enteprises-Skill★ 8same name
37 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 repository165 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/approved-plan-execution.mdcCursor rule
- .cursor/rules/skill-workflows.mdcCursor rule
- .cursor/rules/verification-before-completion.mdcCursor rule
- llms.txtllms.txt
- audit-accessibilitySkill
- audit-agent-speedSkill
- audit-analyticsSkill
- audit-auth-flowsSkill
- audit-backend-architectureSkill
- audit-bundle-sizeSkill
- audit-cicdSkill
- audit-codemod-safetySkill
- audit-code-qualitySkill
- audit-code-reviewSkill
- audit-db-schemaSkill
- audit-doctrineSkill
- audit-env-paritySkill
- audit-fe-apiSkill
- audit-gate-logicSkill
- audit-i18nSkill
- audit-infra-costSkill
- audit-langfuse-llmSkill
- audit-llm-securitySkill
- audit-monetization-iapSkill
- audit-payment-systemSkill
- audit-performanceSkill
- audit-realworldSkill
- audit-registry-listingSkill
- audit-resilienceSkill
- audit-responsiveSkill
- audit-securitySkill
- audit-skill-conflictsSkill
- audit-ui-statesSkill
- audit-uiux-design-systemSkill
- audit-ux-journeysSkill
- audit-uxSkill
- backend-db-performanceSkill
- backend-error-handlingSkill
- backend-observabilitySkill
- backend-patternsSkill
- backend-realtimeSkill
- burndown-fullSkill
- complete-everythingSkill
- data-pipelineSkill
- debug-errorSkill
- debug-fe-be-integrationSkill
- debug-sentry-monitorSkill
- deploy-npmSkill
- deploy-verifySkill
- design-apiSkill
- design-canvasSkill
- design-emailSkill
- design-frontendSkill
- design-generative-artSkill
- design-mobile-firstSkill
- design-motionSkill
- design-prdSkill
- design-systemSkill
- design-themeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
2
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 36
Create beautiful, accessible, and interactive data visualizations for dashboards and reports.
- Distinctive: line 62
Why: Use existing chart library and styling conventions.
- Very specific: line 96
Place it in a w-20 slot beside the stat value, never as its own card.
“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
Degree of freedom: MIXED. Chart type and encoding [HIGH freedom];
existing-library/token probes and a11y fallback [LOW freedom — run exactly].
How to reason
- Observe — existing chart library, tokens, data shape
- Interpret — reuse a component vs new chart type
- Classify — line / bar / area / donut / sparkline / table-fallback
- Severity — inaccessible or empty-state-less chart outranks a missing gradient
Worked example
Observe:
package.jsonhas recharts; nosrc/components/charts; tokens define--primary. Interpret: reuse Recharts + tokens, not D3. Classify:ResponsiveContainerline chart + sr-only table; skeleton while loading. Verify: resizes; screen-reader table present; no second chart library.
Self-critique before reporting
- Existing lib — grepped
package.json; did not add a second chart library - Accessible — sr-only table or text alternative present
- States — loading + empty handled
- Right owner — event taxonomy →
audit-analytics; empty/loading frames →audit-ui-states
Create beautiful, accessible, and interactive data visualizations for dashboards and reports.
Product-event coverage ("are we tracking the right events?") is audit-analytics,
not this skill. Empty/loading chart frames are audit-ui-states.
Check existing first [LOW freedom — run exactly]
Before creating ANY visualization, verify:
- Check for existing chart libraries:
cat package.json | grep -i "recharts\|chart\|d3\|visx\|nivo\|tremor"
rg "LineChart|BarChart|PieChart" --type tsx -l | head -10- Check for existing chart components:
ls -la src/components/charts/ src/components/dashboard/ 2>/dev/null
rg "ResponsiveContainer|Chart" --type tsx | head -10- Check for design tokens:
cat tailwind.config.* | grep -A10 "chart\|colors"Why: Use existing chart library and styling conventions.
Recharts (Recommended for React) [HIGH freedom]
- Wrap every chart in
ResponsiveContainer width="100%"; set a fixedheight. - Style through tokens:
hsl(var(--primary)),fill-muted-foreground,stroke-muted; no hard-coded hex. - Hide axis lines and tick lines (
tickLine={false} axisLine={false}); format Y ticks ($,%). - Custom
Tooltipcontent usesbg-background border rounded-lgso it matches the theme. - Chart types: line (trend over time), bar (
radius={[4,4,0,0]}, highlight the latestCell), area (gradient<defs>fill), donut (innerRadius/outerRadius+ centerLabelfor the total).
'use client'
import { LineChart, Line, XAxis, YAxis, Tooltip, ResponsiveContainer } from 'recharts'
export function RevenueChart({ data }: { data: { month: string; revenue: number }[] }) {
return (
<ResponsiveContainer width="100%" height={350}>
<LineChart data={data}>
<XAxis dataKey="month" tickLine={false} axisLine={false} className="text-xs fill-muted-foreground" />
<YAxis tickLine={false} axisLine={false} tickFormatter={(v) => `$${v}`} />
<Tooltip cursor={{ stroke: 'hsl(var(--muted))' }} />
<Line type="monotone" dataKey="revenue" stroke="hsl(var(--primary))" strokeWidth={2} activeDot={{ r: 6 }} />
</LineChart>
</ResponsiveContainer>
)
}Full line chart with custom tooltip, bar, area-gradient and donut components: references/recharts.md §Line chart, §Bar chart, §Area chart, §Pie/Donut chart.
Sparklines (Mini Charts) [HIGH freedom]
- A
LineChartwith oneLine,dot={false},strokeWidth={1.5}, no axes, height ~40. - Map a
number[]to{ index, value }inside the component so callers pass plain arrays. - Place it in a
w-20slot beside the stat value, never as its own card.
Sparkline component and stats-card usage: references/recharts.md §Sparklines.
Stat Cards with Trends [HIGH freedom]
rounded-xl border bg-card p-6; title intext-muted-foreground, valuetext-3xl font-semibold.- Trend arrow +
Math.abs(change)%; green for up, red for down; pass the same color to the sparkline. sparklineDatais optional; render the sparkline only when present.
StatCard component: references/recharts.md §Stat cards with trends.
Real-time Data Updates [HIGH freedom]
- Append in
setData(prev => [...prev, point].slice(-N)); keep a bounded window (about 20 points). isAnimationActive={false}and a fixedYAxis domainso the chart does not jump per tick.- Clear the interval or socket subscription in the effect cleanup.
RealtimeChart component: references/recharts.md §Real-time data updates.
D3.js for Custom Visualizations [HIGH freedom]
- Reach for D3 only when Recharts cannot express the mark; never add it beside an existing chart library.
- Render into a
ref'd<svg>fromuseEffect;svg.selectAll('*').remove()before redrawing on data change. scaleBandfor categories,scaleLinear().nice()for values; size fromclientWidth/clientHeight, with margins.- Animate with
.transition().duration(750)from the baseline; color with the samehsl(var(--primary))tokens.
Full D3 bar chart component: references/d3-and-accessibility.md §D3.js custom bar chart.
Accessibility [LOW freedom — run exactly]
- Wrap the chart in
<div role="img" aria-label="...">that states what the chart shows and its range. - Mark the SVG chart
aria-hidden="true"; provide the data as ansr-only<table>with a<caption>. - Color is never the only encoding: pair it with labels, markers, or a legend.
<div role="img" aria-label="Revenue chart showing monthly data from January to December">
<ResponsiveContainer><LineChart data={data} aria-hidden="true">{/* ... */}</LineChart></ResponsiveContainer>
<table className="sr-only">
<caption>Monthly Revenue Data</caption>
<thead><tr><th>Month</th><th>Revenue</th></tr></thead>
<tbody>{data.map((d) => <tr key={d.month}><td>{d.month}</td><td>${d.revenue}</td></tr>)}</tbody>
</table>
</div>Full accessibility block: references/d3-and-accessibility.md §Accessibility.
Validation [LOW freedom — do not skip]
After creating visualizations:
- Responsive → Charts resize properly on all screens
- Accessible → Screen reader alternatives provided
- Performance → Large datasets use virtualization/sampling
- Loading states → Skeleton shown while data loads
- Empty states → Meaningful message when no data
- Color contrast → Meets WCAG guidelines
- Tooltips → Provide detailed data on hover
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.

