Code Style

SkillDev tools

Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Code Style skill

What this skill tells your AI

The instructions your AI receives, as published by jetbrains/mps in .agents/skills/code-style/SKILL.md and read by ahel’s review.

Follow the IntelliJ Coding Guidelines with these IntelliJ-specific rules.

ALWAYS use Kotlin for new files - Only use Java when modifying existing Java code
Use idiomatic Kotlin: extension functions, data classes, null safety
Mark experimental APIs with @ApiStatus.Experimental
Build scripts Kotlin style: Follow community/platform/build-scripts/kotlin-style-recommendations.md for build-scripts code:
- Use @JvmField for internal data class fields
- Use .put()/.get() instead of [] operator
- Use explicit HashMap/HashSet/LinkedHashMap instead of mutableMapOf()/mutableSetOf()

Indentation: 2 spaces (4 for Go files)
Line length: 140 characters max
Braces: else/catch/finally on new lines
Only in /rustrover directory you must always use standard Kotlin formatting rules with 4 spaces indentation.

Advanced