IntelliJ Plugin Development

What problem does it solve?

Building IntelliJ IDEA / Android Studio plugins is complex and easy to get wrong, especially around Gradle setup, plugin.xml wiring, threading/EDT rules, UI component requirements, and secure credential handling.

Core Features & Use Cases

• End-to-end plugin scaffold guidance: Uses IntelliJ Platform Gradle Plugin 2.x with Kotlin and Gradle configuration patterns.
• Correct plugin wiring: Covers plugin.xml essentials, tool window registration, and service registration approaches using @Service.
• Production-grade UI and lifecycle patterns: Enforces IntelliJ wrapper components, ActionToolbar usage, EDT/threading model, Disposable lifecycle, lazy tree loading, and settings persistence patterns.
• Security and reliability guardrails: Provides a security audit prompt checklist plus practical guidance for safe credential storage (PasswordSafe) and avoiding common injection/logging mistakes.
• Use case: When you need a custom tool window and actions in Android Studio to automate project workflows, this skill helps you implement the UI, background execution, settings, and safe integration points.

Quick Start

Ask for a complete IntelliJ plugin build plan by providing the target IDE (Community/Ultimate and version) plus the plugin features you want, then request the exact Gradle and plugin.xml structure needed.