القائمة
Work with IntelliJ icon resources, generated *Icons.java classes, icon-robots.txt rules, IconLoader wrappers, or CommunityIconClassesTest failures.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guide for writing UI tests using IDE Starter and UI Driver frameworks. Use when creating or modifying UI tests or when user ask to implement test case from testops.
Guide for writing UI tests using IDE Starter and UI Driver frameworks. Use when creating or modifying UI tests or when user ask to implement test case from testops.
Use when building, modifying, troubleshooting, or extending JetBrains Jewel Markdown rendering in Compose Desktop or IntelliJ-plugin UI: Markdown previews, Markdown chat output, GFM tables/alerts/strikethrough/autolinks/images, custom Markdown syntax, custom renderers, or MarkdownStyling.
Use when building, modifying, troubleshooting, or extending JetBrains Jewel Markdown rendering in Compose Desktop or IntelliJ-plugin UI: Markdown previews, Markdown chat output, GFM tables/alerts/strikethrough/autolinks/images, custom Markdown syntax, custom renderers, or MarkdownStyling.
Design, review, and refactor Kotlin or Java Swing UI in IntelliJ-based IDEs as isolated feature components with explicit state, semantic intents, unidirectional data flow, EDT-safe asynchronous work, and lifecycle ownership. Use when creating or changing Swing panels, dialogs, tool windows, or Kotlin UI DSL components; separating UI from services or business logic; fixing widget-driven state, blocking EDT work, listener leaks, or oversized god panels; or reviewing Swing UI architecture without overengineering small components.
Design, review, and refactor Kotlin or Java Swing UI in IntelliJ-based IDEs as isolated feature components with explicit state, semantic intents, unidirectional data flow, EDT-safe asynchronous work, and lifecycle ownership. Use when creating or changing Swing panels, dialogs, tool windows, or Kotlin UI DSL components; separating UI from services or business logic; fixing widget-driven state, blocking EDT work, listener leaks, or oversized god panels; or reviewing Swing UI architecture without overengineering small components.
| name | icon-resources |
| description | Work with IntelliJ icon resources, generated *Icons.java classes, icon-robots.txt rules, IconLoader wrappers, or CommunityIconClassesTest failures. |
Use this skill when adding, renaming, moving, deleting, or referencing icons under a Java resource root, or when a failure mentions generated icon classes or icon-robots.txt.
*Icons.java classes.IconLoader.getIcon(...) wrappers for icons that should be in a generated icon class. Use the generated field directly from production code and tests.icon-robots.txt rule near the icon resources instead of creating an ad hoc loader.Icons processing | Generate icon classes when available../tests.cmd --module intellij.platform.images.build.tests --test org.jetbrains.intellij.build.images.CommunityIconClassesTestAs of this guide, icon class generation is not exposed as a Bazel runnable target. The package @community//platform/build-scripts/icons contains library and test targets, but no binary target:
bazel query 'kind(".*binary.*", @community//platform/build-scripts/icons:all)'
Use Bazel-backed tests.cmd for verification. If a generator binary target is added later, prefer that documented Bazel target over the IDE run configuration.