favicon-generator
When the user wants to implement, optimize, or audit favicon and app icons. Also use when the user mentions "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," or "tab icon." For visual system, use brand-visual-generator.
Best use case
favicon-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to implement, optimize, or audit favicon and app icons. Also use when the user mentions "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," or "tab icon." For visual system, use brand-visual-generator.
Teams using favicon-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/favicon/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How favicon-generator Compares
| Feature / Agent | favicon-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to implement, optimize, or audit favicon and app icons. Also use when the user mentions "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," or "tab icon." For visual system, use brand-visual-generator.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: 1. **Tech stack**: Next.js, WordPress, static HTML, etc. 2. **PWA**: Is the site a PWA or planning to be? 3. **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](https://developers.google.com/search/docs/appearance/favicon-in-search) 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 ```html <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
Related Skills
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.
pricing-page-generator
When the user wants to create, optimize, or audit pricing page content and structure. Also use when the user mentions "pricing page," "pricing table," "plans," "subscription," "pricing plans," "pricing tiers," "pricing comparison," "SaaS pricing," "enterprise pricing," "API pricing," "contact sales," "pricing in nav," "public pricing," "hide pricing," or "pricing objection handling." For pricing strategy, use pricing-strategy.