Move IntelliJ JPS test modules to Bazel and diagnose failures that occur only under Bazel. The guide helps trace missing dependencies, plugins, test data, and runfiles, then verify the generated target and migrated tests.

• Migrating a JPS test module to Bazel
• Diagnosing a test failure that occurs only in Bazel
• Checking Bazel dependencies and test data wiring

Write or review Kotlin and Java code in line with IntelliJ project conventions. The guidance covers language choice, formatting, sealed types, threading annotations, and safe handling of control flow exceptions so changes fit the surrounding codebase.

• Writing a new Kotlin file that follows IntelliJ conventions
• Reviewing Java code and checking its style guidance
• Checking formatting, sealed-type handling, or exception handling

Create, amend, or rename IntelliJ commits with messages that follow the project’s ticket and label formats. Keep each commit focused, explain the reason and decision in the body when needed, and pass the message safely through the shell or PowerShell.

• Writing a message for a change linked to a YouTrack ticket
• Preparing a commit message for tests, cleanup, or documentation
• Amending or renaming an existing IntelliJ commit

Compare how Python type checkers interpret a code snippet or file. The script runs selected tools, including ty, pyrefly, basedpyright, mypy, and zuban, then produces a Markdown report with verdicts, timings, and each checker's diagnostic output.

• Comparing type inference for a Python snippet
• Checking whether a Python expression should be a type error
• Reviewing differences among Python type checkers

Shape Compose Desktop UI code by keeping composables focused on rendering and placing application decisions in presenters or coordinators. Get guidance on state ownership, effects, reusable component APIs, lazy-list keys, animation, and performance for individual UI changes.

• Separating screen rendering from application decisions
• Choosing which UI state belongs in composition
• Structuring effects and coroutine work

Audit Compose Desktop code for architecture and runtime issues, including state ownership, effects, coroutine use, lazy lists, animation, and recomposition. It produces prioritized findings with file and line references, while keeping visual design outside the audit scope.

• Auditing state ownership and presenter boundaries in a Compose screen
• Investigating effects, coroutines, or flow collection in desktop UI
• Reviewing recomposition, lazy-list, or animation performance concerns