agentsclimarketplace

Power bi report design

Skill MagicRockall/powerbi-skills-marketplace/skills/power-bi-report-design

Design Power BI report layouts, select chart types, plan page structures, choose themes, and apply data storytelling principles BEFORE generating PBIR JSON files. Use this skill whenever the user asks to design a report, plan a dashboard layout, choose visualizations, decide on chart types, apply storytelling to data, select a theme or color palette, plan page navigation, or structure report pages for a Power BI project. Also use when the user provides requirements and needs a report design spec before generation, or when reviewing/improving an existing report's visual design, layout, or UX. This skill produces a Design Spec — a structured plan of pages, visuals, layout, theme, and navigation — that feeds into the `power-bi-pbip-report` skill for JSON generation. Do NOT use for generating PBIR JSON files, validating report structure, or building the semantic model. For JSON generation, use `power-bi-pbip-report`.From its SKILL.md

Install
npx -y skills add MagicRockall/powerbi-skills-marketplace --skill power-bi-report-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

9.5 KB, as published. Nobody here has run it

Power BI Report Design

Plan and design Power BI reports before generating PBIR files. This skill transforms business requirements and a semantic model into a structured Design Spec that the power-bi-pbip-report skill consumes to produce the actual .Report/ folder.

Always search Microsoft Learn (microsoft-learn-mcp/microsoft_docs_search) for the latest visualization guidance before recommending chart types or patterns.

Reference Files

Role files (phase-driven workflow)

These role files correspond to the power-bi-developer agent's design phases. Load the one matching the current phase.

Role FileUsed InPurpose
references/strategist.mdPhase 4a5-question intake, style selection, layout/chart picks, produces the Design Spec
references/executor-base.mdPhase 4bShared two-pass (Layout → Narrative) rules inherited by all executors
references/executor-executive.mdPhase 4bExecutive personality — ≤4 visuals, Big-Idea titles, high whitespace
references/executor-analytical.mdPhase 4bAnalytical personality — 5-8 visuals, KPI + hero + 3-col grid, direct labels
references/executor-operational.mdPhase 4bOperational personality — 8-12 visuals, traffic-light status, large fonts
references/polisher.mdPhase 4cDrives finalize_pbir.py + design_quality_check.py, Design Spec reconciliation

Shared standards & templates

ReferenceWhen to Read
references/shared-standards.mdNon-negotiable PBIR design rules — banned patterns, grid, typography scale, color 60/30/10, accessibility, performance budgets. All roles must load this.
references/design-spec-reference.md11-section Design Spec contract template + Seven Confirmations sign-off table
references/layouts/layouts-index.jsonIndex of starter page layouts (slot coordinates, style tags)
references/layouts/*.mdIndividual layout recipes (exec-overview-16x9, sales-performance, drillthrough-detail, …)
references/chart-templates/chart-templates-index.jsonIndex of chart recipes (composition + slots + gotchas)
references/chart-templates/*.mdIndividual chart recipes (kpi-banner, bar-comparison, trend-line, yoy-variance, waterfall-bridge, …)
assets/icons/SVG icon library (Tabler / Lucide / custom sets). Strategist binds a set in Seven Confirmations item #6.
assets/images/Raster artwork — backgrounds, banners, dividers, demo logos.
assets/layout-previews/SVG thumbnails (1 per layout) used in Seven Confirmations item #2
assets/chart-previews/SVG/PNG thumbnails (1 per chart recipe) used in Design Spec §5

Legacy / cross-skill references

ReferenceWhen to Read
references/chart-selection-guide.mdDeciding WHICH chart type to use — decision matrix, hard rules (why bar beats pie)
references/visual-vocabulary.mdIntent-first catalog: 9 data-relationship categories × ~70 charts (FT Visual Vocabulary / Gramener edition) mapped to Power BI visualTypes
references/visual-design-principles.mdPre-attentive attributes, Gestalt principles, color theory, typography, narrative structure, Kirk's 5-layer design process, accessibility design (alt text, tab order, markers, contrast, checklist)
references/page-layout-templates.mdStarting layouts: Overview, Detail, Drillthrough, Tooltip, Grid, Sidebar, Scorecard, Tab-Nav
references/domain-report-structures.mdIndustry page sets: Sales, Manufacturing, Financial, Supply Chain, Retail, Healthcare, Technology
references/theme-colors.mdTheme architecture, semantic colors, industry palettes, custom theme JSON patterns, colorblind-safe alternatives
../power-bi-pbip-report/references/common-patterns.mdReusable components: KPI rows, slicer panels, background shapes, page navigator, visual interactions, TOP N chart (shared with pbip-report)
references/navigation-patterns.mdNavigation buttons, bookmark tabs, back button, reset filters, hub-and-spoke, breadcrumbs, page navigator
references/slicer-filter-patterns.mdDecision guide for filter scope, slicer type selection, sync groups, cross-filter vs. highlight, default state, filter-vs-drillthrough, pane visibility, RLS interaction
references/slicer-patterns/Recipe cookbook — 14 slicer/filter composition recipes (ASCII mockup + slots + property snippet + defaults + anti-patterns) in 7 families: date, category, numeric, search, architecture, governance, parameter. Index: slicer-patterns/slicer-patterns-index.json
../power-bi-pbip-report/references/mobile-layout.mdMobile design rules, auto-create, minimum visual sizes, formatting, slicer behavior, limitations
../power-bi-pbip-report/references/themes/*.jsonReady-to-use custom theme files (8 industries) — canonical source

Design Workflow (Summary)

The full workflow is driven by the Strategist role (references/strategist.md). Each step below links to the detailed reference — load the reference, don't re-derive.

StepActionPrimary Reference
1. Audience & PurposeFive-question intake (WHO, WHAT, BIG IDEA, ACTION, STYLE)references/strategist.md Step 1 + references/visual-design-principles.md
2. Page StructureSelect pages by domain + page typereferences/domain-report-structures.md + references/page-layout-templates.md
3. Chart SelectionStart from analytical task → pick chart → pick recipereferences/chart-selection-guide.md + references/visual-vocabulary.md
4. Layout & PositioningKirk's 5-layer process; Z/F-pattern; canvas 1664×936references/visual-design-principles.md + references/layouts/
5. Theme & ColorsBrand or industry palette; 60/30/10 rule; 4.5:1 contrastreferences/theme-colors.md + references/shared-standards.md §3
6. Navigation & FiltersPattern selection + slicer recipe bindingreferences/navigation-patterns.md + references/slicer-filter-patterns.md + references/slicer-patterns/
7. Mobile LayoutAuto-create as starting point; refine for touch/single-column../power-bi-pbip-report/references/mobile-layout.md
8. Produce Design SpecFill all 11 sections of the contract templatereferences/design-spec-reference.md

Hard rules (no pie>5, no 3D, no rainbow, max visuals/page) are defined authoritatively in references/shared-standards.md §1. All roles load that file first.

Related Skills

SkillRelationshipWhen
power-bi-pbip-reportDownstream (Phase 4b)Design Spec is consumed to generate PBIR JSON files
power-bi-dax-developmentUpstream (Phase 3)Measure catalog provides data bindings for visuals
power-bi-business-analysisUpstream (Phase 1)Page plan, audience, KPIs, and domain from requirements
power-bi-performance-troubleshootingCross-cuttingReport-level optimization (visual count, slicer design, query reduction)
power-bi-feedback-iterationLoop-backChart/layout redesign feedback routes through this skill

Phase-Driven Workflow (agent-aligned)

The seven-step workflow above is the classic, skill-internal flow. When invoked from the power-bi-developer agent, follow the role-based phase gates instead:

Agent PhaseRole to loadOutput
4a Design Strategyreferences/strategist.md + shared-standards.md + layouts/chart-templates indexesFilled design-spec-reference.md
4a.5 Seven Confirmations (Plan-mode Q&A, non-blocking)(no role file — vscode_askQuestions panel with recommended defaults; single-message summary as fallback)Recorded user decision on Canvas / Pages / Audience / Style / Palette / Iconography / Navigation (accepted defaults or inline edits)
4b Generationreferences/executor-base.md + one of executor-executive.md / executor-analytical.md / executor-operational.mdPBIR files (Pass 1 Layout → Pass 2 Narrative)
4c Polish & Design QAreferences/polisher.mdfinalize_pbir.py → design_quality_check.py → validate_report.py → evidence package

Phase 4a.5 is a non-blocking Plan-mode review: a single vscode_askQuestions call presents the seven decisions with the Strategist's recommended defaults, and the user can accept the whole panel in one click or via a chat reply of "proceed" / "go" / "looks good". Inline edits update only the changed items; a full redesign loops back to 4a. Do NOT run 4b without a Design Spec, and every 4b regeneration MUST be followed by 4c.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.