From tabular-editor
Generates Best Practice Analyzer (BPA) rules for Tabular Editor based on a description or model analysis. Outputs a complete rule in JSON format with scope, expression, and severity.
How this command is triggered — by the user, by Claude, or both
Slash command
/tabular-editor:suggest-rule [description or model path]sonnetThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Suggest BPA Rule Generate a BPA (Best Practice Analyzer) rule based on the provided description or model analysis. ## Arguments $ARGUMENTS ## Instructions 1. **Understand the Request** - If a description is provided, identify the best practice to enforce - If a model path is provided, analyze the model for potential rule opportunities 2. **Load Skill Context** - Load the `bpa-rules` skill for reference documentation - Review `references/expression-syntax.md` for available properties and patterns - Check `examples/comprehensive-rules.json` for similar existing rules 3...
Generate a BPA (Best Practice Analyzer) rule based on the provided description or model analysis.
$ARGUMENTS
Understand the Request
Load Skill Context
bpa-rules skill for reference documentationreferences/expression-syntax.md for available properties and patternsexamples/comprehensive-rules.json for similar existing rulesGenerate Rule
PREFIX_DESCRIPTIVE_NAMEOutput Format
Provide the complete rule in JSON format:
{
"ID": "PREFIX_RULE_NAME",
"Name": "Human readable rule name",
"Category": "Category",
"Description": "Why this rule matters and guidance for fixing",
"Severity": 2,
"Scope": "Measure, CalculatedColumn",
"Expression": "Dynamic LINQ expression",
"FixExpression": null,
"CompatibilityLevel": 1200
}
User: "Create a rule to check if measures use CALCULATE without filters"
Output:
{
"ID": "DAX_CALCULATE_NO_FILTERS",
"Name": "CALCULATE should have filter arguments",
"Category": "DAX Expressions",
"Description": "CALCULATE without filter arguments is redundant. Either add filters or remove CALCULATE.",
"Severity": 1,
"Scope": "Measure, CalculatedColumn",
"Expression": "Tokenize().Any(Type = FUNCTION and Text = \"CALCULATE\") and not Tokenize().Any(Type = FUNCTION and Text = \"CALCULATE\" and Next.Type = OPEN_PARENS and Next.Next.Type <> COMMA)",
"FixExpression": null,
"CompatibilityLevel": 1200,
"Remarks": "May have false positives for complex expressions"
}
npx claudepluginhub jonathan-pap/power-bi-agentic-development --plugin tabular-editor2plugins reuse this command
First indexed Jul 17, 2026
/suggest-ruleGenerates Best Practice Analyzer (BPA) rules for Tabular Editor based on a description or model analysis. Outputs a complete rule in JSON format with scope, expression, and severity.
/pbi-daxGenerates a DAX measure or pattern for Power BI based on a business requirement description, with variables, comments, prerequisites, format string, and notes.
/audit-rulesAudits .claude/rules/ files across enforceability, token efficiency, conflict detection, and correctness risk dimensions. Supports --full and --mini depth flags.
/data-qualityGenerates data quality rules, expectations, and test suites for data models by analyzing model SQL or schema descriptions. Supports Great Expectations suites, dbt YAML tests, and custom SQL assertions.
/suggest-improvementGenerates a structured MD improvement suggestion artifact for rules, validations, or skills based on learning insights from code reviews.
/dpiaGenerates a UK GDPR Article 35 Data Protection Impact Assessment (DPIA) by analyzing project data models, architecture principles, requirements, and external policies to produce a compliance report with risk mitigations.