measures

Design Power BI DAX measure layers with TMDL wrappers and naming conventions.

2|Updated May 1, 2026
One-click install
npx skills add https://github.com/jonathan-pap/PowerBI-Claude-Design --skill measures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: measures
Source: https://github.com/jonathan-pap/PowerBI-Claude-Design/tree/main/measures
Command: npx skills add https://github.com/jonathan-pap/PowerBI-Claude-Design --skill measures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Measures unit provides a structured approach to designing, naming, and implementing Power BI DAX measures, ensuring consistency and scalability across models.

Core Features & Use Cases

  • Naming conventions with prefixes for different measure types and consistent formatting.
  • Time intelligence and KPI patterns, including YTD, QTD, MTD, PY, rolling periods, and variance calculations.
  • TMDL-wrapped measure definitions, display folders, and recommended folder structures for production-ready models.
  • Practical examples across base, time, and semi-additive measures for revenue, headcount, and budgets.

Quick Start

Scaffold a complete measure layer for your Power BI model using the patterns and templates in this guide.

Frequently Asked Questions about measures

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

FAQPage Schema
How do I design a consistent Power BI measure layer for large data models?

Designing a consistent Power BI measure layer requires standard naming conventions, structured display folders, and TMDL-wrapped definitions to ensure scalability and maintainability across business domains like revenue and headcount.

What naming patterns should I use for base, time intelligence, and KPI measures in DAX?

DAX measure naming patterns use specific prefixes to distinguish base measures, time intelligence calculations like YTD and MTD, and KPI variances, ensuring clear identification and consistent formatting throughout the Power BI model.

How do I implement semi-additive measures for headcount and budget tracking in Power BI?

Implement semi-additive measures in Power BI by applying specialized DAX patterns that aggregate values differently across time periods, enabling accurate headcount and budget snapshots without inflating totals over date ranges.

Does this approach support TMDL wrappers for production-ready Power BI deployments?

Yes, this approach provides TMDL-wrapped measure definitions and recommended folder structures, enabling production-ready Power BI deployments with clear dependency tracking and standardized asset exposure across the model.

What is the best way to structure time intelligence calculations like PY and rolling periods in DAX?

The best way to structure DAX time intelligence is to apply standardized patterns for Previous Year (PY), rolling periods, and variance calculations, placing them in dedicated display folders to separate base measures from time-based logic.