plugin-icons
Skill1 starsChanged 2 days agoMITView on GitHub
Designs, draws, renders, reviews and checks the directory listing icon of every plugin in this marketplace, on the owner-approved shared frame. Use whenever a new plugin needs its icon, an icon should be redesigned, re-rendered or reviewed, a plugin is renamed or removed and its icon source must follow, the consistency check reports PC-09, or plugins are being prepared for Anthropic's directory, even if the request only says "make it a logo" or "it needs a picture".
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- referencesSkill
- docs-maintenanceSkill
- plugin-catalog-changesSkill
- plugin-releasesSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
No marks of others: no Claude, Anthropic or third-party logo or lookalike.
- Distinctive: line 34
Never use an AI image generator or a raster file as a source: the icon could not be edited or rendered again identically, and generated …
- Distinctive: line 50
Read the images yourself before sending them, and fix a glyph that blurs at 32 px or looks like a sibling at 48 px.
- Distinctive: line 60
Remove a plugin: delete its source in the same change, or PC-09 reports it as stray.
- Very specific: line 61
Audit: run npm run check:consistency -- --offline and review the contact sheet at 160, 48 and 32 px against the style above.
- Very specific: line 62
Prepare a directory submission: run claude plugin validate --strict --profile directory plugins/<plugin>, then, in the developer portal's …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plugin icons
Each plugin ships one icon, plugins/<plugin>/.claude-plugin/icon.png, which Anthropic's directory shows on the plugin's listing. All 22 icons share one frame and one style, so a new icon has to look like part of the family, and nothing about it can be generated in a way that can't be reproduced.
The pieces
| Piece | Path | Ships to users |
| Source, one per plugin | scripts/generators/plugin-icons/<plugin>.svg | No |
| Renderer | npm run icons:render [-- <plugin>...] (scripts/generators/plugin-icons.mjs) | No |
| Rendered icon | plugins/<plugin>/.claude-plugin/icon.png, 1024 × 1024, 256 colors, about 50 KB | Yes |
| Declaration | "icon": "./.claude-plugin/icon.png" in plugin.json, next to documentationUrl, supportUrl and privacyPolicyUrl | Yes |
| Check | npm run check:consistency (PC-09 icon and source, PC-10 listing URLs) | No |
The renderer needs Playwright's Chromium, ImageMagick and the JetBrains Mono font; the check needs none of them. claude plugin validate only reports an icon path that isn't a file, so PC-09 is the only check of size, shape and source.
The style
The owner approved this style; keep every new icon inside it:
- Frame: a navy rounded square with a faint grid and a thin light border. Every source carries the same frame markup, byte for byte, up to and including the
<rect … rx="212" …/>border line. Never edit the frame in one icon. - Glyph: one flat, centered symbol that names what the plugin does, drawn after the border line and filled or stroked with the turquoise gradient
url(#g)(#5EEAD4to#14B8A6). Keep it inside roughly x 200 to 824 and y 200 to 840, the span the gradient covers. - Lines: strokes of about 44 to 56 units with
stroke-linecap="round"andstroke-linejoin="round", so a glyph reads at 32 px. - Details on the glyph: navy
#0F1E33at 0.25 to 0.45 opacity for cut-outs and inner lines, white at low opacity for highlights. - Text: none, except a short language label (
$_,.py,.ts, a version digit) in JetBrains Mono for a language plugin. - No marks of others: no Claude, Anthropic or third-party logo or lookalike. The directory holds listings that look like a known brand.
- Distinct: at 48 px the new glyph must not be mistaken for another plugin's icon in the family.
Never use an AI image generator or a raster file as a source: the icon could not be edited or rendered again identically, and generated images tend to imitate known logos.
Make a new plugin's icon
- Choose the glyph from the plugin's purpose (its
descriptionand category), and show the owner one or two ideas in words before drawing. - Start from the closest existing source: copy it to
scripts/generators/plugin-icons/<plugin>.svg, keep everything up to and including the border line, and replace only what follows it with the new glyph, closing with</g></svg>. Copying keeps the frame identical without a second template to drift. - Render it:
npm run icons:render -- <plugin>. It writesplugins/<plugin>/.claude-plugin/icon.pngand stops with the reason on a missing source or tool. Show the owner a contact sheet of the new icon next to the whole family at review sizes, and wait for approval before any commit. From the repository root, with a scratchpad folder as
<out>:args=(); for d in plugins/*/; do args+=(-label "$(basename "$d")" "$d.claude-plugin/icon.png"); done montage "${args[@]}" -resize 160x160 -geometry +14+10 -tile 6x -background white -pointsize 12 <out>/icons-160.png montage plugins/<plugin>/.claude-plugin/icon.png -resize 48x48 -geometry +8+8 <out>/new-48.png montage plugins/<plugin>/.claude-plugin/icon.png -resize 32x32 -geometry +8+8 <out>/new-32.pngRead the images yourself before sending them, and fix a glyph that blurs at 32 px or looks like a sibling at 48 px.
- Declare it in
plugin.jsonas"icon": "./.claude-plugin/icon.png", with the three listing URLs in the same order as the other manifests. - Check it:
npm run check:consistency -- --offlinereports no PC-09 or PC-10 for the plugin, andclaude plugin validate --strict --profile directory plugins/<plugin>passes. - Commit the source (maintainer scope, no pull request) and the plugin's files separately. The icon and the declaration are part of the plugin's next version: version it with the
plugin-releasesskill; for a new plugin they ship in its0.1.0.
Other icon tasks
- Redesign one icon: steps 1 to 6 on its existing source. A shipped plugin's new
icon.pngchanges the plugin, so it needs a patch bump and a pull request. - Re-render the family (after a font or renderer change):
npm run icons:render, thengit status plugins. Unchanged sources must give byte-identical PNGs; any other difference is a regression to explain to the owner before committing. - Rename a plugin: with the
plugin-catalog-changesskill, rename its source to the new name in the same change, or PC-09 reports a missing source and a stray one. - Remove a plugin: delete its source in the same change, or PC-09 reports it as stray.
- Audit: run
npm run check:consistency -- --offlineand review the contact sheet at 160, 48 and 32 px against the style above. - Prepare a directory submission: run
claude plugin validate --strict --profile directory plugins/<plugin>, then, in the developer portal's Listing details step, ask the owner to check the icon preview. Whether the portal crops the transparent rounded corners is undocumented; report what the preview shows.
Size limits
PC-09 enforces a square PNG of 512 to 2048 px under 2 MB. These limits come from the text of claude plugin validate 2.1.318; no current official page states them, so treat them as this project's convention and report any portal finding that contradicts them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

