power-bi-report-design-consultationby GitHub

Power BI Report Design Consultation Skill.

A Claude Code and Codex skill for diagrams and charts: power BI report design: chart selection, layout, readability, accessibility.

Diagrams & Data Visualization
Dashboard

Download OpenDesign View usage guide

github/awesome-copilot · skills/power-bi-report-design-consultation/SKILL.mdSKILL.md

--- name: power-bi-report-design-consultation description: Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design. --- ## Design Consultation Framework ## Visualization Design Process ## Design Review and Validation ## Visualization Recommendations Output

Front matter and section headings read from the upstream file on 2026-09-14 · 10,891 characters in full

01 What it does

What the power-bi-report-design-consultation Skill Does in Claude Code and Codex

Summary, workflow and outputs, all read from the skill's SKILL.md.

From the SKILL.mdRead 2026-09-14 · not a recorded run

In the Skill's Own Terms

A design consultation prompt for Power BI reports: it walks through requirements gathering, chart selection, layout, color, typography, interaction and mobile design before producing a written specification. The audience is anyone who already has data and needs to decide how to present it — executives, analysts and operators are the three audiences the file names.

What makes it specific is the vocabulary it fixes: bullet charts for targets, waterfall for bridge analysis, stepped lines for status transitions, a 4.5:1 contrast minimum, a seven-tab ceiling and 44px touch targets. It ends with a page-by-page design template and a four-week delivery plan rather than code.

What it produces

A written visualization design recommendation covering purpose, audience, design principles and the rationale behind each primary visual choice.
A page-by-page visual architecture, starting with a dashboard overview page holding header KPI cards, a primary chart, supporting visuals and a filter panel.
An interaction design section specifying cross-filtering, drill-through, navigation flow and the mobile optimization approach.
A four-phase implementation plan ending in mobile optimization and final polish.

See the example prompt ↗

How It Works

01
Gather Context Before Recommending Anything
The framework opens with a checklist covering business context, data context and technical requirements, so chart advice is grounded in the problem, audience, decisions and data types first.
02
Match Chart Type to the Data Relationship
Charts are grouped by the analytical job they do — comparison, trend, composition, distribution — and each group lists the chart types that fit.
03
Pick a Design Pattern for the Audience
Executive, analytical and operational reports each get their own rules for density, interactivity and refresh behavior, so the same data is presented differently depending on who reads it.
04
Order Content into an Information Architecture
Content is prioritized into critical metrics, supporting context, detailed analysis, with navigation and filters last, then placed into a header plus primary insight plus secondary analysis layout.
05
Validate with Review and User Testing
A quality checklist and a five-scenario usability protocol with timed tasks and numeric success criteria close the process before deliverables are handed over.
06
Package the Output as a Spec and Phased Plan
Recommendations are written up as a design specification with visual architecture per page, interaction design, and a four-week development priority list.

02 Find your fit

When to Use the power-bi-report-design-consultation Skill

Use the power-bi-report-design-consultation skill in Claude Code or Codex when the job is diagrams and charts of this kind. Fit and limits below are taken from the skill's own file.

Good Fit

Analytical reports that need multiple levels of detail with drill-down capability and period-over-period comparison.
Operational reports read in the field, where the design must be mobile-optimized and status-driven.
Accessibility-driven work, including screen reader support and alternative text.

Know the Boundaries

Putting dense matrices, complex scatter plots, multi-series area charts or small multiples on a mobile layout — the file lists these as mobile-challenging.
Encoding meaning through red-versus-green distinctions alone; the palette must be colorblind-friendly.

What to Provide

Business context and report objectivesThe skill asks for the business problem, the decisions the report supports and the key performance indicators before it will recommend visuals.
Target audience and usage scenariosWho reads it and how it is accessed matters, since executive, analytical and operational patterns differ and desktop, mobile and presentation access change the layout.
Data description and key metricsData types, volume, granularity, hierarchies and the comparisons or trends that matter drive the chart selection step.
Technical constraints and requirementsPerformance constraints, expected load, mobile needs and integration with other reports all feed the technical requirements checklist.
Brand guidelines and accessibility needsBrand colors and color restrictions set the palette, and accessibility needs set the contrast and non-color-coding requirements.

03 Inside the skill

Rules the power-bi-report-design-consultation Skill Gives Claude Code and Codex

8 concrete instructions, defaults and limits the SKILL.md sets for the agent — the part of the file that changes the result.

Hold Text Contrast to at Least 4.5:1
Any recommendation must clear a minimum 4.5:1 contrast ratio for text, along with high contrast mode compatibility and alternative text for screen readers.
Cap Pie and Donut Charts at 5-7 Categories
Pie and donut charts are reserved for simple composition only; the file puts a hard category ceiling of 5 to 7 slices on them.
Use at Most Two Font Families
Typography stays consistent: a maximum of two font families across the report, with size and weight bands given per element from 20-24pt report title down to 9-10pt footnotes.
Size Touch Targets at 44px Minimum
Both button navigation and mobile layout must respect a minimum 44px interaction target for touch.
Keep Tab Navigation to Seven Tabs
Tab navigation is for related content areas and time periods, with clear labels capped at a maximum of seven tabs and an obvious active state.
Never Carry Meaning by Color Alone
Accessibility compliance requires that color is not the only information carrier, with pattern and shape alternatives to color coding.
Avoid Dense Matrices and Tables on Mobile
Mobile-challenging visuals are excluded from mobile layouts; on mobile the file steers toward card visuals, simple bars, lines with few data points, and large KPI or gauge visuals.
Apply Fixed Semantic Colors
Color carries assigned meaning: green #2E8B57 for positive or on-target performance, red #DC143C for negative or below-target, blue #4682B4 for neutral base metrics, orange #FF8C00 for warnings and gray #708090 for inactive states.

04 Put it to work

Install power-bi-report-design-consultation in Claude Code or Codex

One npx skills add command, then a first task in your agent and a checklist for the result.

Add power-bi-report-design-consultation to Claude Code, Codex or Your Agent

Run in your project; the installer asks which agent to add it to.

Terminal

npx skills add https://github.com/github/awesome-copilot --skill power-bi-report-design-consultation

Generic skills CLI form for skills/power-bi-report-design-consultation/SKILL.md; the repository may document its own path.

Give the Skill a First Diagrams and Charts Task

Written in the skill's own terms; replace the bracketed parts with your material.

Starter prompt

We need a quarterly sales dashboard in Power BI for our leadership team. The audience is executives, mostly viewed on desktop but also on mobile during meetings, and it has to meet our accessibility guidelines. The data is order-level with region, a product hierarchy, and monthly revenue against target. Recommend the chart type for each KPI, give us a page-by-page layout, and flag anything that will break on mobile.

Source: written from the SKILL.md in the skill's own terms.

Check the First Result

What the SKILL.md itself says a correct result looks like:

Run the visual clarity checklist: hierarchy, contrast and readability, logical eye flow, low cognitive load and appropriate white space.
Confirm accessibility compliance across screen reader compatibility, keyboard navigation, high contrast mode, alt text and color independence.
Test with the five timed scenarios, including orientation in 30 seconds, finding specific information in 2 minutes and mobile simulation in 5 minutes.
Measure against the success criteria: task completion above 80%, time to insight under 2 minutes and satisfaction above 4 out of 5.
Run quality assurance: visual accuracy, interaction testing across browsers, mobile device testing and user acceptance testing.

In OpenDesign import power-bi-report-design-consultation from its SKILL.md link: Plugins → Add → Skill → Import from link, then pick it in the top bar.

Download OpenDesign Read the quickstart

05 Open source, traceable

Source, License and Verification

Where this page's facts come from, and when they were last checked.

Author: GitHub
Repository: github.com/github/awesome-copilot Branch main
Skill file: skills/power-bi-report-design-consultation/SKILL.md Content checksum recorded at verification; commit 1899b18
License: MIT From LICENSE.
Repository stars: 38,981 GitHub snapshot taken 2026-09-14 for the whole github/awesome-copilot repository, which contains 6 skills in this catalog. Not a rating or usage count for power-bi-report-design-consultation.
Verified by OpenDesign: 2026-09-14 Source file, path, license text and star count were checked. Not bundled in OpenDesign main (checked 2026-08-28); a live run has not been recorded on this page.

Inside the SKILL.md

Design Consultation FrameworkChecklists for business, data and technical requirements to complete before advising.
Chart Selection MethodologyChart types grouped by comparison, trend, composition and distribution analysis, plus audience design patterns.
Phase 1: Information ArchitecturePrioritize critical metrics down to filters, then place them in a header-and-insight layout.
Phase 2: Visual Design SpecificationsSemantic color mapping, accessibility and brand rules, and a typography size and weight scale.
Phase 3: Interactive DesignTab, drill-through and button navigation patterns plus slicer and filter strategy.
Phase 4: Mobile and Responsive DesignMobile-first layout considerations and which visuals are mobile-friendly versus challenging.
Design Quality ChecklistVisual clarity, functional design and accessibility items to tick off before shipping.
User Testing FrameworkFive timed test scenarios with numeric success criteria for completion, insight time and satisfaction.
Design Specification TemplateThe write-up format: executive summary, page-by-page visual architecture and interaction design.
Implementation GuidelinesFour-week development priority, QA checklist and success metrics such as adoption and time to insight.

The Skill's Own Description

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

Front-matter description from SKILL.md. The full file is about 10,891 characters. Read the full file on GitHub.

06 Before you install

Questions About the power-bi-report-design-consultation Skill

Answers come from the SKILL.md as read on 2026-09-14, not from a recorded run.

Is this tied to Power BI specifically, or can I use it for another tool?

It is framed as a Power BI report visualization design prompt, so the vocabulary, visuals and interaction patterns are Power BI's. No other BI tool or integration is named in the file.

Power BI Report Design Consultation

Run power-bi-report-design-consultation on a Real Diagrams and Charts Task.

Download OpenDesign, import power-bi-report-design-consultation from its SKILL.md link, paste the prompt above, and read the plan before the result.

Download OpenDesign Browse all skills

Terminal

npx skills add https://github.com/github/awesome-copilot --skill power-bi-report-design-consultation

What the power-bi-report-design-consultation Skill Does in Claude Code and Codex

In the Skill's Own Terms

How It Works

When to Use the power-bi-report-design-consultation Skill

Good Fit

Know the Boundaries

What to Provide

Rules the power-bi-report-design-consultation Skill Gives Claude Code and Codex

Hold Text Contrast to at Least 4.5:1

Cap Pie and Donut Charts at 5-7 Categories

Use at Most Two Font Families

Size Touch Targets at 44px Minimum

Keep Tab Navigation to Seven Tabs

Never Carry Meaning by Color Alone

Avoid Dense Matrices and Tables on Mobile

Apply Fixed Semantic Colors