dashboard-design
Skill0 starsChanged 3 months agoMITView on GitHub
Designs dashboard layouts with KPI hierarchy, component selection, and attention choreography. Use when creating dashboards, KPI displays, monitoring screens, or executive summary views.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- xsovad06/sovatheir own version, first seen Nov 8, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 8, 2026
- dmoreq/agent-grimoiretheir own version, first seen Nov 8, 2026
- matheus-rib1108/meu-kit-claude-codetheir own version, first seen Nov 1, 2026
- oleg494/coding-kittheir own version, first seen Nov 1, 2026
- ArnavPuri/designskillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use motion-design and design-system.
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.
soilmassSkillmotion-design
Create animations and motion graphics using industry standards. Use when asked to animate UI elements, create video content, implement transitions, or build motion systems. Implements W3C Design Tokens, Material Design 3 baseline, and Lottie specification compliance.
Also in 3 projects that use this
AnthropicSkilldesign-system
Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.
Also in 4 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- abdiraimov-otabek/dashboard-design-skill★ 410same name
- ArnavPuri/designskills★ 17same name
- YepAPI/skills★ 8same name
- Marvellbrazil/my-agentic-skills★ 4same name
- oleg494/coding-kit★ 3same name
- xsovad06/sova★ 3same name
- gmanch94/claude-code-aidlc-template★ 2same name
- valewnrt/design-skills★ 2same name
- tines/skills★ 1same name
- dmoreq/agent-grimoire★ 0same name
7 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 repository5 other files it gives its agents.
- data-storytellerSkill
- data-visualizationSkill
- infographic-creatorSkill
- table-designSkill
- visualization-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
All shared rules in ../../assets/core-standards.md apply.
- Distinctive: line 16
One screen: no scrolling. If it doesn't fit, split into multiple views or add drill-down.
- Very specific: line 35
Follow the branding workflow in ../../assets/core-standards.md.
- Distinctive: line 42
Look for 5 seconds, look away.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Dashboard Design
The user's request: "$ARGUMENTS"
A dashboard is not a collection of charts — it is a single-screen narrative that must pass the 5-second test.
Critical Constraints
All shared rules in ../../assets/core-standards.md apply. Dashboard-specific additions:
- One screen: no scrolling. If it doesn't fit, split into multiple views or add drill-down.
- No gauges — use bullet graphs. No ornamental icons that don't encode data.
- Sparklines need context (min/max/target). Traffic-light red/amber/green always pairs with icons or labels.
Instructions
Step 1: Define Audience and Purpose
Who uses it (executive, analyst, operations)? How often (real-time, daily, weekly)? What decision does it support? What is the single most important question it must answer?
Step 2: Identify and Rank KPIs
List all metrics; rank by which 1–3 answer the primary question. Group the rest as supporting context. Identify targets, thresholds, or benchmarks for each.
Step 3: Select Component Types
Match each metric to a component (KPI tile + sparkline, bullet graph, sorted bar, line ≤3 series, heatmap, simple text) using references/kpi-components.md.
Step 4: Design Layout with Attention Choreography
Top row: primary KPIs, large and left-aligned. Middle: supporting charts. Bottom/right: detail tables and drill-down. Align all panel edges and baselines. Use the templates in references/layout-patterns.md.
Step 5: Apply Branding, Color, and Accessibility
Follow the branding workflow in ../../assets/core-standards.md. On dashboards, alert states (red) should be the only vivid color. Verify contrast deterministically:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_contrast.py" '#FG' '#BG'
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_palette.py" '#hex1,#hex2,...'Step 6: Validate — 5-Second Test
Look for 5 seconds, look away. Can you state the headline insight and which KPIs are off-track? If not: simplify, enlarge primary KPIs, cut noise.
Step 7: Generate Output
Produce the layout/code in the user's preferred tool. After generating, run the visualization-review skill on the output (P0 checks at minimum).
Troubleshooting
"Add more metrics — we need everything on one screen": each added metric dilutes attention on every other metric. Push less critical items to a drill-down or secondary view.
"Use gauges for the KPIs": gauges waste space and resist comparison. Bullet graphs encode the same information (value vs. target) in a compact, comparable form.
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.

