feat: add a plugin icon
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- tooling
Research direction
Start by reading plugin.json and marketplace.json, then check Claude Code's documented icon fields; the issue does not name the icon file or a specific field. Add a small square SVG or PNG in the repo, reference it in both manifests, and run claude plugin validate . and npm test to confirm the acceptance criteria.
Written by the indexing model from the issue text.
Description
What
The plugin has no icon in the plugin manager or on its marketplace entry.
Why
An icon makes the plugin easier to spot in /plugin and in screenshots of the README.
Acceptance criteria
- A small square icon (SVG or PNG) lives in the repo.
- plugin.json and marketplace.json reference it in whatever field Claude Code documents for icons.
-
claude plugin validate .andnpm teststill pass.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from devmaxxx/stackwise
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
bug eval
Difficulty 3/5 1-2 days Newbie friendliness 66/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug eval
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in devmaxxx/stackwise
Similar issues
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
good first issue tests
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day