Skip to content
cccskills
FreePublished on GitHub

icon-resources

Manage IntelliJ icons in Java resource roots by updating generated icon classes or exclusion rules. Follow the documented generation and verification steps, check affected call sites, and update API dumps when a generated field changes the public API.

OriginalShow the original description

Manage IntelliJ icons, generated Icons classes, and icon-robots rules.

JetBrains/intellij-community20,664 stars(GitHub 20,664 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Adding or renaming an IntelliJ icon
  • Fixing stale generated icon classes
  • Excluding an icon from class generation

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- Generated by community/.ai/render-guides.mjs; edit community/.agents/skills/icon-resources/SKILL.md -->

Icon Resources

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.

Generated Icon Classes

  • Icons under resource roots are normally represented by generated *Icons.java classes.
  • Do not add local IconLoader.getIcon(...) wrappers for icons that should be in a generated icon class. Use the generated field directly from production code and tests.
  • If an icon should intentionally be excluded from class generation, add or update an icon-robots.txt rule near the icon resources instead of creating an ad hoc loader.
  • Generated classes include cache keys derived from normalized SVG content. Do not guess cache keys.

How To Update

  1. Prefer running the IDE run configuration Icons processing | Generate icon classes when available.
  2. If the run configuration is unavailable, run the icon-class test and apply the exact generated diff it prints for the affected class: bt.cmd --module intellij.platform.images.build.tests --filter org.jetbrains.intellij.build.images.CommunityIconClassesTest
  3. After applying the generated output, rerun the same test to confirm there are no stale generated icon classes.
  4. Also run the affected module tests or compilation for production call-site changes; the icon-class test validates generated files but does not necessarily compile every icon consumer.
  5. A new or renamed field in a generated icon class changes the public API. Update the API dumps of each module with a changed icon class. In the monorepo, use the api-dump skill to run ApiCheckTest. For AllIcons, update these modules:
    • intellij.platform.util.ui for AllIcons
    • intellij.platform.icons for AllIconDescriptors
    • intellij.platform.jewel.ui for AllIconsKeys

Bazel Status

As 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 bt.cmd for verification. If a generator binary target is added later, prefer that documented Bazel target over the IDE run configuration.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

actions

FreeSummary

Implement or update IntelliJ `AnAction` classes and their `plugin.xml` registrations. Keep labels and descriptions in message bundles, configure optional icons, and launch suspending work through the event coroutine scope so synchronous action handling does not freeze the IDE.

  • Adding a new IntelliJ action
  • Updating an action's registration or icon
  • Moving action labels into a message bundle
JetBrains/intellij-community20.7KUpdated Oct 26, 2026

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
JetBrains/intellij-community20.7KUpdated Oct 26, 2026

code-style

FreeSummary

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
JetBrains/intellij-community20.7KUpdated Oct 26, 2026

commits

FreeSummary

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
JetBrains/intellij-community20.7KUpdated Oct 26, 2026

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
JetBrains/intellij-community20.7KUpdated Oct 26, 2026

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
JetBrains/intellij-community20.7KUpdated Oct 26, 2026

See all skills by JetBrains

Report a problem with this skill