Claude Skills by thedixitjain

| Use when migrating from Zendesk/Freshdesk/HelpScout to Intercom, bulk-importing contacts, or re-platforming to Intercom with the contacts, conversations, and articles APIs. Trigger with phrases like \"migrate to intercom\", \"intercom migration\", \"import contacts to intercom\", \"switch to intercom\", \"zendesk to intercom\", \"intercom data import\".

| Optimize Intercom API performance with caching, search optimization, and pagination. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Intercom integrations. Trigger with phrases like \"intercom performance\", \"optimize intercom\", \"intercom latency\", \"intercom caching\", \"intercom slow\", \"intercom pagination\".

'Implement Intercom reference architecture with layered project structure. Use when designing new Intercom integrations, reviewing project structure, or establishing architecture standards for Intercom applications. Trigger with phrases like \"intercom architecture\", \"intercom project structure\", \"how to organize intercom\", \"intercom layout\", \"intercom design patterns\". '

'Apply production-ready intercom-client SDK patterns for TypeScript. Use when implementing Intercom integrations, refactoring SDK usage, or establishing team coding standards for Intercom API calls. Trigger with phrases like \"intercom SDK patterns\", \"intercom best practices\", \"intercom code patterns\", \"idiomatic intercom\", \"intercom typescript\". '

| Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely. Use when a project is pinned to an old intercom-client release, when the v5 CommonJS API must move to the v6 TypeScript rewrite, or when detecting breaking changes in a new Intercom release before shipping. Trigger with phrases like \"upgrade intercom\", \"intercom migration\", \"intercom breaking changes\", \"update intercom SDK\", \"intercom API version\".

Use when targeting International Conference for High Performance Computing, Networking, Storage and Analysis (SC) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for HPC flagship.

Use when targeting International Symposium on Computer Architecture (ISCA) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for computer architecture flagship.

This skill should be used when the user asks to \"design interview processes\", \"create hiring pipelines\", \"calibrate interview loops\", \"generate interview questions\", \"design competency matrices\", \"analyze interviewer bias\", \"create scoring rubrics\", \"build question banks\", or \"optimize hiring systems\". Use for designing role-specific interview loops, competency assessments, and hiring calibration systems.

Systematic debugging with root cause investigation. (gstack)

Use when designing or auditing IPSN-lineage evaluations, covering real testbeds and deployments, ground-truth instrumentation, energy/latency/footprint measurement on real hardware, on-device/TinyML profiling, estimation-theoretic baselines and bounds, and matching evidence to the shape of each sensing claim across the IP and SPOTS tracks.

>- Problem scoping with Is/Is-Not for 8D D2 problem description, CAPA investigation, or hypothesis elimination. Defines the precise boundary by contrasting what IS observed vs what IS NOT — eliminating hypotheses that don't fit the pattern. A Ford-originated automotive technique used in every structured quality investigation.

Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind rules, and exploiting ISCA's unlimited reference pages.

Use when reasoning about how an ISCA submission is evaluated — the two-round review structure with December and February reviewer waves, what the combined rebuttal-and-revision window means for decisions, PC-meeting dynamics at a flagship architecture venue, and how to read the eventual outcome.

Use when deciding whether a project belongs at ISCA, the ACM/IEEE flagship architecture symposium — testing whether the machine itself is the contribution, choosing between ISCA's November gate and the MICRO, HPCA, and ASPLOS seats in the architecture year, and weighing the main track against the industry track.

Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.

Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say \"migrate my labels to issue fields\", \"migrate project fields to issue fields\", \"convert labels to issue fields\", \"copy project field values to issue fields\", or ask about adopting issue fields. Issue fields are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, sea...

| Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the standard chain with a PR exit. Trigger with /hyperflow:issue, \"work on issue #N\", \"fix this issue <url>\", \"implement this issue\", \"triage issue #N and raise a PR\".

>- Skill Refiner, the eval-guided improvement loop for SKILL.md files. Runs the bootstrap, score, propose, apply, and status cycle as a thin wrapper over the published @intentsolutions/refiner CLI, proposing safe, minimal, bounded SKILL.md edits and accepting an edit only when a held-out eval score strictly improves with no regression on any other case. Ships a 3-layer cost-tiered hook architecture (sinker, line, hook) that gates skill quality at edit time, end of turn, and commit time. Use w...

Refactoring using Extract Methods in Java Language

Refactoring using Remove Parameter in Java Language

Language-specific super-code guidelines for java.

You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N

Migrate Java code from javax.* to jakarta.* namespace. Use when upgrading to Tomcat 11, Jakarta EE 10, or when javax imports are detected in the codebase.

Use when designing and analyzing a solution algorithm for a 《管理科学学报》 (Journal of Management Sciences in China) manuscript — giving exact / heuristic / decomposition methods with complexity analysis and, for iterative methods, convergence proofs. \"It runs fast\" is not analysis. Use after the model and properties are established.

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

'Diagnose and fix Juicebox API errors. Trigger: \"juicebox error\", \"fix juicebox\", \"debug juicebox\". '

'Collect Juicebox debug evidence. Trigger: \"juicebox debug\", \"juicebox support ticket\". '

'Juicebox incident response. Trigger: \"juicebox incident\", \"juicebox outage\". '

'Migrate to Juicebox from other tools. Trigger: \"switch to juicebox\", \"migrate to juicebox\". '

'Optimize Juicebox performance. Trigger: \"juicebox performance\", \"optimize juicebox\". '

'Implement Juicebox reference architecture. Trigger: \"juicebox architecture\", \"recruiting platform design\". '

'Plan Juicebox SDK upgrades. Trigger: \"upgrade juicebox\", \"juicebox migration\". '

Master Julia 1.10+ with modern features, performance optimization, multiple dispatch, and production-ready practices.

Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.

Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on \"review my diff\", \"check complexity\", \"am I overcomplicating this\", \"karpathy check\", \"before I commit\", or any code quality concern where the LLM might be overcoding.

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

'Diagnose and fix common Klaviyo API errors and exceptions. Use when encountering Klaviyo 4xx/5xx errors, debugging failed requests, or troubleshooting SDK integration issues. Trigger with phrases like \"klaviyo error\", \"fix klaviyo\", \"klaviyo not working\", \"debug klaviyo\", \"klaviyo 400\", \"klaviyo 429\". '

'Collect Klaviyo debug evidence for support tickets and troubleshooting. Use when a Klaviyo integration is failing, when preparing a support ticket, or when collecting diagnostic information for a Klaviyo API problem. Trigger with phrases like \"klaviyo debug\", \"klaviyo support bundle\", \"collect klaviyo logs\", \"klaviyo diagnostic\", \"klaviyo troubleshoot\". '

| Execute Klaviyo incident response procedures with triage, mitigation, and postmortem. Use when responding to Klaviyo-related outages, investigating API errors (401/403/429/5xx), or running post-incident reviews for Klaviyo integration failures on an on-call rotation. Trigger with phrases like \"klaviyo incident\", \"klaviyo outage\", \"klaviyo down\", \"klaviyo on-call\", \"klaviyo emergency\", \"klaviyo broken\".

'Use when you are moving an email/CDP stack onto Klaviyo — off the deprecated v1/v2 APIs, off a competitor ESP (Mailchimp, SendGrid), or re-platforming gradually with the strangler fig pattern — and need field mapping, batch import, and post-migration validation. Trigger with phrases like \"migrate to klaviyo\", \"klaviyo migration\", \"switch to klaviyo\", \"klaviyo replatform\", \"mailchimp to klaviyo\", \"legacy to klaviyo\", \"v1 to v2 klaviyo\". '

| Optimize Klaviyo API performance with caching, batching, and pagination tuning. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Klaviyo integrations. Trigger with phrases like \"klaviyo performance\", \"optimize klaviyo\", \"klaviyo latency\", \"klaviyo caching\", \"klaviyo slow\", \"klaviyo batch\".

'Implement Klaviyo reference architecture with best-practice project layout. Use when designing new Klaviyo integrations, reviewing project structure, or establishing architecture standards for email/SMS marketing applications. Trigger with phrases like \"klaviyo architecture\", \"klaviyo project structure\", \"klaviyo design\", \"how to organize klaviyo\", \"klaviyo layout\". '

'Apply production-ready Klaviyo SDK patterns for the klaviyo-api package. Use when implementing Klaviyo integrations, refactoring SDK usage, or establishing team coding standards for Klaviyo API calls. Trigger with phrases like \"klaviyo SDK patterns\", \"klaviyo best practices\", \"klaviyo code patterns\", \"idiomatic klaviyo\", \"klaviyo wrapper\". '

'Upgrade Klaviyo SDK versions and migrate between API revisions. Use when upgrading the klaviyo-api package, migrating from v1/v2 legacy APIs to the current REST API, or handling breaking changes between revisions. Trigger with phrases like \"upgrade klaviyo\", \"klaviyo migration\", \"klaviyo breaking changes\", \"update klaviyo SDK\", \"klaviyo API revision\". '

'Set up logging and debugging for Kling AI API integrations. Use when troubleshooting video generation or building observability. Trigger with phrases like ''klingai debug'', ''kling ai logging'', ''klingai troubleshoot'', ''debug kling video generation''. '

'Optimize Kling AI for speed, quality, and cost efficiency. Use when improving generation times or finding optimal settings. Trigger with phrases like ''klingai performance'', ''kling ai optimize'', ''faster klingai'', ''klingai quality settings''. '

'Production reference architecture for Kling AI video generation platforms. Use when designing scalable systems. Trigger with phrases like ''klingai architecture'', ''kling ai system design'', ''video platform architecture'', ''klingai production setup''. '

'Production SDK patterns for Kling AI: client wrapper, retry logic, async polling, and error handling. Use when building robust integrations. Trigger with phrases like ''klingai sdk'', ''kling ai client'', ''klingai patterns'', ''kling ai wrapper''. '

'Migrate between Kling AI model versions safely. Use when upgrading from v1.x to v2.x or adopting new features. Trigger with phrases like ''klingai upgrade'', ''kling ai migrate'', ''klingai version update'', ''upgrade kling model''. '