
Claude Skills by fabioc-aloha
github.com/fabioc-alohaSchema design, normalization, query optimization, and data modeling patterns
Use this skill to get context about Fabric Lakehouse and its features for software systems and AI-powered functions. It offers descriptions of Lakehouse data components, organization with schemas and shortcuts, access control, and code examples. This skill supports users in designing, building, and optimizing Lakehouse solutions using best practices.
KQL language expertise for writing correct, efficient Kusto Query Language queries. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries -- even simple ones -- because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Trigger on: ...
Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.
Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active mo...
Generate comprehensive synthetic relational data for any specified subject with multiple normalized CSV files maintaining referential integrity
Analyze Power BI semantic models for column-level overlaps that confuse Copilot and Fabric data agents. Detect ambiguity, review with domain expert, apply fixes via MCP.
Analyze a semantic model (via MCP or TMDL) to find columns whose value domains overlap, classify ambiguity types, generate proposed descriptions/rules/exclusions, and produce a review Excel for domain experts. Use when a semantic model has columns whose values overlap across tables or hierarchies, when Copilot picks the wrong column for ambiguous queries, when preparing a model for Prep data for AI, or when auditing a model for attribute collisions before connecting a data agent.
Inline Python in shell scripts has quoting issues:
VS Code's TMDL (Tabular Model Definition Language) linter reports valid syntax as errors:
Hardcoded paths in build scripts break when directory structure changes:
Patterns for requirements elicitation, BRDs, process analysis, and stakeholder alignment.
Patterns for organizational change, ADKAR methodology, stakeholder engagement, and adoption strategies.
Mixing structure and content makes both hard to maintain:
When extracting hardcoded data to JSON, field values silently drift:
Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.
Patterns for fiction, narrative structure, character development, dialogue, and storytelling craft.
Template-driven layouts require code changes for structural updates:
Focus blocks, distraction management, and flow state triggers for cognitively demanding work
What to do when things break.
One-time fixes get repeated manually:
Create well-structured git commits using the Conventional Commits specification. Use when asked to \"commit changes\", \"create a git commit\", \"stage and commit\", \"write a commit message\", or \"/commit\". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
Consistent git practices, recovery patterns, and safe operations.
Older action versions trigger deprecation warnings and will eventually break:
GitHub README display rules — which README renders when multiple exist, profile READMEs, org READMEs
GitHub Wiki has a flat namespace — no real folders, sidebar ordering tricks, link gotchas
Calm, systematic crisis handling — from detection through post-mortem to prevention
Production visibility through logs, metrics, traces, and alerting — the three pillars of observability
Add a new project to the planning suite. Creates a project-specific configuration directory and walks through project settings.
Write a postmortem for a regression or incident that escaped to production, broke real users, and traces back to a design flaw worth documenting. Use when asked to \"write a postmortem\", \"document an incident\", \"analyze a production failure\", \"root cause analysis\", or \"incident review\". Only invoke after confirming no existing postmortem covers the same root cause.
Best practice decision matrix for choosing between Marp, Gamma, and PptxGenJS based on use case requirements.
Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces...
Universal deployment patterns for any project type.
Systematic methodology for identifying, categorizing, and mitigating software project risks before implementation
Generate release notes or changelog entries for completed changes. Use when asked to \"write release notes\", \"update the changelog\", \"document what changed\", \"create a release summary\", or when preparing a release. Follows Keep a Changelog format.
Pre-checks, version consistency, and deployment discipline.
Recognize scope creep, suggest MVP cuts, and manage project boundaries
Analyze documentation gaps, create Architecture Decision Records (ADRs), and build knowledge indexes. Use after feature completion, during knowledge sharing, or when onboarding documentation needs ...
Detect burnout signals and proactively support sustainable productivity.
Use when creating, editing, or generating draw.io diagram files (.drawio, .drawio.svg, .drawio.png). Covers mxGraph XML authoring, shape libraries, style strings, flowcharts, system architecture, sequence diagrams, ER diagrams, UML class diagrams, network topology, layout strategy, the hediet.vscode-drawio VS Code extension, and the full agent workflow from request to a ready-to-open file.
Generate Excalidraw diagrams from natural language descriptions. Use when asked to \"create a diagram\", \"make a flowchart\", \"visualize a process\", \"draw a system architecture\", \"create a mind map\", or \"generate an Excalidraw file\". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Create Mermaid diagrams for flowcharts, sequences, ERDs, and architectures. Masters syntax for all diagram types and styling.
Help writers produce content that sounds genuinely human by avoiding telltale AI-generated text patterns
Technical documentation, API references, user guides, and docs-as-code workflows.
Generate launch-companion content for books — blog posts, author notes, and dogfooding angles that demonstrate the book's thesis through its own production. Use when a manuscript is approaching publication submission (KDP, agent query, prelaunch).
Markdown-to-PDF pipeline via Pandoc and LuaLaTeX with emoji rendering, dual output, and print-ready formatting
Create diagrams using Mermaid.js markdown-inspired syntax. Supports 23+ diagram types including flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, state diagrams, pie charts,...
Comprehensive preparation for doctoral dissertation defense including timeline management, presentation design, Q&A practice, mock sessions, and committee dynamics.
Structured workflow for co-authoring technical documentation. Use when asked to \"write documentation\", \"create a spec\", \"draft a proposal\", \"write a design doc\", \"create an RFC\", \"document this feature\", or \"write technical docs\". Three stages: context gathering, iterative refinement, and reader testing.
Documentation hygiene — anti-drift rules, count elimination, and living document maintenance