favicon-generator▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides favicon and app icon implementation for brand consistency across browser tabs, bookmarks, mobile home screens, and Google Search results. Favicons help users identify sites; missing or incorrect icons hurt trust.
Components: Favicon
Guides favicon and app icon implementation for brand consistency across browser tabs, bookmarks, mobile home screens, and Google Search results. Favicons help users identify sites; missing or incorrect icons hurt trust.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand and visual identity.
Identify:
- Tech stack: Next.js, WordPress, static HTML, etc.
- PWA: Is the site a PWA or planning to be?
- Existing assets: Logo, icon files
Required Sizes
| Size | Use |
|---|---|
| 16x16 | Browser tabs, standard displays |
| 32x32 | Retina/HiDPI browser tabs |
| 180x180 | Apple Touch Icon (iOS home screen); no transparency |
| 192x192 | Android Chrome home screen, PWA launcher |
| 512x512 | PWA splash screens, adaptive icons |
Optional: 48x48, 96x96, 120x120, 152x152, 167x167, 256x256 for broader coverage.
Formats
| Format | Use |
|---|---|
| SVG | Modern browsers; scalable; supports dark mode via media queries; lightweight |
| PNG | High-DPI; explicit sizes; easy to generate; required for Apple Touch Icon |
| ICO | Legacy; bundles multiple sizes; fallback for older browsers |
Recommended: Provide SVG + PNG fallbacks. Never skip Apple Touch Icon (180x180); iOS shows a generic screenshot without it.
Google Search (SERP Display)
See serp-features for SERP feature types and optimization.
Favicons can appear in Google Search results next to your site's listings. Google Search Central requirements:
| Requirement | Guideline |
|---|---|
| Placement | Add <link rel="icon" href="/path/to/favicon.ico"> to homepage header |
| One per hostname | One favicon per hostname; example.com and code.example.com are separate; example.com/sub-site shares the same favicon |
| Crawlability | Googlebot-Image must crawl favicon; Googlebot must crawl homepage; do not block either in robots.txt |
| Shape | Square (1:1 aspect ratio); minimum 8x8px; preferably >48x48px for quality across platforms |
| Stable URL | Do not change favicon URL frequently |
| Appropriate | No inappropriate content (pornography, hate symbols); Google may replace with default icon |
| Timing | Crawling can take days to weeks; use Search Console URL Inspection to request indexing |
Supported rel values: icon, shortcut icon, apple-touch-icon, apple-touch-icon-precomposed. href can be relative (/favicon.ico) or absolute; favicon can be hosted on CDN.
Implementation
HTML Link Tags
<link rel="icon" href="/favicon.ico" sizes="any">
<link rel="icon" href="/icon.svg" type="image/svg+xml">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
Next.js
Place in /app: favicon.ico, icon.png, apple-icon.png. Next.js auto-generates tags.
PWA Manifest
Include icons array in manifest.json with 192x192 and 512x512 for maskable icons.
Best Practices
- Simplicity: At 16x16, complex details are illegible; use simplified logo mark; design for brand recognition in SERPs
- Consistency: Favicon should match logo/brand (logo-generator, brand-visual-generator)
- Cache: Use long cache; version for updates (e.g.
/favicon.ico?v=2) - Tools: RealFaviconGenerator, favicon.io, or favicons npm package for automation
- Test: Check across browsers, dark mode, and Search Console (favicon may take days to weeks to appear)
Output Format
- Size checklist (16, 32, 180, 192, 512; >48x48 for Google Search)
- Format recommendations (SVG, PNG, ICO)
- Implementation notes per tech stack (homepage header placement)
- Google Search checklist (crawlability, stable URL, appropriate content)
- Manifest (if PWA)
Related Skills
- logo-generator: Favicon typically derived from logo; consistent branding
- media-kit-page-generator: Media kit should include favicon or link to brand assets
- brand-visual-generator: Visual identity; favicon aligns with brand colors and mark
- indexing: Favicon requires crawlable homepage; URL Inspection for indexing
How to use favicon-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 development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add favicon-generator
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches favicon-generator from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate favicon-generator. Access the skill through slash commands (e.g., /favicon-generator) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★31 reviews- ★★★★★Hiroshi Gupta· Dec 28, 2024
Keeps context tight: favicon-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Dec 12, 2024
favicon-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Amina Rahman· Dec 8, 2024
favicon-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Layla Zhang· Nov 27, 2024
Registry listing for favicon-generator matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Hiroshi Shah· Nov 27, 2024
Useful defaults in favicon-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Oshnikdeep· Nov 3, 2024
Solid pick for teams standardizing on skills: favicon-generator is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Oct 22, 2024
We added favicon-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Layla Khan· Oct 18, 2024
favicon-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yuki Desai· Oct 18, 2024
favicon-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aditi Huang· Sep 25, 2024
We added favicon-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 31