icon-set-generator
Generate cohesive, project-specific SVG icon sets with enforced visual consistency.
Works with
3
total installs
3
this week
697
GitHub stars
0
upvotes
Install Skill
Run in your terminal
3
installs
3
this week
697
stars
What it does
Builds custom icon sets from a shared style specification, ensuring identical stroke weight, corner treatment, and visual density across all icons
Supports five preset styles (Clean, Sharp, Soft, Minimal, Bold) tailored to different project aesthetics; recommends based on industry and brand vibe
Includes industry-specific icon suggestions organized by category (navigation, communication, trust, action
Installation Guide
How to use icon-set-generator on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
icon-set-generator
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches icon-set-generator from jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate icon-set-generator. Access via /icon-set-generator in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
Icon Set Generator
Generate custom, visually consistent SVG icon sets tailored to specific projects. Each set is built from a shared style specification so every icon looks like it belongs with the others — same stroke weight, same corner treatment, same visual density.
Why This Matters
Generic icon libraries (Lucide, Heroicons) are great but every site using them looks similar. A custom icon set gives a project distinct visual identity. The hard part is consistency — drawing 20+ icons individually causes style drift. This skill solves that by defining style rules once and enforcing them across every icon.
Workflow
Step 1: Understand the Project
Ask about the project. You need enough to suggest icons and pick a style:
- What's the business/project? (industry, name, vibe)
- Any brand guidelines or colour palette? (informs style choices even though SVGs use currentColor)
- What feel? (modern, friendly, corporate, minimal, bold)
- Roughly how many icons? (typical small site: 15-25)
A brief like "plumber in Newcastle, modern feel" is enough to proceed. Don't over-interview.
Step 2: Suggest Icons
Read references/industry-icons.md for industry-specific suggestions. Organise into groups:
- Navigation — menu, close, arrows, search
- Communication — phone, email, location, clock
- Trust — star, shield, award, users
- Actions — download, share, calendar, form
- Industry-Specific — icons unique to this business type
Present the list. Let the user add, remove, or rename before generating.
Step 3: Define the Style Spec
Read references/style-presets.md for full preset definitions. Pick one as starting point:
| Preset | Best For | Stroke | Caps/Joins | Corners |
|---|---|---|---|---|
| Clean | Most business sites | 1.5px | round/round | 2px |
| Sharp | Corporate/technical | 1.5px | square/miter | 0px |
| Soft | Friendly/approachable | 2px | round/round | 4px |
| Minimal | Elegant/editorial | 1px | round/round | 0px |
| Bold | High impact/accessible | 2.5px | round/round | 2px |
Tell the user which preset you're recommending and why, then confirm.
Step 4: Generate the Icons
Generate every icon following the SVG Rules below. Output to an icons/ directory in the project root (or the user's preferred location).
Read references/svg-examples.md before generating — it contains reference implementations showing the right level of complexity and how to handle common icon shapes.
Generate in batches of ~5. After each batch, visually review for consistency before continuing. After all icons are done, create the preview page and style-spec.json.
Step 5: Deliver
Output structure:
icons/
├── style-spec.json
├── preview.html
├── home.svg
├── phone.svg
└── ...
Present preview.html first so the user sees the complete set visually.
SVG Rules
Every icon in a set MUST follow all of these. Even small inconsistencies — a slightly different stroke width, a rounded corner where others are sharp — make the set look amateur.
SVG Template
Every icon uses this exact outer structure:
<svg xmlns="http://www.w3.org/2000/svg"
width="{grid}" height="{grid}"
viewBox="0 0 {grid} {grid}"
fill="none"
stroke="currentColor"
stroke-width="{strokeWidth}"
stroke-linecap="{strokeLinecap}"
stroke-linejoin="{strokeLinejoin}">
<!-- icon paths here -->
</svg>
Hard Rules
-
currentColoronly — Never hardcode colours. SVGs inherit colour from CSS. Nofill="#000"orstroke="blue". If a shape needs fill, usefill="currentColor". -
Identical viewBox — Every icon uses the same
viewBox. No exceptions. -
Identical root stroke attributes —
stroke-width,stroke-linecap,stroke-linejoinon the<svg>element must match across all icons. Override on individual elements only when truly necessary. -
No transforms on root — No
translate,rotate,scale. Bake positioning into coordinates. -
No IDs or classes — Keep SVGs clean for external styling.
-
Coordinate precision — Max 2 decimal places. Snap to half-pixel grid (e.g.
12,12.5, not12.333). -
Consistent padding — Maintain configured padding from viewBox edge. For 24px grid with 2px padding, draw within 2–22 coordinate range.
-
Minimal elements — Fewest
<path>,<circle>,<rect>,<line>elements practical. Simpler = smaller + faster rendering. -
Visual centring — Appear visually centred, not just mathematically centred. A leftward arrow shifts slightly right. A house with a chimney adjusts for asymmetry.
Optical Corrections
Subtle but essential for professional results:
- Curved stroke compensation: Curves appear thinner than straight lines at same stroke width. For primarily curved icons (phone, globe), make paths slightly larger rather than changing stroke width.
- Pointed shape overshoot: Arrows, chevrons, triangles extend ~0.5px beyond where a square would stop to appear the same size.
- Visual weight balancing: Simple icons (single chevron) look lighter than complex ones (gear). Make simpler icons slightly larger in the grid, or use slightly more substantial paths. No icon should look noticeably lighter or heavier than the others.
style-spec.json
{
"name": "project-name-icons",
"preset": "clean",
"grid": 24,
"strokeWidth": 1.5,
"strokeLinecap": "round",
"strokeLinejoin": "round",
"cornerRadius": 2,
"padding": 2,
"opticalBalance": true,
"iconCount": 20,
"icons": ["home", "phone", "email"],
"generated": "2026-02-15"
}
Preview Page
Generate a self-contained HTML file displaying all icons for visual review. Read references/preview-template.md for the template. Requirements:
- Grid of all icons at native size (24px) with labels
- Same grid at 2x (48px) for detail inspection
- Dark background section (white on dark) for contrast check
- Style spec summary at top
- Inline CSS, no dependencies — just open in browser
- Inline all SVGs directly into the HTML (don't reference external files)
Quality Checklist
Verify every item before delivering:
- All SVGs have identical
viewBox,stroke-width,stroke-linecap,stroke-linejoin - All SVGs use
currentColorexclusively - Visual weight is balanced across the set
- Padding is consistent (nothing touching viewBox edge)
- All icons visually centred
- Filenames are lowercase kebab-case (
arrow-right.svg) - Preview HTML renders all icons correctly
- style-spec.json is accurate and lists all icons
Reference Files
Read these before generating:
references/style-presets.md— Detailed preset definitions and selection guidancereferences/industry-icons.md— Industry-specific icon suggestionsreferences/preview-template.md— HTML template for the preview pagereferences/svg-examples.md— Example SVGs showing proper construction at various complexity levels
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
wordpress-elementor
84jezweb/claude-skills
grill-me
388mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
99pproenca/dot-skills
write-a-prd
91mattpocock/skills
Reviews
- AAmina Gonzalez★★★★★Dec 28, 2024
I recommend icon-set-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMin Thompson★★★★★Dec 28, 2024
icon-set-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- BBenjamin Agarwal★★★★★Dec 20, 2024
Solid pick for teams standardizing on skills: icon-set-generator is focused, and the summary matches what you get after install.
- DDhruvi Jain★★★★★Dec 4, 2024
Useful defaults in icon-set-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- OOshnikdeep★★★★★Nov 23, 2024
icon-set-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- MMin Haddad★★★★★Nov 19, 2024
Keeps context tight: icon-set-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- KKofi Gill★★★★★Nov 19, 2024
Useful defaults in icon-set-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- KKiara Verma★★★★★Nov 11, 2024
We added icon-set-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- GGanesh Mohane★★★★★Oct 14, 2024
Keeps context tight: icon-set-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- MMin Garcia★★★★★Oct 10, 2024
icon-set-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 39
Discussion
Comments — not star reviews- No comments yet — start the thread.