CtrlK
BlogDocsLog inGet started
Tessl Logo

code-style

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

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Code Style

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

Language

  • 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()

Formatting

  • 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.
Repository
JetBrains/MPS
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.