Claude Skills by thedixitjain

'Apply advanced debugging techniques for hard-to-diagnose Perplexity Sonar API issues. Use when standard troubleshooting fails, investigating inconsistent citations, or preparing evidence for support escalation. Trigger with phrases like \"perplexity hard bug\", \"perplexity mystery error\", \"perplexity inconsistent results\", \"difficult perplexity issue\", \"perplexity deep debug\". '

'Choose and implement Perplexity architecture blueprints for different scales: direct search widget, cached research layer, and multi-query pipeline. Trigger with phrases like \"perplexity architecture\", \"perplexity blueprint\", \"how to structure perplexity\", \"perplexity project layout\". '

'Diagnose and fix Perplexity Sonar API errors and exceptions. Use when encountering Perplexity errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like \"perplexity error\", \"fix perplexity\", \"perplexity not working\", \"debug perplexity\", \"perplexity 429\". '

'Collect Perplexity debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Perplexity problems. Trigger with phrases like \"perplexity debug\", \"perplexity support bundle\", \"collect perplexity logs\", \"perplexity diagnostic\". '

'Execute Perplexity incident response procedures with triage, mitigation, and postmortem. Use when responding to Perplexity API outages, investigating search failures, or running post-incident reviews for Perplexity integration issues. Trigger with phrases like \"perplexity incident\", \"perplexity outage\", \"perplexity down\", \"perplexity on-call\", \"perplexity emergency\". '

'Identify and avoid Perplexity anti-patterns and common integration mistakes. Use when reviewing Perplexity code, onboarding new developers, or auditing existing integrations for best practices violations. Trigger with phrases like \"perplexity mistakes\", \"perplexity anti-patterns\", \"perplexity pitfalls\", \"perplexity code review\", \"perplexity gotchas\". '

'Migrate to Perplexity Sonar from other search/LLM APIs using the strangler fig pattern. Use when switching from Google Custom Search, Bing API, or other LLMs to Perplexity, or migrating from legacy pplx-api models. Trigger with phrases like \"migrate to perplexity\", \"switch to perplexity\", \"replace search API with perplexity\", \"perplexity replatform\". '

'Optimize Perplexity Sonar API performance with caching, streaming, model routing, and batching. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Perplexity integrations. Trigger with phrases like \"perplexity performance\", \"optimize perplexity\", \"perplexity latency\", \"perplexity caching\", \"perplexity slow\". '

'Implement Perplexity reference architecture with model routing, citation pipeline, and research automation. Use when designing new Perplexity integrations, reviewing project structure, or establishing architecture for search-augmented apps. Trigger with phrases like \"perplexity architecture\", \"perplexity project structure\", \"how to organize perplexity\", \"perplexity design patterns\". '

'Apply production-ready Perplexity Sonar API patterns for TypeScript and Python. Use when implementing Perplexity integrations, refactoring SDK usage, or establishing team coding standards for search-augmented generation. Trigger with phrases like \"perplexity SDK patterns\", \"perplexity best practices\", \"perplexity code patterns\", \"idiomatic perplexity\", \"perplexity wrapper\". '

'Migrate between Perplexity model generations and API parameter changes. Use when upgrading to new Sonar models, handling deprecated parameters, or migrating from legacy pplx-api models. Trigger with phrases like \"upgrade perplexity\", \"perplexity migration\", \"perplexity model change\", \"update perplexity\", \"perplexity deprecated\". '

Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files th...

>- Build a PFMEA worksheet, process risk analysis, or AP table using the AIAG-VDA FMEA Handbook 2019 7-step approach. Covers Structure Analysis, Function Analysis, Failure Analysis, Risk Analysis (Action Priority H/M/L), Optimization, and Documentation. Required by IATF 16949 and OEM customer-specific requirements for new processes, process changes, and post-escape PFMEA updates.

Use when debugging any bug. Enforces a 5-phase protocol where code edits are blocked until root cause is confirmed. Prevents premature fix attempts.

'Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications. '

Language-specific super-code guidelines for php.

Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.

High-performance genomic interval operations and bioinformatics file I/O on Polars DataFrames. Overlap, nearest, merge, coverage, complement, subtract for BED/VCF/BAM/GFF intervals. Streaming, cloud-native, faster bioframe alternative.

High-performance DataFrame library for Python ETL, analytics, and pandas migration. Use for expression-based data manipulation with lazy query optimization, parallel execution, streaming out-of-core processing, Arrow interoperability, and optional GPU execution.

Use when selecting or auditing the method for a Production and Operations Management (POM) manuscript — analytical modeling (optimization, stochastic models, game theory), empirical identification, behavioral experiments, simulation, or operations data science. Matches method to the operations question; it does not execute the analysis (pom-data-analysis).

> Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into \"later means never\". Use when the user says \"ponytail debt\", \"/ponytail-debt\", \"what did ponytail defer\", \"list the shortcuts\", \"ponytail ledger\", or \"what did we mark to do later\". One-shot report, changes nothing.

> Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says \"review for over-engineering\", \"what can we delete\", \"is this over-engineered\", \"simplify review\", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

> Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. ...

Use when designing the empirical component of a POPL paper — deciding whether evidence should be a mechanization, a prototype, case studies, or benchmarks; reporting proof effort and case-study coverage honestly; and keeping performance numbers in a supporting role so the formal claim stays the paper's center of gravity.

Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from stated needs, then hand off to the build skills. The advisory entry point. Use when starting a new data-portal project and the underlying architecture has not yet been decided.

/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics.

../../../c-level-advisor/c-level-agents/skills/post-mortem/SKILL.md

PostgreSQL optimization including indexes, query plans, partitioning, JSONB operations, and connection pooling

PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS).

'Diagnose and fix common PostHog errors: events not appearing, flags returning undefined, 401/429 errors, SDK initialization failures, and identity issues. Trigger: \"posthog error\", \"fix posthog\", \"posthog not working\", \"debug posthog\", \"posthog events missing\", \"posthog broken\". '

'Collect PostHog debug evidence for support tickets and troubleshooting. Gathers SDK versions, API connectivity, event flow status, flag definitions, and redacted configuration into a support-ready archive. Trigger: \"posthog debug\", \"posthog support bundle\", \"collect posthog logs\", \"posthog diagnostic\", \"posthog not working debug\". '

'PostHog enterprise access control: organization/project hierarchy, member roles, scoped API keys, SSO/SAML configuration, and activity audit logging. Trigger: \"posthog SSO\", \"posthog RBAC\", \"posthog enterprise\", \"posthog roles\", \"posthog permissions\", \"posthog SAML\", \"posthog access\". '

'PostHog incident response: triage decision tree, immediate actions for 401/429/500 errors, graceful degradation, evidence collection, and postmortem. Trigger: \"posthog incident\", \"posthog outage\", \"posthog down\", \"posthog on-call\", \"posthog emergency\", \"posthog broken production\". '

'Migrate to PostHog from Google Analytics, Mixpanel, Amplitude, or Segment. Covers dual-write strategy, historical data import, event name mapping, identity resolution, and feature flag based traffic shifting. Trigger: \"migrate posthog\", \"posthog migration\", \"switch to posthog\", \"posthog from mixpanel\", \"posthog from GA\", \"posthog replatform\". '

'Optimize PostHog performance: local flag evaluation, client batching config, event sampling, efficient HogQL queries, and serverless flush patterns. Trigger: \"posthog performance\", \"optimize posthog\", \"posthog latency\", \"posthog caching\", \"posthog slow\", \"posthog batch\", \"posthog fast\". '

'Production PostHog architecture: event taxonomy, SDK layering, feature flag strategy, analytics module layout, and data pipeline integration patterns. Trigger: \"posthog architecture\", \"posthog best practices\", \"posthog project structure\", \"how to organize posthog\", \"posthog design\". '

'Upgrade posthog-js and posthog-node SDKs with breaking change detection. Covers v4 to v5 posthog-node migration (sendFeatureFlags change), posthog-js autocapture API changes, and version-specific gotchas. Trigger: \"upgrade posthog\", \"posthog breaking changes\", \"update posthog SDK\", \"posthog version\", \"posthog migration\". '

/em:postmortem — Honest analysis of what went wrong. Use after a failed launch, missed quarter, or bad hire to run a blameless 5-Whys retrospective with a change register — e.g. dissecting why the Q3 release slipped six weeks.

Optionally test a retrospective causal

Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.

../../../c-level-advisor/executive-mentor/skills/postmortem/SKILL.md

Scaffold a complete Power Apps Code App project with PAC CLI setup, SDK integration, and connector configuration

Comprehensive Power BI DAX formula optimization prompt for improving performance, readability, and maintainability of DAX calculations.

Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.

Use this skill when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams.

Author, validate, and test Power Query M expressions in semantic model partitions. Automatically invoke when the user mentions \"Power Query\", \"M code\", \"M expression\", \"partition expression\", \"query folding\", or asks to \"write Power Query\", \"fix Power Query\", \"test a partition\", \"preview partition data\", \"debug Power Query step\", \"optimize Power Query\".

>- Production Part Approval Process (PPAP) — verify PPAP submission level, audit all 18 elements, check completeness for customer approval, prepare PSW. Use when a supplier needs to submit parts for approval, when reviewing a PPAP package, or when determining which PPAP level is required. Covers AIAG PPAP 4th edition with Ford, BMW, VW, and Stellantis OEM-specific requirements.

Use when writing a PPoPP author-response rebuttal, covering the short fixed word-capped window, answering the recurring \"does it scale?\" and \"what about baseline X?\" questions with pre-run numbers, correcting factual misreadings of a concurrency argument, staying double-blind, and prioritizing the points that can actually move a decision.

Use when designing or auditing a PPoPP paper's evaluation, covering the twin bar of concurrency correctness and measured scalability — speedup curves, strong vs weak scaling, core/thread sweeps, NUMA and GPU effects, contention microbenchmarks plus real workloads, variance and measurement hygiene, and honest strong baselines.

Use when deciding whether a parallel/concurrent-computing project belongs at PPoPP or should be routed to PLDI, CGO, POPL, ASPLOS, HPCA, SC, SPAA, or OOPSLA, and when distinguishing PPoPP's \"the parallelism is the point\" scope from a compiler contribution (CGO/PLDI), a concurrency logic (POPL), or a microarchitecture result (ASPLOS/HPCA).