extract-module
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.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
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.
Work with IntelliJ icon resources, generated *Icons.java classes, icon-robots.txt rules, IconLoader wrappers, or CommunityIconClassesTest failures.
Prepare a Jewel pull request for the intellij-community repository. Validates commit message format, runs local CI checks (detekt, tests, API dumps, Metalava), ensures the branch is squashed to a single commit, checks for visual change screenshots, drafts release notes, and suggests a PR title and description. Optionally creates the PR via gh. Use when the user is ready to submit or review a Jewel contribution.
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.
Query IntelliJ Product DSL module sets, products, plugin graph ownership, dependencies, reachability, loading rules, validation, and packaging composition by running the repo's Bazel `//platform/buildScripts:plugin-model-tool` target with JSON requests. Use instead of the retired PluginModelAnalyzer MCP server whenever Codex needs module/product/plugin-model facts in the IntelliJ monorepo.
Working with pseudo-KMP (Kotlin Multiplatform) modules in the IntelliJ monorepo. Use when creating, migrating, or modifying modules that use the expects-compiler-plugin for expect/actual emulation in JPS projects.