powerbi-report-design

Generate Power BI report visual design guidance and design contracts before PBIR authoring.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill powerbi-report-design-9vantage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: powerbi-report-design
Source: https://github.com/9vantage/skills-for-fabric-clone/tree/main/plugins/powerbi-authoring/skills/powerbi-report-design
Command: npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill powerbi-report-design-9vantage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Power BI reports often end up with generic layouts, wrong chart types, poor color choices, and accessibility failures because design decisions are made ad hoc during file authoring. This Skill separates design from implementation by producing a concrete, validated design contract before any PBIR files are written. ## Core Features & Use Cases - Design Identity & Archetype Routing: Commits a tone and signature for the report, then routes each page to one of five archetypes (Executive Summary, Operational Monitor, Analytical Canvas, Narrative Story, Comparative Benchmark) with layout variants selected from data signals. - Chart, Layout, Color, and Theme Guidance: Applies an encoding-accuracy hierarchy for chart selection, an 8px grid layout system, CVD-safe palettes, WCAG contrast rules, and a base theme JSON with per-visual-type safeguards. - Canonical Design Brief Contract: Emits a structured YAML design contract with grid regions, placements, space audits, and color maps that hands off cleanly to the powerbi-report-authoring skill for PBIR implementation. - Use Case: Ask to redesign an existing sales dashboard to match your brand. The Skill screenshots current pages, diagnoses anti-patterns, defines current and target tones, and produces a brownfield redesign brief ready for authoring. ## Quick Start Use the powerbi-report-design skill to design a professional executive summary report from my semantic model and produce a design brief.

Frequently Asked Questions about powerbi-report-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a professional Power BI report layout?

Start by inspecting the semantic model, then commit a tone and signature, route each page to an archetype (Executive, Operational, Analytical, Narrative, or Comparative), and select charts using the encoding-accuracy hierarchy. The Skill emits a design brief with grid regions and placements for authoring.

How to choose the right chart type for Power BI visuals?

Match the chart to the analytical question, not the data type: horizontal bars for comparison, line charts for trends, scatter plots for relationships, and sorted bars for ranking. Respect cardinality limits such as 15 bars maximum and 5 pie slices maximum.

Does this skill write or edit Power BI PBIR files?

No. This skill only decides what the report should look like and why, producing a design contract. All PBIR file mechanics, including page creation, theme registration, and validation, are handed off to the powerbi-report-authoring skill.

Can I redesign or restyle an existing Power BI report?

Yes. Brownfield mode screenshots existing pages, diagnoses them against the anti-patterns catalog and pre-flight checklist, captures current and target tones, and emits a redesign brief listing specific deltas while preserving bookmarks and conditional formatting logic.

What accessibility standards does the report design follow?

Designs follow WCAG 2.1/2.2 with 4.5:1 body text contrast, 3:1 non-text contrast, insight-driven alt text on every visual, keyboard-navigable tab order, 24x24px minimum touch targets, and color vision deficiency safe palettes such as Okabe-Ito.

Why do AI-generated Power BI reports look generic or broken?

Common failures include truncated bar baselines, dual y-axes, KPI carpet-bombing, monochrome bars, raw field names on axes, and tone declared but never propagated to palette and typography. The anti-patterns catalog and pre-flight checklist catch these before handoff.