Claude Skills by thedixitjain

Diagnoses and fixes slow Qdrant search. Use when someone reports 'search is slow', 'high latency', 'queries take too long', 'low QPS', 'throughput too low', 'filtered search is slow', or 'search was fast but now it's slow'. Also use when search performance degrades after config changes or data growth.

Code quality checks, formatting, and metrics via qlty CLI

Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.

Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2. Use when leading management reviews, setting quality policy and objectives, monitoring quality KPIs and cost of quality, or exercising QMR governance and regulatory oversight responsibilities.

>- Run quality problem zeroing, perform 双归零 (double-five zeroing), write a technical zeroing report, write a management zeroing report, or close an aerospace quality problem under GB/T 29076—2021. Covers problem reporting, emergency response, team formation, technical zeroing (定位准确、机理清楚、问题复现、 措施有效、举一反三), management zeroing (过程清楚、责任明确、措施落实、严肃处理、 完善规章), evidence gates, review, and closure. Use for aerospace or complex equipment failures, defects, accidents, repeated problems, human-responsibili...

Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.

Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.

JUnit 5、Mockito、REST Assured、Camelテスト、JaCoCoを使用したQuarkus 3.xのテスト駆動開発。機能追加、バグ修正、またはイベント駆動サービスのリファクタリング時に使用。

Desarrollo guiado por pruebas para Quarkus 3.x LTS usando JUnit 5, Mockito, REST Assured, pruebas Camel y JaCoCo. Usar al agregar funcionalidades, corregir bugs o refactorizar servicios orientados a eventos.

Verification loop for Quarkus projects: build, static analysis, tests with coverage, security scans, native compilation, and diff review before release or PR.

\"QuickNode debug bundle \\u2014 blockchain RPC and Web3 infrastructure\\ \\ integration.\\nUse when working with QuickNode for blockchain development.\\nTrigger\\ \\ with phrases like \\\"quicknode debug bundle\\\", \\\"quicknode-debug-bundle\\\", \\\"blockchain\\ \\ RPC\\\".\\n\"

\"QuickNode performance tuning \\u2014 blockchain RPC and Web3 infrastructure\\ \\ integration.\\nUse when working with QuickNode for blockchain development.\\nTrigger\\ \\ with phrases like \\\"quicknode performance tuning\\\", \\\"quicknode-performance-tuning\\\"\\ , \\\"blockchain RPC\\\".\\n\"

\"QuickNode reference architecture \\u2014 blockchain RPC and Web3 infrastructure\\ \\ integration.\\nUse when working with QuickNode for blockchain development.\\nTrigger\\ \\ with phrases like \\\"quicknode reference architecture\\\", \\\"quicknode-reference-architecture\\\"\\ , \\\"blockchain RPC\\\".\\n\"

\"QuickNode upgrade migration \\u2014 blockchain RPC and Web3 infrastructure\\ \\ integration.\\nUse when working with QuickNode for blockchain development.\\nTrigger\\ \\ with phrases like \\\"quicknode upgrade migration\\\", \\\"quicknode-upgrade-migration\\\"\\ , \\\"blockchain RPC\\\".\\n\"

Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use when developers want to optimize their app's size, remove redundant or overly broad keep rules, or troubleshoot Proguard configurations.

Run a sequential three-tier code review on a finished implementation branch — Haiku (surface) → Sonnet (logic) → Opus (deep). Restarts from Tier 1 on any tier failure. Use when a solo branch or PR is code-complete and you want structured pre-merge verification before human review.

\"Ramp debug bundle \\u2014 corporate card and expense management API integration.\\n\\ Use when working with Ramp for card management, expenses, or accounting sync.\\n\\ Trigger with phrases like \\\"ramp debug bundle\\\", \\\"ramp-debug-bundle\\\", \\\"corporate\\ \\ card API\\\".\\n\"

\"Ramp incident runbook \\u2014 corporate card and expense management API\\ \\ integration.\\nUse when working with Ramp for card management, expenses, or accounting\\ \\ sync.\\nTrigger with phrases like \\\"ramp incident runbook\\\", \\\"ramp-incident-runbook\\\"\\ , \\\"corporate card API\\\".\\n\"

\"Ramp migration deep dive \\u2014 corporate card and expense management\\ \\ API integration.\\nUse when working with Ramp for card management, expenses, or\\ \\ accounting sync.\\nTrigger with phrases like \\\"ramp migration deep dive\\\", \\\"ramp-migration-deep-dive\\\"\\ , \\\"corporate card API\\\".\\n\"

\"Ramp performance tuning \\u2014 corporate card and expense management\\ \\ API integration.\\nUse when working with Ramp for card management, expenses, or\\ \\ accounting sync.\\nTrigger with phrases like \\\"ramp performance tuning\\\", \\\"ramp-performance-tuning\\\"\\ , \\\"corporate card API\\\".\\n\"

\"Ramp reference architecture \\u2014 corporate card and expense management\\ \\ API integration.\\nUse when working with Ramp for card management, expenses, or\\ \\ accounting sync.\\nTrigger with phrases like \\\"ramp reference architecture\\\", \\\"\\ ramp-reference-architecture\\\", \\\"corporate card API\\\".\\n\"

\"Ramp upgrade migration \\u2014 corporate card and expense management\\ \\ API integration.\\nUse when working with Ramp for card management, expenses, or\\ \\ accounting sync.\\nTrigger with phrases like \\\"ramp upgrade migration\\\", \\\"ramp-upgrade-migration\\\"\\ , \\\"corporate card API\\\".\\n\"

Provides the complete migration pattern for React legacy context API (contextTypes, childContextTypes, getChildContext) to the modern createContext API. Use this skill whenever migrating legacy context in class components - this is always a cross-file migration requiring the provider AND all consumers to be updated together. Use it before touching any contextTypes or childContextTypes code, because migrating only the provider without the consumers (or vice versa) will cause a runtime failure....

Provides exact before/after migration patterns for the three unsafe class component lifecycle methods - componentWillMount, componentWillReceiveProps, and componentWillUpdate - targeting React 18.3.1. Use this skill whenever a class component needs its lifecycle methods migrated, when deciding between getDerivedStateFromProps vs componentDidUpdate, when adding getSnapshotBeforeUpdate, or when fixing React 18 UNSAFE_ lifecycle warnings. Always use this skill before writing any lifecycle migrat...

Provides exact migration patterns for React string refs (ref=\"name\" + this.refs.name) to React.createRef() in class components. Use this skill whenever migrating string ref usage - including single element refs, multiple refs in a component, refs in lists, callback refs, and refs passed to child components. Always use this skill before writing any ref migration code - the multiple-refs-in-list pattern is particularly tricky and this skill prevents the most common mistakes. Use it for React ...

Preserve React 18 concurrent patterns and adopt React 19 APIs (useTransition, useDeferredValue, Suspense, use(), useOptimistic, Actions) during migration.

Reference for React 19 source-file migration patterns, including API changes, ref handling, and context updates.

Set line length (measure) for prose — capping the maximum width of body text so lines stay in the 45–75 character range that supports comfortable sustained reading. Use when designing article layouts, documentation, email templates, dashboard copy, or any container that holds paragraphs of prose. Line length is the most fundamental readability decision because it directly affects the reader''s eye movement; lines that are too long or too short both cost reading comfort.

Apply the principle of Readability — the ease with which sustained prose can be read, determined by line length, line height, paragraph rhythm, font choice for prose, and visual breathing room. Use when designing long-form content (articles, documentation, books, transcripts), writing email or report layouts, evaluating whether users can comfortably read paragraphs of text. Distinct from legibility (per-character clarity); readability is about the experience of reading sustained prose without...

Debug and optimize AI agents by analyzing reasoning traces, context degradation, tool confusion, instruction drift, repeated task failures, and performance regressions.

Use BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include \"should I X or Y\", \"why is X happening\", \"what's the best approach\", \"what are the tradeoffs\", \"help me think through\", \"diagnose\", \"root cause\", \"plan/design X\", \"what are the implications of\", \"compare these approaches\". Also fires on cross-domain analysis, strategy questions, architecture decisions, or anything requiring multiple factors to be weighed before...

Use when review findings arrive — verify each claim against the codebase and HOTL contracts before making changes. Governs how agents respond to review feedback.

Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.

Code review requires technical evaluation, not emotional performance.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.

Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.

Intelligent refactor command. Triggers: refactor, refactoring, cleanup, restructure, extract, simplify, modernize.

Execute one behavior-preserving structural

Code refactoring workflow - analyze → plan → implement → review → validate

Refactor, simplify, or clean up code for improved maintainability without changing business logic

Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods.

Create a concrete plan before starting a multi-file refactor. Use when the user asks to plan, sequence, scope, or safely execute a refactor across multiple files; always investigate first, output the plan, and wait for confirmation before making code changes.

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

\"RemoFirst debug bundle \\u2014 global HR, EOR, and payroll platform integration.\\n\\ Use when working with RemoFirst for global employment, payroll, or compliance.\\n\\ Trigger with phrases like \\\"remofirst debug bundle\\\", \\\"remofirst-debug-bundle\\\"\\ , \\\"global HR API\\\".\\n\"

\"RemoFirst upgrade migration \\u2014 global HR, EOR, and payroll platform\\ \\ integration.\\nUse when working with RemoFirst for global employment, payroll,\\ \\ or compliance.\\nTrigger with phrases like \\\"remofirst upgrade migration\\\", \\\"\\ remofirst-upgrade-migration\\\", \\\"global HR API\\\".\\n\"

'Choose and implement Replit architecture blueprints: single-file script, modular app, and multi-service. Use when designing new Replit apps, choosing the right architecture scale, or planning migration paths as your app grows. Trigger with phrases like \"replit architecture options\", \"replit blueprint\", \"how to structure replit app\", \"replit monolith vs service\", \"replit app scale\". '

'Diagnose and fix the top Replit errors: container sleep, port binding, Nix failures, DB limits. Use when encountering Replit errors, debugging failed deployments, or troubleshooting workspace and hosting issues. Trigger with phrases like \"replit error\", \"fix replit\", \"replit not working\", \"debug replit\", \"replit broken\", \"replit deploy failed\". '

'Collect Replit diagnostic info for debugging deployments, workspace issues, and support tickets. Use when encountering persistent issues, preparing support tickets, or collecting system state for troubleshooting Replit problems. Trigger with phrases like \"replit debug\", \"replit support bundle\", \"collect replit logs\", \"replit diagnostic\", \"replit troubleshoot\". '

'Execute Replit incident response: triage deployment failures, database issues, and platform outages. Use when responding to Replit-related outages, investigating deployment crashes, or running post-incident reviews for Replit app failures. Trigger with phrases like \"replit incident\", \"replit outage\", \"replit down\", \"replit emergency\", \"replit broken\", \"replit crash\". '