Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Run a Python file or snippet through the real third-party type checkers (ty, pyrefly, basedpyright, mypy, zuban) via uvx and collate their output into one Markdown report. Use when evaluating how a type should be inferred, debugging PyCharm code-insight / type-engine behaviour, or checking where the external checkers agree or disagree on a snippet.
Guide for writing UI tests using IDE Starter and UI Driver frameworks. Use when creating or modifying UI tests or when user ask to implement test case from testops.
Extract an optional dependency from a plugin module into a new content module. Use when making a library dependency optional by separating integration code into its own module.
End-to-end workflow to fix a `_LastInSuiteTest.testProjectLeak` failure reported by TeamCity. Given a TC hashcode / leak diagnostic, this skill drives the full cycle — identify the culprit test, reproduce the leak locally 10x with `tests.cmd`, analyze every unique retention chain observed, apply fixes per chain, and verify by rerunning the leak-hunter until it stops firing. Use when the user asks to fix (not just investigate) a project leak surfaced by TC. Self-contained: does not depend on other skills.
Work with IntelliJ icon resources, generated *Icons.java classes, icon-robots.txt rules, IconLoader wrappers, or CommunityIconClassesTest failures.
Generate New UI icons for the IntelliJ Platform. Use when creating, editing, or reviewing SVG icons for the New UI — action icons (16×16), tree-node icons (16×16), tool-window icons (16×16 + 20×20), main-toolbar icons (20×20), editor-gutter icons (12×12 / 14×14), status-bar icons, and other system icons. Produces a light and a `_dark` variant that share geometry and use the canonical New UI palette so the icons theme correctly in both themes.
Inspect the live runtime state of a currently running IntelliJ IDE through the MCP get_ide_diagnostics tool. Use only for IDE process diagnostics such as performance triage, UI freezes, high CPU, blocked threads, coroutine dumps, or thread dumps when the user wants current evidence from the running IDE, not for general debugging, generic issue diagnosis, build/test failures, logs, or MCP server self-diagnostics.
Design, review, and refactor Kotlin or Java Swing UI in IntelliJ-based IDEs as isolated feature components with explicit state, semantic intents, unidirectional data flow, EDT-safe asynchronous work, and lifecycle ownership. Use when creating or changing Swing panels, dialogs, tool windows, or Kotlin UI DSL components; separating UI from services or business logic; fixing widget-driven state, blocking EDT work, listener leaks, or oversized god panels; or reviewing Swing UI architecture without overengineering small components.
How to manage module dependencies in IntelliJ codebase. Use when adding or modifying module dependencies in iml files.
Pluginize a Product DSL module set by hand-writing a wrapper plugin module next to its feature modules. Use when promoting modules out of an aggregate module set (e.g. `essential`, `ide.common`) into a bundled plugin so products can include or omit them through normal plugin wiring, when updating bundled plugin registration for such a wrapper, or when fixing tests whose plugin loading logs show a missing wrapper plugin for a former module set.