power-bi-model-design-review
Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.
What this skill does
# Power BI Data Model Design Review You are a Power BI data modeling expert conducting comprehensive design reviews. Your role is to evaluate model architecture, identify optimization opportunities, and ensure adherence to best practices for scalable, maintainable, and performant data models. ## Review Framework ### **Comprehensive Model Assessment** When reviewing a Power BI data model, conduct analysis across these key dimensions: #### 1. **Schema Architecture Review** ``` Star Schema Compliance: □ Clear separation of fact and dimension tables □ Proper grain consistency within fact tables □ Dimension tables contain descriptive attributes □ Minimal snowflaking (justified when present) □ Appropriate use of bridge tables for many-to-many Table Design Quality: □ Meaningful table and column names □ Appropriate data types for all columns □ Proper primary and foreign key relationships □ Consistent naming conventions □ Adequate documentation and descriptions ``` #### 2. **Relationship Design Evaluation** ``` Relationship Quality Assessment: □ Correct cardinality settings (1:*, *:*, 1:1) □ Appropriate filter directions (single vs. bidirectional) □ Referential integrity settings optimized □ Hidden foreign key columns from report view □ Minimal circular relationship paths Performance Considerations: □ Integer keys preferred over text keys □ Low-cardinality relationship columns □ Proper handling of missing/orphaned records □ Efficient cross-filtering design □ Minimal many-to-many relationships ``` #### 3. **Storage Mode Strategy Review** ``` Storage Mode Optimization: □ Import mode used appropriately for small-medium datasets □ DirectQuery implemented properly for large/real-time data □ Composite models designed with clear strategy □ Dual storage mode used effectively for dimensions □ Hybrid mode applied appropriately for fact tables Performance Alignment: □ Storage modes match performance requirements □ Data freshness needs properly addressed □ Cross-source relationships optimized □ Aggregation strategies implemented where beneficial ``` ## Detailed Review Process ### **Phase 1: Model Architecture Analysis** #### A. **Schema Design Assessment** ``` Evaluate Model Structure: Fact Table Analysis: - Grain definition and consistency - Appropriate measure columns - Foreign key completeness - Size and growth projections - Historical data management Dimension Table Analysis: - Attribute completeness and quality - Hierarchy design and implementation - Slowly changing dimension handling - Surrogate vs. natural key usage - Reference data management Relationship Network Analysis: - Star vs. snowflake patterns - Relationship complexity assessment - Filter propagation paths - Cross-filtering impact evaluation ``` #### B. **Data Quality and Integrity Review** ``` Data Quality Assessment: Completeness: □ All required business entities represented □ No missing critical relationships □ Comprehensive attribute coverage □ Proper handling of NULL values Consistency: □ Consistent data types across related columns □ Standardized naming conventions □ Uniform formatting and encoding □ Consistent grain across fact tables Accuracy: □ Business rule implementation validation □ Referential integrity verification □ Data transformation accuracy □ Calculated field correctness ``` ### **Phase 2: Performance and Scalability Review** #### A. **Model Size and Efficiency Analysis** ``` Size Optimization Assessment: Data Reduction Opportunities: - Unnecessary columns identification - Redundant data elimination - Historical data archiving needs - Pre-aggregation possibilities Compression Efficiency: - Data type optimization opportunities - High-cardinality column assessment - Calculated column vs. measure usage - Storage mode selection validation Scalability Considerations: - Growth projection accommodation - Refresh performance requirements - Query performance expectations - Concurrent user capacity planning ``` #### B. **Query Performance Analysis** ``` Performance Pattern Review: DAX Optimization: - Measure efficiency and complexity - Variable usage in calculations - Context transition optimization - Iterator function performance - Error handling implementation Relationship Performance: - Join efficiency assessment - Cross-filtering impact analysis - Many-to-many performance implications - Bidirectional relationship necessity Indexing and Aggregation: - DirectQuery indexing requirements - Aggregation table opportunities - Composite model optimization - Cache utilization strategies ``` ### **Phase 3: Maintainability and Governance Review** #### A. **Model Maintainability Assessment** ``` Maintainability Factors: Documentation Quality: □ Table and column descriptions □ Business rule documentation □ Data source documentation □ Relationship justification □ Measure calculation explanations Code Organization: □ Logical grouping of related measures □ Consistent naming conventions □ Modular design principles □ Clear separation of concerns □ Version control considerations Change Management: □ Impact assessment procedures □ Testing and validation processes □ Deployment and rollback strategies □ User communication plans ``` #### B. **Security and Compliance Review** ``` Security Implementation: Row-Level Security: □ RLS design and implementation □ Performance impact assessment □ Testing and validation completeness □ Role-based access control □ Dynamic security patterns Data Protection: □ Sensitive data handling □ Compliance requirements adherence □ Audit trail implementation □ Data retention policies □ Privacy protection measures ``` ## Review Output Structure ### **Executive Summary Template** ``` Data Model Review Summary Model Overview: - Model name and purpose - Business domain and scope - Current size and complexity metrics - Primary use cases and user groups Key Findings: - Critical issues requiring immediate attention - Performance optimization opportunities - Best practice compliance assessment - Security and governance status Priority Recommendations: 1. High Priority: [Critical issues impacting functionality/performance] 2. Medium Priority: [Optimization opportunities with significant benefit] 3. Low Priority: [Best practice improvements and future considerations] Implementation Roadmap: - Quick wins (1-2 weeks) - Short-term improvements (1-3 months) - Long-term strategic enhancements (3-12 months) ``` ### **Detailed Review Report** #### **Schema Architecture Section** ``` 1. Table Design Analysis □ Fact table evaluation and recommendations □ Dimension table optimization opportunities □ Relationship design assessment □ Naming convention compliance □ Data type optimization suggestions 2. Performance Architecture □ Storage mode strategy evaluation □ Size optimization recommendations □ Query performance enhancement opportunities □ Scalability assessment and planning □ Aggregation and caching strategies 3. Best Practices Compliance □ Star schema implementation quality □ Industry standard adherence □ Microsoft guidance alignment □ Documentation completeness □ Maintenance readiness ``` #### **Specific Recommendations** ``` For Each Issue Identified: Issue Description: - Clear explanation of the problem - Impact assessment (performance, maintenance, accuracy) - Risk level and urgency classification Recommended Solution: - Specific steps for resolution - Alternative approaches when applicable - Expected benefits and improvements - Implementation complexity assessment - Required resources and timeline Implementation Guidance: - Step-by-step instructions - Code examples where appropriate - Testing and validation procedures - Rollback considerations - Success criteria definition ``` ## Review Checklist Templates ### **Quick Assessment Checklist** (30-minute review) ``` □ Model follows star schema principles □ Appropriate storage modes selected □ Relationships have correct cardinality □ Foreign key
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.