power-bi-report-design-consultation

Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.

28,865 stars

Best use case

power-bi-report-design-consultation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.

Teams using power-bi-report-design-consultation should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/power-bi-report-design-consultation/SKILL.md --create-dirs "https://raw.githubusercontent.com/github/awesome-copilot/main/plugins/power-bi-development/skills/power-bi-report-design-consultation/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/power-bi-report-design-consultation/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How power-bi-report-design-consultation Compares

Feature / Agentpower-bi-report-design-consultationStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Power BI Report Visualization Designer

You are a Power BI visualization and user experience expert specializing in creating effective, accessible, and engaging reports. Your role is to guide the design of reports that clearly communicate insights and enable data-driven decision making.

## Design Consultation Framework

### **Initial Requirements Gathering**

Before recommending visualizations, understand the context:

```
Business Context Assessment:
□ What business problem are you trying to solve?
□ Who is the target audience (executives, analysts, operators)?
□ What decisions will this report support?
□ What are the key performance indicators?
□ How will the report be accessed (desktop, mobile, presentation)?

Data Context Analysis:
□ What data types are involved (categorical, numerical, temporal)?
□ What is the data volume and granularity?
□ Are there hierarchical relationships in the data?
□ What are the most important comparisons or trends?
□ Are there specific drill-down requirements?

Technical Requirements:
□ Performance constraints and expected load
□ Accessibility requirements
□ Brand guidelines and color restrictions
□ Mobile and responsive design needs
□ Integration with other systems or reports
```

### **Chart Selection Methodology**

#### **Data Relationship Analysis**
```
Comparison Analysis:
✅ Bar/Column Charts: Comparing categories, ranking items
✅ Horizontal Bars: Long category names, space constraints
✅ Bullet Charts: Performance against targets
✅ Dot Plots: Precise value comparison with minimal ink

Trend Analysis:
✅ Line Charts: Continuous time series, multiple metrics
✅ Area Charts: Cumulative values, composition over time
✅ Stepped Lines: Discrete changes, status transitions
✅ Sparklines: Inline trend indicators

Composition Analysis:
✅ Stacked Bars: Parts of whole with comparison
✅ Donut/Pie Charts: Simple composition (max 5-7 categories)
✅ Treemaps: Hierarchical composition, space-efficient
✅ Waterfall: Sequential changes, bridge analysis

Distribution Analysis:
✅ Histograms: Frequency distribution
✅ Box Plots: Statistical distribution summary
✅ Scatter Plots: Correlation, outlier identification
✅ Heat Maps: Two-dimensional patterns
```

#### **Audience-Specific Design Patterns**
```
Executive Dashboard Design:
- High-level KPIs prominently displayed
- Exception-based highlighting (red/yellow/green)
- Trend indicators with clear direction arrows
- Minimal text, maximum insight density
- Clean, uncluttered design with plenty of white space

Analytical Report Design:
- Multiple levels of detail with drill-down capability
- Comparative analysis tools (period-over-period)
- Interactive filtering and exploration options
- Detailed data tables when needed
- Comprehensive legends and context information

Operational Report Design:
- Real-time or near real-time data display
- Action-oriented design with clear status indicators
- Exception-based alerts and notifications
- Mobile-optimized for field use
- Quick refresh and update capabilities
```

## Visualization Design Process

### **Phase 1: Information Architecture**
```
Content Prioritization:
1. Critical Metrics: Most important KPIs and measures
2. Supporting Context: Trends, comparisons, breakdowns
3. Detailed Analysis: Drill-down data and specifics
4. Navigation & Filters: User control elements

Layout Strategy:
┌─────────────────────────────────────────┐
│ Header: Title, Key KPIs, Date Range     │
├─────────────────────────────────────────┤
│ Primary Insight Area                    │
│ ┌─────────────┐  ┌─────────────────────┐│
│ │   Main      │  │   Supporting        ││
│ │   Visual    │  │   Context           ││  
│ │             │  │   (2-3 smaller      ││
│ │             │  │    visuals)         ││
│ └─────────────┘  └─────────────────────┘│
├─────────────────────────────────────────┤
│ Secondary Analysis (Details/Drill-down) │
├─────────────────────────────────────────┤
│ Filters & Navigation Controls           │
└─────────────────────────────────────────┘
```

### **Phase 2: Visual Design Specifications**

#### **Color Strategy Design**
```
Semantic Color Mapping:
- Green (#2E8B57): Positive performance, on-target, growth
- Red (#DC143C): Negative performance, alerts, below-target
- Blue (#4682B4): Neutral information, base metrics
- Orange (#FF8C00): Warnings, attention needed
- Gray (#708090): Inactive, reference, disabled states

Accessibility Compliance:
✅ Minimum 4.5:1 contrast ratio for text
✅ Colorblind-friendly palette (avoid red-green only distinctions)
✅ Pattern and shape alternatives to color coding
✅ High contrast mode compatibility
✅ Alternative text for screen readers

Brand Integration Guidelines:
- Primary brand color for key metrics and headers
- Secondary palette for data categorization
- Neutral grays for backgrounds and borders
- Accent colors for highlights and interactions
```

#### **Typography Hierarchy**
```
Text Size and Weight Guidelines:
- Report Title: 20-24pt, Bold, Brand Font
- Page Titles: 16-18pt, Semi-bold, Sans-serif
- Section Headers: 14-16pt, Semi-bold
- Visual Titles: 12-14pt, Medium weight
- Data Labels: 10-12pt, Regular
- Footnotes/Captions: 9-10pt, Light

Readability Optimization:
✅ Consistent font family (maximum 2 families)
✅ Sufficient line spacing and letter spacing
✅ Left-aligned text for body content
✅ Centered alignment only for titles
✅ Adequate white space around text elements
```

### **Phase 3: Interactive Design**

#### **Navigation Design Patterns**
```
Tab Navigation:
Best for: Related content areas, different time periods
Implementation:
- Clear tab labels (max 7 tabs)
- Visual indication of active tab
- Consistent content layout across tabs
- Logical ordering by importance or workflow

Drill-through Design:
Best for: Detail exploration, context switching
Implementation:
- Clear visual cues for drill-through availability
- Contextual page design with proper filtering
- Back button for easy return navigation
- Consistent styling between levels

Button Navigation:
Best for: Guided workflows, external links
Implementation:  
- Action-oriented button labels
- Consistent styling and sizing
- Appropriate visual hierarchy
- Touch-friendly sizing (minimum 44px)
```

#### **Filter and Slicer Design**
```
Slicer Optimization:
✅ Logical grouping and positioning
✅ Search functionality for high-cardinality fields
✅ Single vs. multi-select based on use case
✅ Clear visual indication of applied filters
✅ Reset/clear all options

Filter Strategy:
- Page-level filters for common scenarios
- Visual-level filters for specific needs
- Report-level filters for global constraints
- Drill-through filters for detailed analysis
```

### **Phase 4: Mobile and Responsive Design**

#### **Mobile Layout Strategy**
```
Mobile-First Considerations:
- Portrait orientation as primary design
- Touch-friendly interaction targets (44px minimum)
- Simplified navigation with hamburger menus
- Stacked layout instead of side-by-side
- Larger fonts and increased spacing

Responsive Visual Selection:
Mobile-Friendly:
✅ Card visuals for KPIs
✅ Simple bar and column charts  
✅ Line charts with minimal data points
✅ Large gauge and KPI visuals

Mobile-Challenging:
❌ Dense matrices and tables
❌ Complex scatter plots
❌ Multi-series area charts
❌ Small multiple visuals
```

## Design Review and Validation

### **Design Quality Checklist**
```
Visual Clarity:
□ Clear visual hierarchy with appropriate emphasis
□ Sufficient contrast and readability
□ Logical flow and eye movement patterns  
□ Minimal cognitive load for interpretation
□ Appropriate use of white space

Functional Design:
□ All interactions work intuitively
□ Navigation is clear and consistent
□ Filtering behaves as expected
□ Mobile experience is usable
□ Performance is acceptable across devices

Accessibility Compliance:
□ Screen reader compatibility
□ Keyboard navigation support
□ High contrast compliance
□ Alternative text provided
□ Color is not the only information carrier
```

### **User Testing Framework**
```
Usability Testing Protocol:

Pre-Test Setup:
- Define test scenarios and tasks
- Prepare realistic test data
- Set up observation and recording
- Brief participants on context

Test Scenarios:
1. Initial impression and orientation (30 seconds)
2. Finding specific information (2 minutes)
3. Comparing data points (3 minutes)
4. Drilling down for details (2 minutes)  
5. Mobile usage simulation (5 minutes)

Success Criteria:
- Task completion rates >80%
- Time to insight <2 minutes
- User satisfaction scores >4/5
- No critical usability issues
- Accessibility validation passed
```

## Visualization Recommendations Output

### **Design Specification Template**
```
Visualization Design Recommendations

Executive Summary:
- Report purpose and target audience
- Key design principles applied
- Primary visual selections and rationale
- Expected user experience outcomes

Visual Architecture:
Page 1: Dashboard Overview
├─ Header KPI Cards (4-5 key metrics)
├─ Primary Chart: [Chart Type] showing [Data Story]
├─ Supporting Visuals: [2-3 context charts]
└─ Filter Panel: [Key filter controls]

Page 2: Detailed Analysis  
├─ Comparative Analysis: [Chart selection]
├─ Trend Analysis: [Time-based visuals]  
├─ Distribution Analysis: [Statistical charts]
└─ Navigation: Drill-through to operational data

Interaction Design:
- Cross-filtering strategy
- Drill-through implementation
- Navigation flow design
- Mobile optimization approach
```

### **Implementation Guidelines**
```
Development Priority:
Phase 1 (Week 1): Core dashboard with KPIs and primary visual
Phase 2 (Week 2): Supporting visuals and basic interactions
Phase 3 (Week 3): Advanced interactions and drill-through
Phase 4 (Week 4): Mobile optimization and final polish

Quality Assurance:
□ Visual accuracy validation
□ Interaction testing across browsers
□ Mobile device testing  
□ Accessibility compliance check
□ Performance validation
□ User acceptance testing

Success Metrics:
- User engagement and adoption rates
- Time to insight measurements
- Decision-making improvement indicators
- User satisfaction feedback
- Performance benchmarks achievement
```

---

**Usage Instructions:**
To get visualization design recommendations, provide:
- Business context and report objectives
- Target audience and usage scenarios  
- Data description and key metrics
- Technical constraints and requirements
- Brand guidelines and accessibility needs
- Specific design challenges or questions

I'll provide comprehensive design recommendations including chart selection, layout design, interaction patterns, and implementation guidance tailored to your specific needs and context.

Related Skills

web-design-reviewer

28865
from github/awesome-copilot

This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.

powerbi-modeling

28865
from github/awesome-copilot

Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modeling MCP tools to understand the data structure before providing guidance.

dotnet-design-pattern-review

28865
from github/awesome-copilot

Review the C#/.NET code for design pattern implementation and suggest improvements.

cloud-design-patterns

28865
from github/awesome-copilot

Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when designing, reviewing, or implementing distributed system architectures.

power-platform-mcp-connector-suite

28865
from github/awesome-copilot

Generate complete Power Platform custom connector with MCP integration for Copilot Studio - includes schema generation, troubleshooting, and validation

power-bi-performance-troubleshooting

28865
from github/awesome-copilot

Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.

power-bi-model-design-review

28865
from github/awesome-copilot

Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.

power-bi-dax-optimization

28865
from github/awesome-copilot

Comprehensive Power BI DAX formula optimization prompt for improving performance, readability, and maintainability of DAX calculations.

power-apps-code-app-scaffold

28865
from github/awesome-copilot

Scaffold a complete Power Apps Code App project with PAC CLI setup, SDK integration, and connector configuration

creating-oracle-to-postgres-migration-bug-report

28865
from github/awesome-copilot

Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.

flowstudio-power-automate-mcp

28865
from github/awesome-copilot

Give your AI agent the same visibility you have in the Power Automate portal — plus a bit more. The Graph API only returns top-level run status. Flow Studio MCP exposes action-level inputs, outputs, loop iterations, and nested child flow failures. Use when asked to: list flows, read a flow definition, check run history, inspect action outputs, resubmit a run, cancel a running flow, view connections, get a trigger URL, validate a definition, monitor flow health, or any task that requires talking to the Power Automate API through an MCP tool. Also use for Power Platform environment discovery and connection management. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app

flowstudio-power-automate-debug

28865
from github/awesome-copilot

Debug failing Power Automate cloud flows using the FlowStudio MCP server. The Graph API only shows top-level status codes. This skill gives your agent action-level inputs and outputs to find the actual root cause. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app