Menu
Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
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.
How to manage module dependencies in IntelliJ codebase. Use when adding or modifying module dependencies in iml files.
Guidelines for structuring and developing IntelliJ remote development modules. Use when working on Remote Development features.
| name | code-style |
| description | Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance. |
Follow the IntelliJ Coding Guidelines with these IntelliJ-specific rules.
@ApiStatus.Experimentalcommunity/platform/build-scripts/kotlin-style-recommendations.md for build-scripts code:
@JvmField for internal data class fields.put()/.get() instead of [] operatorHashMap/HashSet/LinkedHashMap instead of mutableMapOf()/mutableSetOf()/rustrover directory you must always use standard Kotlin formatting rules with 4 spaces indentation.