design-dashboards

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: design-dashboards
description: User-invoked dashboard critique, concept, redesign, spec, and grill workflow.
disable-model-invocation: true
---

# Design Dashboards

Use this skill to critique, design, redesign, or specify dashboards as working instruments for decisions, not presentation graphics.

Open `references/dashboard-design-principles.md` before any critique, redesign, operational dashboard work, best-practice review, or spec where dashboard judgment matters. It is optional only for straightforward concept sketches that do not require chart, layout, Gestalt, perception, interaction, or visual-encoding reasoning.

## Mode Selection

Choose the narrowest mode that fits the user's request.

If the request involves an operational, real-time, monitoring, queue, incident-response, or other response-oriented dashboard, first choose the normal mode by task, then also apply the Operational Dashboard workflow:

- existing operational dashboard critique: Mode 1 plus Operational Dashboard
- new real-time or operations dashboard: Mode 2 plus Operational Dashboard
- existing operations dashboard redesign: Mode 3 plus Operational Dashboard
- operational dashboard spec: Mode 4 plus Operational Dashboard

### Mode 1: Dashboard Critique And Polish

Use by default when the user provides an existing dashboard, screenshot, wireframe, chart set, or asks whether a dashboard follows best practices. Give quick wins, visual-design misses, Gestalt assessment, strategic concerns, and logical gaps. Do not over-redesign.

Preserve:

- dashboard purpose unless it is clearly broken
- current information architecture where possible
- existing KPIs unless a KPI is visibly misleading
- product constraints and visual language

Focus on purpose, dashboard role, KPI validity, comparison context, chart/layout fit, visual emphasis, interaction behavior, and strategic gaps.

Return:

- **Verdict**
- **What works**
- **Severity-ranked issues**
- **Gestalt assessment**
- **Chart/KPI fixes**
- **Layout, color, and interaction polish**
- **Strategic concerns**
- **What context would change this**
- **Suggested next step**

Use three severity levels:

- **High**: blocks or misleads the dashboard's decision
- **Medium**: slows comprehension or weakens comparison
- **Low**: polish, consistency, or efficiency issue

Done when every major KPI, chart, layout group, color/emphasis pattern, interaction surface, and dashboard-role mismatch has been classified as keep, fix, replace, or out of scope. If the dashboard goal/spec is missing, state assumptions and warn that strategic critique is provisional. The **Suggested next step** must name the Dashboard Spec Grill and give the exact trigger phrase: "Run Dashboard Spec Grill."

### Mode 2: New Dashboard Concept

Use when the user starts from a business problem, requirements, metrics, or a blank slate.

Return 1-3 concepts. When uncertainty is high, give two contrasting concepts: one optimized for monitoring clarity and one optimized for deeper analysis.

For each concept, include:

- **Concept**
- **Best for**
- **Main story**
- **Audience**
- **Key questions answered**
- **Layout**
- **Visuals**
- **Context shown**
- **Color/emphasis**
- **Tradeoffs**
- **What to avoid**

Done when the concept identifies the audience, primary decision, cadence, dashboard role, KPI model, required comparison context, layout zones, visual choices, drill-down/alert behavior, and what stays off the overview. If those inputs are missing and materially affect the concept, ask one clarifying question or run the Dashboard Spec Grill.

### Mode 3: Existing Dashboard Redesign

Use when the user has an existing dashboard but wants to revisit the concept, KPI model, decision flow, or overall structure. Triggers include redesign, rethink, does this dashboard answer the right question, improve the dashboard strategy, rebuild this dashboard, or make this dashboard more useful.

Assess the current dashboard as an input, not as a constraint. Ide