К основному содержанию
скилл CX Codex

dashboard-designer — скилл для Claude Code: дашборды и установка

Скилл dashboard-designer для Claude Code помогает спроектировать дашборд: выбрать KPI, расположить блоки и настроить визуальную иерархию. Запускается на запросы о структуре панели мониторинга или выборе BI-инструмента.

MIT 109 установок ★ 71 обновлён 2026-06-29

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add NickCrew/Claude-Cortex --skill dashboard-designer -a claude-code
Открыть на GitHub

Что делает dashboard-designer

Скилл помогает определить аудиторию и цель дашборда, выбрать показатели и разложить данные по уровням важности. Он предлагает продумать KPI, структуру экрана, цветовую кодировку и частоту обновления. Для стратегической, операционной и аналитической панелей нужны разные наборы метрик и схемы расположения.

Также скилл помогает выбрать BI-инструмент, например Tableau или Power BI. Он не пишет SQL-запросы и код графиков: для этих задач нужны отдельные скиллы sql-analyst и chart-builder.

Какие задачи решает

  • выбрать KPI для дашборда
  • расположить показатели и графики на экране
  • разобрать перегруженную или запутанную панель
  • сравнить BI-инструменты для задачи

Примеры запросов агенту

  • Помоги спроектировать дашборд для отдела продаж: какие KPI показать и как расположить блоки?
  • Предложи структуру панели мониторинга для руководителей.
  • Сравни Tableau и Power BI для нашего дашборда.

Как установить dashboard-designer

1Через Skills CLI (Vercel)

npx skills add NickCrew/Claude-Cortex --skill dashboard-designer -a claude-code

2Вручную: положить файлы

~/.claude/skills/dashboard-designer/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/dashboard-designer/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о dashboard-designer

Как установить dashboard-designer в Claude Code?

Выполните npx skills add NickCrew/Claude-Cortex --skill dashboard-designer -a claude-code. Файл скилла появится по пути ~/.claude/skills/dashboard-designer/SKILL.md.

Что делает dashboard-designer?

Помогает определить KPI, спланировать расположение элементов и визуальную иерархию дашборда, а также выбрать BI-инструмент.

Может ли dashboard-designer написать SQL-запросы или код графиков?

Нет. Для SQL-запросов предназначен скилл sql-analyst, а для кода графиков на Python или JavaScript — chart-builder.

Исходный текст

SKILL.md · MIT
---
name: dashboard-designer
description: 'Use this skill when designing a data dashboard—choosing KPIs, structuring layout, applying visual hierarchy, or deciding which BI tool to use. Trigger phrases: ''design a dashboard'', ''build a KPI dashboard'', ''what should my dashboard show'', ''help me layout a dashboard'', ''dashboard for monitoring''. Not for building chart code from scratch (use chart-builder), writing SQL queries (use sql-analyst), or designing marketing landing pages.'
version: 1.0.0
author: community
tags:
  - data
  - dashboard
  - visualization
  - business-intelligence
license: MIT
keywords:
  - design dashboard
  - KPI dashboard
  - BI tool
  - dashboard layout
  - dashboard
  - designer
  - dashboard designer
---

# Dashboard Designer

## Overview
This skill provides a structured approach to dashboard design—from defining the right KPIs and audience through information architecture, visual hierarchy, color coding, and tool selection. A well-designed dashboard surfaces the right information to the right person at the right time. This skill combines data visualization principles with UX thinking to create dashboards that drive decisions, not just display data.

## When to Use
- You're building a new dashboard and need to decide what to show and how to arrange it
- An existing dashboard is cluttered, ignored, or confusing to users
- You need to choose between BI tools (Tableau, Power BI, Looker, Grafana)
- You want to design a KPI framework before building the technical implementation
- You're presenting data to an executive audience and need to structure the narrative

## When NOT to Use
- Writing SQL queries to power the dashboard (use sql-analyst skill)
- Building chart code in Python/JavaScript (use chart-builder skill)
- Creating a static report or slide deck (use a presentation skill)
- Designing the underlying data model or warehouse (use a data engineering skill)

## Quick Reference
| Design Principle | Rule |
|-----------------|------|
| Visual hierarchy | Most important KPI top-left; details bottom-right |
| White space | 15–20% of dashboard area; prevents cognitive overload |
| Color coding | Max 4–5 colors; use red/green for status, grey for context |
| Chart density | Max 6–8 charts per screen; prefer fewer, larger charts |
| KPI count | Executive: 3–5 KPIs. Operational: 8–12. Analyst: unlimited |
| Text | Titles as insights ("Revenue Up 12%"), not labels ("Revenue") |
| Refresh rate | Real-time for ops, daily for management, weekly/monthly for strategy |
| Interactivity | Filters at top; drill-down by click; default to most common view |
| Mobile | Stack charts vertically for mobile; limit to top 3 KPIs |
| Accessibility | Colorblind-safe palette; min contrast ratio 4.5:1 |

## Instructions

### Step 1: Define the Audience and Purpose
Answer these questions before designing anything:
1. **Who uses this dashboard?** Executive, team manager, analyst, engineer, customer?
2. **What decision does it inform?** ("Should we increase marketing spend in the West region?")
3. **How often will they look at it?** Real-time (ops), daily, weekly, monthly?
4. **What action can they take?** If no action → reconsider whether a dashboard is the right format.

**Dashboard archetypes:**
| Type | Audience | Refresh | KPI Count | Example |
|------|----------|---------|-----------|---------|
| Strategic | C-suite, VPs | Weekly/Monthly | 3–5 | Company health scorecard |
| Operational | Team leads, managers | Daily | 8–15 | Sales pipeline dashboard |
| Analytical | Data analysts | On-demand | Unlimited | Cohort analysis explorer |
| Real-time monitoring | Engineers, support | Live | 10–20 | System uptime & error rates |

### Step 2: Select the Right KPIs
A KPI must be:
- **Actionable**: the viewer can change it based on what they see
- **Timely**: available at the frequency the dashboard refreshes
- **Comparable**: has a target, benchmark, or prior period to compare against
- **Unambiguous**: has one clear definition shared by all stakeholders

**KPI selection process:**
1. List 20 metrics the audience cares about
2. Filter to metrics the audience can act on (eliminate vanity metrics)
3. Group remaining into 3–5 themes (e.g., Revenue, Customers, Operations, Quality)
4. Pick 1–3 primary metrics per theme
5. Define calculation, data source, and owner for each

**KPI tiers:**
- **Level 1 (headline)**: 3–5 KPIs shown large at the top (Total Revenue, MAU, NPS)
- **Level 2 (supporting)**: 6–10 charts providing context (by region, by product, trend)
- **Level 3 (detail)**: Tables or drill-downs for investigation

### Step 3: Information Architecture (Layout Patterns)

**F-pattern layout** (most common): Users scan top-left → top-right → down the left.
```
┌─────────────────────────────────────────────────────┐
│  KPI 1        KPI 2        KPI 3        KPI 4       │  ← Headline KPIs
├───────────────────────┬─────────────────────────────┤
│                       │                             │
│  Primary chart        │  Secondary chart            │  ← Primary context
│  (e.g. revenue trend) │  (e.g. by region)           │
│                       │                             │
├───────────────────────┴─────────────────────────────┤
│  Detail chart 1    │  Detail chart 2  │  Table      │  ← Supporting detail
└────────────────────┴──────────────────┴─────────────┘
```

**Z-pattern layout** (executive dashboards): Fewer elements, high-level narrative flow.

**Grid layout** (operational dashboards): Equal-sized tiles arranged in rows.

### Step 4: Visual Hierarchy Principles
1. **Size**: Larger = more important. Make the most critical KPI card the biggest element.
2. **Position**: Top-left corner gets most attention. Put the hero metric there.
3. **Color**: Use strong color (blue, orange) for primary data; grey for all context.
4. **Typography**: Metric values large (24–32pt), labels small (10–12pt), titles medium (14–16pt).
5. **White space**: Empty space is not wasted—it guides the eye and reduces fatigue.

### Step 5: Color Coding System
Establish a consistent color language:
- 🟢 **Green**: good, on track, above target
- 🔴 **Red**: bad, alert, below target
- 🟡 **Yellow/Orange**: caution, approaching threshold
- 🔵 **Blue**: primary data, neutral information
- ⬜ **Grey**: secondary data, prior period, context

**Colorblind-safe alternative palette:**
- Use: `#0077BB` (blue), `#EE7733` (orange), `#009988` (teal), `#CC3311` (red)
- Avoid: pure red + pure green together without texture or label differentiation

### Step 6: BI Tool Selection Guide
| Tool | Best For | Strengths | Limitations |
|------|----------|-----------|-------------|
| **Tableau** | Enterprise BI, complex visualizations | Powerful viz, strong community, drag-and-drop | Expensive, steep learning curve |
| **Power BI** | Microsoft-centric orgs, self-service BI | Deep Excel/Azure integration, affordable | Less flexible layout, DAX complexity |
| **Looker** | Data-team-driven, engineering-heavy orgs | LookML modeling, governed metrics, Git integration | Requires data engineers, expensive |
| **Grafana** | Real-time monitoring, engineering metrics | Live data, alerting, open source | Not for business users, limited chart types |
| **Metabase** | Small teams, SQL-first analytics | Open source, easy SQL → dashboard | Limited advanced features |
| **Google Data Studio (Looker Studio)** | Google Workspace users, quick sharing | Free, easy to share, Google Sheets integration | Limited transformations, basic visuals |
| **Retool** | Operational dashboards with actions | CRUD operations, internal tools | Requires developer to set up |

**Quick selector:**
- Startup with small team → Metabase or Looker Studio
- Enterprise with existing Microsoft stack → Power BI
- Data team building governed metrics layer → Looker
- Engineering monitoring → Grafana
- Best-in-class viz + large budget → Tableau

### Step 7: Dashboard Quality Checklist
Before publishing, verify:
- [ ] Every chart has a title stating the insight (not just the metric name)
- [ ] Every KPI has a comparison value (vs. target, vs. last period)
- [ ] Color coding is consistent throughout
- [ ] Date range is clearly labeled and user-controlled
- [ ] Filters are at the top and default to the most common view
- [ ] All numbers are formatted with appropriate precision (revenue: $1.2M not $1,234,567.89)
- [ ] Data source and refresh date are visible in a footer
- [ ] Mobile layout tested (if relevant)

## Examples

### Example 1: Design a Sales Performance Dashboard
**Input:** "I need a dashboard for our VP of Sales to review weekly. We care about revenue, pipeline health, and team performance."

**Audience analysis:** VP of Sales — executive level — weekly review — strategic decisions about team resourcing and focus.

**KPI selection (Level 1 — headline):**
1. **Bookings (ARR)** — new closed revenue this week vs target
2. **Pipeline Coverage** — pipeline value / quota (target: 3× coverage)
3. **Win Rate** — % of deals closed-won (target: 25%)
4. **Deals at Risk** — open deals past expected close date

**Layout design:**
```
┌────────────────────────────────────────────────────────────────┐
│ FILTER: [Week ▼]  [Region ▼]  [Rep ▼]          Data as of Mon │
├──────────────┬──────────────┬──────────────┬──────────────────┤
│ Bookings     │ Pipeline     │ Win Rate     │ Deals at Risk    │
│ $1.2M        │ 3.4× quota   │ 28%          │ 12 deals         │
│ ▲ 15% vs LW  │ ✅ on track  │ ▲ 3pt vs LW  │ 🔴 $340K at risk │
├──────────────┴──────────────┴──────────────┴──────────────────┤
│ Bookings Trend (12 weeks) ← primary chart, 60% width          │
│                                                                │
├─────────────────────────────┬──────────────────────────────────┤
│ Revenue by Rep (bar chart)  │ Pipeline Stage Funnel            │
├─────────────────────────────┴──────────────────────────────────┤
│ Deal Table: Name | Stage | Value | Expected Close | Days Late  │
└────────────────────────────────────────────────────────────────┘
```

**Color logic:**
- Green: metric above target
- Red: metric below target or "at risk" items
- Blue: trend line (primary data)
- Grey: prior period comparison line

**Tool recommendation:** Salesforce Einstein Analytics (if using Salesforce CRM) or Tableau with Salesforce connector. For smaller teams, HubSpot built-in reporting or Metabase connected to CRM database.

---

### Example 2: Design an Engineering Metrics Dashboard
**Input:** "Engineering team wants a dashboard to track system health, deployment frequency, and incident response."

**Audience:** Engineering team leads, on-call engineers — daily + real-time use.

**KPI selection (DORA Metrics framework):**
1. **Deployment Frequency** — deploys/week (target: daily)
2. **Lead Time for Changes** — PR merge → production (target: < 1 day)
3. **Change Failure Rate** — % of deploys causing incidents (target: < 5%)
4. **MTTR (Mean Time to Recovery)** — avg incident duration (target: < 1 hour)

**Supporting charts:**
- Error rate by service (last 24h line chart)
- P95 API latency by endpoint (heatmap)
- Open incidents table with severity and SLA status
- Recent deployments log

**Tool recommendation:** Grafana (connects directly to Prometheus, DataDog, or CloudWatch; native alerting; real-time refresh).

**Color coding:** Red = SLA breach, Yellow = degraded, Green = healthy, Grey = no data.

## Best Practices
- Design for the question, not the data—start with "what decision does this enable?" not "what data do I have?"
- One dashboard, one audience—don't try to serve executives and analysts with the same view
- KPIs need targets: a number without a benchmark is meaningless
- "Alert" color (red) loses impact if overused; reserve it for genuine problems
- Show the trend, not just the snapshot—a current value without history lacks context
- Label data directly on charts when possible rather than relying on legend lookups
- Build the mobile version after the desktop version, not as an afterthought

## Common Mistakes
- Too many KPIs: 20+ metrics creates analysis paralysis, not insight
- Vanity metrics: page views, social followers, total registered users (not actionable)
- Missing comparison context: showing $1.2M revenue without target or prior period
- Inconsistent date filters: one chart shows "last 30 days" while another shows "this month"
- Using pie charts for more than 5 segments—switch to a ranked bar chart
- Auto-refreshing a dashboard that users need to study calmly—adds cognitive load
- Forgetting mobile: 40%+ of dashboard views happen on tablets or phones

## Tips & Tricks
- Run a "5-second test": show the dashboard to someone for 5 seconds, then ask "what's the most important thing?"—if they can't answer, the hierarchy isn't clear
- Use grey as your default color for all secondary data; use color only to highlight what matters
- Always include a "last updated" timestamp so users know if data is stale
- Dashboard titles should answer the question the dashboard addresses: "Sales Performance — Week of Jan 15" not "Sales Dashboard"
- For executive dashboards, start with a written "dashboard narrative" document before building—executives often want a briefing, not a tool to explore

## Related Skills
- [chart-builder](../../data/chart-builder/SKILL.md)
- [sql-analyst](../../data/sql-analyst/SKILL.md)
- [data-analyst](../../data/data-analyst/SKILL.md)
- [business-analyst](../../business/business-analyst/SKILL.md)

© community · MIT · NickCrew/Claude-Cortex

Похожие скиллы

Все скиллы по теме «Дизайн» →
build-exec-dashboard gtmagents Команда build-exec-dashboard собирает спецификацию дашборда с KPI для топов: раскладка, запросы, фильтры, источники и план внедрения. CX Codex +1 ★ 450звёзд репо chart-designer claude-office-skills Скилл chart-designer для Claude Code: разбирает данные, подбирает тип диаграммы и отдаёт готовый конфиг для ECharts или Chart.js. Закрывает сборку дашборда и отчёта без ручной рисовки графиков. CX Codex +1 6 100установок youtube-channel-analytics-dashboard reason-machines Скилл youtube-channel-analytics-dashboard для Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI и OpenCode, который следит за метриками YouTube-канала через дашборд. CX Codex +1 613установок kpi-dashboard-design aj-geddes Скилл kpi-dashboard-design для Claude Code, Cursor и других ИИ-редакторов: проектирует дашборды с ключевыми метриками. Выбирает показатели под бизнес-цели, строит визуализации и настраивает мониторинг. CX Codex +1 531установок executive-dashboard-generator OneWave-AI Скилл executive-dashboard-generator превращает CSV, Google Sheets и выгрузки из баз в отчёт для руководства: метрики, графики, тренды и рекомендации. CX Codex +1 431установок build-dashboard официальный Data Analytics Maintainers Скилл build-dashboard для Codex и ChatGPT, который строит дашборды с подключёнными источниками данных — для мониторинга метрик, операционных обзоров или аналитических исследований. CX Codex GP ChatGPT +1 8установок

Из того же набора21

Весь набор →
security-testing-patterns Скилл security-testing-patterns задаёт правила тестирования безопасности: от SAST и SCA до фаззинга, DAST и аудита API по OWASP. Помогает выстроить CI/CD пайплайн и разобрать уязвимости. CX Codex +1 154установок secure-coding-practices Скилл secure-coding-practices для Claude Code помогает применять защитные практики при работе с авторизацией, пользовательским вводом и чувствительными данными. Подключается и для проверки кода на уязвимости. CX Codex +1 134установок ux-review Скилл ux-review проверяет компонент или поток с трёх сторон: удобство, доступность по WCAG 2.1 AA и поведение интерфейса. Отдаёт отчёт с находками по приоритетам. CX Codex +1 119установок event-driven-architecture Скилл event-driven-architecture для Claude Code помогает проектировать системы на событиях: event sourcing, CQRS, саги и обмен сообщениями. Охватывает микросервисы и распределённые транзакции. CX Codex +1 118установок terraform-best-practices Скилл terraform-best-practices внедряет инженерные стандарты Terraform: разбиение на модули, блокировку стейта, разделение сред и валидацию в CI/CD. CX Codex +1 109установок mermaid-diagramming Скилл mermaid-diagramming учит агента рисовать диаграммы Mermaid: блок-схемы, sequence-диаграммы, ERD, состояния, Gantt и архитектурные виды, отдельно базовую и стилизованную версию. CX Codex +1 105установок kubernetes-security-policies Скилл kubernetes-security-policies для Claude Code помогает настроить Pod Security Standards, сетевые политики и RBAC в Kubernetes. Ужесточает защиту прод-окружения. CX Codex +1 104установок user-journey-mapping Скилл user-journey-mapping для Claude Code помогает составить карту пути пользователя с этапами, точками контакта, эмоциями и проблемами. Запускается при анализе пользовательского опыта или конверсии. CX Codex +1 102установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой