Power-Bi-Report-Design-Best-Practices
Power-Bi-Report-Design-Best-Practices是一款design方向的AI技能,核心价值是Comprehensive Power BI report design and visualization best practices based on Microsoft guidance for creating effective, accessible, and performant reports and dashboards,可用于解决开发者在design领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。
Comprehensive Power BI report design and visualization best practices based on Microsoft guidance for creating effective, accessible, and performant reports and dashboards.
mkdir -p ./skills/power-bi-report-design-best-practices && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/power-bi-report-design-best-practices/SKILL.md -o ./skills/power-bi-report-design-best-practices/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# Power BI Report Design and Visualization Best Practices
Overview
This document provides comprehensive instructions for designing effective, accessible, and performant Power BI reports and dashboards following Microsoft's official guidance and user experience best practices.
Fundamental Design Principles
1. Information Architecture
**Visual Hierarchy** - Organize information by importance:
- **Primary**: Key metrics, KPIs, most critical insights (top-left, header area)
- **Secondary**: Supporting details, trends, comparisons (main body)
- **Tertiary**: Filters, controls, navigation elements (sidebars, footers)
**Content Structure**:
Report Page Layout:
┌─────────────────────────────────────┐
│ Header: Title, KPIs, Key Metrics │
├─────────────────────────────────────┤
│ Main Content Area │
│ ┌─────────────┐ ┌─────────────────┐ │
│ │ Primary │ │ Supporting │ │
│ │ Visual │ │ Visuals │ │
│ └─────────────┘ └─────────────────┘ │
├─────────────────────────────────────┤
│ Footer: Filters, Navigation, Notes │
└─────────────────────────────────────┘2. User Experience Principles
**Clarity**: Every element should have a clear purpose and meaning
**Consistency**: Use consistent styling, colors, and interactions across all reports
**Context**: Provide sufficient context for users to interpret data correctly
**Action**: Guide users toward actionable insights and decisions
Chart Type Selection Guidelines
1. Comparison Visualizations
Bar/Column Charts:
✅ Comparing categories or entities
✅ Ranking items by value
✅ Showing changes over discrete time periods
✅ When category names are long (use horizontal bars)
Best Practices:
- Start axis at zero for accurate comparison
- Sort categories by value for ranking
- Use consistent colors within category groups
- Limit to 7-10 categories for readability
Example Use Cases:
- Sales by product category
- Revenue by region
- Employee count by department
- Customer satisfaction by service typeLine Charts:
✅ Showing trends over continuous time periods
✅ Comparing multiple metrics over time
✅ Identifying patterns, seasonality, cycles
✅ Forecasting and projection scenarios
Best Practices:
- Use consistent time intervals
- Start Y-axis at zero when showing absolute values
- Use different line styles for multiple series
- Include data point markers for sparse data
Example Use Cases:
- Monthly sales trends
- Website traffic over time
- Stock price movements
- Performance metrics tracking2. Composition Visualizations
Pie/Donut Charts:
✅ Parts-of-whole relationships
✅ Maximum 5-7 categories
✅ When percentages are more important than absolute values
✅ Simple composition scenarios
Limitations:
❌ Difficult to compare similar-sized segments
❌ Not suitable for many categories
❌ Hard to show changes over time
Alternative: Use stacked bar charts for better readability
Example Use Cases:
- Market share by competitor
- Budget allocation by category
- Customer segments by typeStacked Charts:
✅ Showing composition and total simultaneously
✅ Comparing composition across categories
✅ Multiple sub-categories within main categories
✅ When you need both part and whole perspective
Types:
- 100% Stacked: Focus on proportions
- Regular Stacked: Show both absolute and relative values
- Clustered: Compare sub-categories side-by-side
Example Use Cases:
- Sales by product category and region
- Revenue breakdown by service type over time
- Employee distribution by department and level3. Relationship and Distribution Visualizations
Scatter Plots:
✅ Correlation between two continuous variables
✅ Outlier identification
✅ Clustering analysis
✅ Performance quadrant analysis
Best Practices:
- Use size for third dimension (bubble chart)
- Apply color coding for categories
- Include trend lines when appropriate
- Label outliers and key points
Example Use Cases:
- Sales vs. marketing spend by product
- 🎯 Best For
- UI designers
- Product designers
- Claude users
- GitHub Copilot users
- Designers
💡 Use Cases
- Generating component mockups
- Creating design system tokens
- Design system documentation
- Component specification creation
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Power-Bi-Report-Design-Best-Practices to Your Work
Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.
- 4
Review and Refine
Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.
❓ Frequently Asked Questions
Does this work with Figma?
Some design skills integrate with Figma plugins. Check the Works With section for supported tools.
Does Power-Bi-Report-Design-Best-Practices generate production-ready design specs?
It generates detailed specifications that developers can use directly. Review and adjust for your specific design system.
How do I install Power-Bi-Report-Design-Best-Practices?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/power-bi-report-design-best-practices/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping usability testing
AI-generated designs should be validated with real users before development.
Not reading the full skill
Skills contain important context and edge cases beyond the quick start.