Claude Skills by thedixitjain

'Execute this skill enables AI assistant to create application performance monitoring (apm) dashboards. it is triggered when the user requests the creation of a new apm dashboard, monitoring dashboard, or a dashboard for application performance. the skill helps ... Use when generating or creating new content. Trigger with phrases like ''generate'', ''create'', or ''scaffold''. '

Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.

Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.

Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot.

Language-specific super-code guidelines for csharp.

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

'Set up and optimize Cursor codebase indexing for semantic code search and @Codebase queries. Triggers on \"cursor index\", \"codebase indexing\", \"index codebase\", \"cursor semantic search\", \"@codebase\", \"cursor embeddings\". '

'Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring. Triggers on \"cursor composer\", \"multi-file edit\", \"cursor generate files\", \"composer workflow\", \"cursor scaffold\", \"Cmd+I\". '

'Debug AI suggestion quality, context issues, and code generation problems in Cursor. Triggers on \"debug cursor ai\", \"cursor suggestions wrong\", \"bad cursor completion\", \"cursor ai debug\", \"cursor hallucination\". '

'Work with multiple repositories in Cursor: multi-root workspaces, monorepo patterns, selective indexing, and cross-project context. Triggers on \"cursor multi repo\", \"cursor multiple projects\", \"cursor monorepo\", \"cursor workspace\", \"multi-root workspace\". '

'Optimize Cursor IDE performance: reduce memory usage, speed up indexing, tune AI features, and manage extensions for large codebases. Triggers on \"cursor performance\", \"cursor slow\", \"cursor optimization\", \"cursor memory\", \"speed up cursor\", \"cursor lag\". '

'Reference architecture for Cursor IDE projects: directory structure, rules organization, indexing strategy, and team configuration patterns. Triggers on \"cursor architecture\", \"cursor project structure\", \"cursor best practices\", \"cursor file structure\". '

'Set up Cursor for teams: plan selection, member management, shared rules, admin dashboard, and onboarding. Triggers on \"cursor team\", \"cursor organization\", \"cursor business\", \"cursor enterprise setup\", \"cursor admin\". '

'Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines. Triggers on \"upgrade cursor\", \"update cursor\", \"cursor migration\", \"cursor new version\", \"vs code to cursor\", \"cursor changelog\". '

'Track and analyze Cursor usage metrics via admin dashboard: requests, model usage, team productivity, and cost optimization. Triggers on \"cursor analytics\", \"cursor usage\", \"cursor metrics\", \"cursor reporting\", \"cursor dashboard\", \"cursor ROI\". '

'Apply Customer.io advanced debugging and incident response. Use when diagnosing complex delivery issues, investigating campaign failures, or running incident playbooks. Trigger: \"debug customer.io\", \"customer.io investigation\", \"customer.io troubleshoot\", \"customer.io incident\", \"customer.io not delivering\". '

'Diagnose and fix Customer.io common errors. Use when troubleshooting API errors, delivery failures, campaign issues, or SDK exceptions. Trigger: \"customer.io error\", \"customer.io not working\", \"debug customer.io\", \"customer.io 401\", \"customer.io 429\". '

'Collect Customer.io debug evidence for support tickets. Use when creating support requests, investigating delivery failures, or documenting integration issues. Trigger: \"customer.io debug\", \"customer.io support ticket\", \"collect customer.io logs\", \"customer.io diagnostics\". '

'Identify and avoid Customer.io anti-patterns and gotchas. Use when reviewing integrations, onboarding developers, or auditing existing Customer.io code. Trigger: \"customer.io mistakes\", \"customer.io anti-patterns\", \"customer.io gotchas\", \"customer.io pitfalls\", \"customer.io code review\". '

'Optimize Customer.io API performance for high throughput. Use when improving response times, implementing connection pooling, batching, caching, or regional routing. Trigger: \"customer.io performance\", \"optimize customer.io\", \"customer.io latency\", \"customer.io connection pooling\". '

'Implement Customer.io enterprise reference architecture. Use when designing integration layers, event-driven architectures, or enterprise-grade Customer.io setups. Trigger: \"customer.io architecture\", \"customer.io design\", \"customer.io enterprise\", \"customer.io integration pattern\". '

'Apply production-ready Customer.io SDK patterns. Use when implementing typed clients, retry logic, event batching, or singleton management for customerio-node. Trigger: \"customer.io best practices\", \"customer.io patterns\", \"production customer.io\", \"customer.io architecture\", \"customer.io singleton\". '

'Plan and execute Customer.io SDK upgrades and migrations. Use when upgrading customerio-node versions, migrating from legacy APIs, or updating to new SDK patterns. Trigger: \"upgrade customer.io\", \"customer.io migration\", \"update customer.io sdk\", \"customer.io breaking changes\". '

Use when reasoning about how an ACM/IEEE Design Automation Conference (DAC) Research Manuscript is evaluated, covering double-blind TPC review, the novelty-plus-QoR decision criteria, program-committee discussion, the accept/reject (no major-revision) outcome, the ~20-25% selectivity, and how DAC's industry-facing, single-shot process differs from the architecture venues' rebuttal-and-revision cycles.

Use when deciding whether an EDA or chip-design project belongs at the ACM/IEEE Design Automation Conference (DAC) and, if so, in the double-blind archival Research Manuscript track versus the industry-facing Engineering Track — or whether it should route to a sibling EDA venue (ICCAD, DATE, ASP-DAC) or a computer-architecture venue (ISCA/MICRO/HPCA), decided by contribution shape, QoR evidence maturity, and the November calendar.

Recovers broken agent state via crash recovery, context overflow, and merge conflict protocols. Use when an agent session fails or a worktree is corrupted.

Language-specific super-code guidelines for dart.

| Guard production Databricks data pipelines — Delta Lake, Liquid Clustering, Structured Streaming, Auto Loader, and DLT — against the twelve foot-guns that fire at scale: OPTIMIZE/auto-compaction conflicts, Liquid-Clustering merge conflicts, VACUUM breaking a streaming checkpoint, RocksDB OOM, Auto Loader schema-evolution stops, and DLT refresh data loss. Includes a PreToolUse hook that blocks DROP/CREATE-OR-REPLACE/VACUUM on a table with active streaming consumers. Use when a Delta MERGE/OP...

| Pilot a Databricks Hive Metastore (HMS) → Unity Catalog (UC) migration before the deadline — audit every table's migratability, produce a dependency-ordered migration plan, trace UC's two-level permission model, and pick an environment isolation pattern. Use when a user asks how to migrate off the Hive metastore, move to Unity Catalog, which tables are UC-ready, why a table won't migrate, why a user lacks access after migration, or how to isolate dev/test/prod under UC. Trigger with \"migra...

Generate production code for Dataverse SDK using advanced patterns, error handling, and optimization techniques.

Generate production-ready Python code using Dataverse SDK with error handling, optimization, and best practices

Generate complete solutions for specific Dataverse SDK use cases with architecture recommendations

DAX performance optimization for semantic models. Automatically invoke when the user asks to \"optimize DAX\", \"fix slow DAX\", \"DAX performance\", \"tune a measure\", \"debug a measure\", \"DAX anti-patterns\", or mentions slow queries, server timings, or DAX authoring.

Guide for building reliable, fault-tolerant Go applications with DBOS durable workflows. Use when adding DBOS to existing Go code, creating workflows and steps, or using queues for concurrency control.

Guide for building reliable, fault-tolerant Python applications with DBOS durable workflows. Use when adding DBOS to existing Python code, creating workflows and steps, or using queues for concurrency control.

Guide for building reliable, fault-tolerant TypeScript applications with DBOS durable workflows. Use when adding DBOS to existing TypeScript code, creating workflows and steps, or using queues for concurrency control.

Validate domain boundaries -- detect cross-context import violations and aggregate invariant issues. Use when auditing a DDD codebase for leaks between bounded contexts, before merging cross-cutting changes, or as a CI gate to catch boundary erosion early.

Find unused functions and dead code in the codebase

Use when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging process before proposing any fix. Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Produces a `.orchestrator/debug/` artifact the fixer agent must reference.

Use for bugs, unexpected behavior, regressions, or failing tests you did not write.

Systematic root-cause isolation for test failures, runtime errors, or unexpected behavior. Narrow hypothesis → verify → fix.

Systematically diagnose and resolve bugs through conversational investigation and root cause analysis

All pods run in namespace crs. Use when pods in the crs namespace are in CrashLoopBackOff, OOMKilled, or restarting, multiple services restart simultaneously (cascade failure), or redis is unresponsive or showing AOF warnings.

> Debugs the Buttercup CRS (Cyber Reasoning System) running on Kubernetes. Use when diagnosing pod crashes, restart loops, Redis failures, resource pressure, disk saturation, DinD issues, or any service misbehavior in the crs namespace. Covers triage, log analysis, queue inspection, and common failure patterns for: redis, fuzzer-bot, coverage-bot, seed-gen, patcher, build-bot, scheduler, task-server, task-downloader, program-model, litellm, dind, tracer-bot, merger-bot, competition-api, pov-r...

Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.

Run the Maestro debugging workflow for investigation-heavy tasks

Run the Maestro debugging workflow for investigation-heavy tasks

Debug issues by investigating logs, database state, and git history

'Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues. '

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.