powerbi-report-designlisted

# Power BI Report Design Skill This skill provides design guidance for Power BI reports. It commits a design identity (tone + signature), routes user requests to the right archetype per page, and applies cross-cutting design principles (color, typography, iconography, layout, interactivity, accessibility). **Scope boundary** — This skill decides *what* a report should look like and *why*. It does **not** write PBIR files. After producing a design contract, hand off to `powerbi-report-authoring` for all file mechanics: page/visual creation, theme registration, expression encoding, formatting objects, and validation. ## Must/Prefer/Avoid ### MUST - Inspect the semantic model or available fields before making design decisions. - Produce concrete design choices: tone, signature, page archetype, chart rationale, layout direction, color, typography, and accessibility considerations. - Hand off file mechanics to `powerbi-report-authoring`; this skill does not edit PBIR. ### PREFER - Ask only for missing design inputs that materially affect the outcome. - Use reference files on demand instead of loading the full design catalog. - Emit a structured `Design Brief:` when the design will be implemented. ### AVOID - Do not create pages, visuals, filters, themes, or PBIR files directly. - Do not provide vague "make it modern" guidance without concrete layout/color/chart decisions. - Do not replace the planning workflow for broad create/build requests. ## Topic Files and Examples