kotlin-developer

Enforce Kotlin coding conventions and project idioms in IntelliJ Platform plugins.

1|1|Updated Sep 29, 2025
One-click install
npx skills add https://github.com/j-plugins/spiral-plugin --skill kotlin-developer-j-plugins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kotlin-developer
Source: https://github.com/j-plugins/spiral-plugin/tree/main/.claude/skills/kotlin-developer
Command: npx skills add https://github.com/j-plugins/spiral-plugin --skill kotlin-developer-j-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures Kotlin code in the repository adheres to the project’s Kotlin/JVM 21 stack and IntelliJ Platform conventions, reducing bugs and ensuring consistency across the codebase.

Core Features & Use Cases

  • Enforces Kotlin coding conventions, nullability rules, and idiomatic patterns across Kotlin files.
  • Guides PSI-based utilities, extension functions, and bundle/icon singleton usage for new and updated code.
  • Use Case: When adding a new feature or refactoring, apply this skill to ensure the code aligns with the project's Kotlin standards.

Quick Start

Apply this skill whenever editing Kotlin files to ensure idiomatic, project-aligned code.

Frequently Asked Questions about kotlin-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Kotlin coding conventions and nullability rules in an IntelliJ plugin?▼

Enforce Kotlin coding conventions by applying this skill to edits, ensuring nullability rules, scope function usage, and PSI-based patterns align with IntelliJ Platform plugin idioms and extension functions.

What is the correct way to use scope functions and PSI helpers when refactoring Kotlin JVM code?▼

Use scope functions and PSI helpers by following repository idioms: leverage extension functions, bundle/icon singletons, and PSI-based patterns to maintain consistency across Kotlin files during refactoring.

Do I need the Kotlin JVM toolchain 21 for IntelliJ Platform plugin development?▼

Yes, the Kotlin JVM toolchain 21 is required. The skill enforces this stack and avoids explicit kotlin-stdlib dependencies to ensure project alignment and reduce bugs across the codebase.

How do I write idiomatic Kotlin for an IntelliJ Platform plugin without explicit kotlin-stdlib dependencies?▼

Write idiomatic Kotlin by relying on the toolchain's implicit stdlib, using extension functions and bundle/icon singletons, while the skill validates that no explicit kotlin-stdlib dependencies are introduced.

What are the limitations when applying project-specific Kotlin idioms to new features?▼

The skill is limited to Kotlin files within the IntelliJ Platform plugin context, enforcing nullability rules, scope functions, and PSI patterns, but does not address cross-language or non-JVM Kotlin targets.