Dashboard Design Spec
Defining the key questions the dashboard must answer at a glance prevents scope creep and ensures every widget earns its space. Specifying the audience expertise level calibrates complexity.
Design a dashboard for {{dashboard_purpose}} used by {{target_users}}. Data sources available: {{data_sources}} Key metrics to track: {{key_metrics}} Update frequency: {{update_frequency}} Tool: {{dashboard_tool}} Provide: 1. Dashboard layout (which charts go where, with wireframe description) 2. For each chart/widget: - Metric shown - Chart type and why - Filters or drill-down capability needed - Thresholds or conditional formatting rules 3. Global filters (date range, {{filter_dimensions}}) 4. A "north star" KPI that should be the most prominent element 5. Mobile considerations if applicable Design for a {{expertise_level}} audience — choose complexity accordingly. The dashboard should answer these questions at a glance: {{key_questions}}
Variables to customize
Why this prompt works
Defining the key questions the dashboard must answer at a glance prevents scope creep and ensures every widget earns its space. Specifying the audience expertise level calibrates complexity.
What you get when you save this prompt
Your workspace unlocks powerful tools to iterate and improve.
AI Optimization
One-click improvement with structure analysis and pattern suggestions.
Version History
Track every edit. Compare versions side-by-side with word-level diffs.
Folders & Tags
Organize your library with nested folders, tags, and drag-and-drop.
$ npm i -g @promptingbox/mcpUse Everywhere
Access prompts from Claude, Cursor, ChatGPT & more via MCP integration.
Your prompts, organized
Save, version, and access your best prompts across ChatGPT, Claude, Cursor, and more.