favicon
Skill1 starsChanged 10 months agoMITView on GitHub
Generate favicons from a source image
- Installs packages
6 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- sambulosenda/Skillsedited, first seen Nov 8, 2026
- joelhooks/joelclawtheir own version, first seen Oct 8, 2026
- brianlovin/claude-configedited, first seen Oct 8, 2026
- abineetsingh/ClaudeSkillsedited, first seen Jun 12, 2026
- MohamedAbdallah-14/prompt-to-assettheir own version, first seen May 6, 2026
- cpiprint/skillsedited, first seen Jan 24, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- brianlovin/claude-config★ 37694% same
- sambulosenda/Skills★ 294% same
- abineetsingh/ClaudeSkills★ 199% same
- cpiprint/skills★ 196% same
Wrote their own version · 2
- joelhooks/joelclaw★ 65same name
- MohamedAbdallah-14/prompt-to-asset★ 18same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- buildSkill
- chat-widgetSkill
- conductor-setupSkill
- issuesSkill
- new-rails-projectSkill
- readmeSkill
- screenshotsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 11 are common, 0 are distinctive, and 14 are very specific to this project.
11
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 19
If not found, stop and instruct the user to install it:
- Very specific: line 25
Verify the source image exists at the provided path: $1
- Common: line 26
Check the file extension is a supported format (PNG, JPG, JPEG, SVG, WEBP, GIF)
- Common: line 27
If the file doesn't exist or isn't a valid image format, report the error and stop
- Very specific: line 51
Important: If existing favicon files are found (e.g., favicon.ico, apple-touch-icon.png), use their location as the target directory …
- Very specific: line 61
Existing
site.webmanifest: - Check the detected static assets directory for an existing manifest and extract the name field - Common: line 64
Directory name: - Use the current working directory name as fallback
- Common: line 70
Check if the detected static assets directory exists.
- Very specific: line 74
Run these ImageMagick commands to generate all favicon files.
- Very specific: line 109
If the source file has a .svg extension, copy it:
- Very specific: line 116
Create or update [STATIC_DIR]/site.webmanifest with this content (substitute the detected app name):
- Very specific: line 142
If site.webmanifest already exists in the static directory, preserve the existing theme_color, background_color, and display values while …
- Very specific: line 147
If static files are in public/ or static/ and served from root → use /favicon.ico
- Very specific: line 148
If static files are in src/assets/ → use /assets/favicon.ico
- Very specific: line 149
If static files are in the same directory as HTML → use ./favicon.ico or just favicon.ico
- Very specific: line 165
If the source was NOT an SVG, omit the <link rel="icon" type="image/svg+xml" href="/favicon.svg" /> line
- Very specific: line 166
Remove any existing <link rel="icon", <link rel="shortcut icon", <link rel="apple-touch-icon", or <link rel="manifest" tags before adding …
- Very specific: line 167
Place these tags near the top of the <head> section, after <meta charset> and <meta name="viewport"> if present
- Very specific: line 193
If the source was NOT an SVG, omit the { url: '/favicon.svg', type: 'image/svg+xml' } entry from the icon array
- Common: line 194
If metadata export doesn't exist, create it with just the icons-related fields
- Common: line 195
If metadata export exists, merge the icons configuration with existing fields
- Common: line 226
If ImageMagick is not installed, provide installation instructions and stop
- Common: line 227
If the source image doesn't exist, report the exact path that was tried and stop
- Common: line 228
If ImageMagick commands fail, report the specific error message
- Common: line 229
If the layout file cannot be found for HTML updates, generate files anyway and instruct on manual HTML addition
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generate a complete set of favicons from the source image at $1 and update the project's HTML with the appropriate link tags.
Prerequisites
First, verify ImageMagick v7+ is installed by running:
which magickIf not found, stop and instruct the user to install it:
- macOS:
brew install imagemagick - Linux:
sudo apt install imagemagick
Step 1: Validate Source Image
- Verify the source image exists at the provided path:
$1 - Check the file extension is a supported format (PNG, JPG, JPEG, SVG, WEBP, GIF)
- If the file doesn't exist or isn't a valid image format, report the error and stop
Note whether the source is an SVG file - if so, it will also be copied as favicon.svg.
Step 2: Detect Project Type and Static Assets Directory
Detect the project type and determine where static assets should be placed. Check in this order:
| Framework | Detection | Static Assets Directory |
| Rails | config/routes.rb exists | public/ |
| Next.js | next.config.* exists | public/ |
| Gatsby | gatsby-config.* exists | static/ |
| SvelteKit | svelte.config.* exists | static/ |
| Astro | astro.config.* exists | public/ |
| Hugo | hugo.toml or config.toml with Hugo markers | static/ |
| Jekyll | _config.yml with Jekyll markers | Root directory (same as index.html) |
| Vite | vite.config.* exists | public/ |
| Create React App | package.json has react-scripts dependency | public/ |
| Vue CLI | vue.config.* exists | public/ |
| Angular | angular.json exists | src/assets/ |
| Eleventy | .eleventy.js or eleventy.config.* exists | Check _site output or root |
| Static HTML | index.html in root | Same directory as index.html |
Important: If existing favicon files are found (e.g., favicon.ico, apple-touch-icon.png), use their location as the target directory regardless of framework detection.
Report the detected project type and the static assets directory that will be used.
When in doubt, ask: If you are not 100% confident about where static assets should be placed (e.g., ambiguous project structure, multiple potential locations, unfamiliar framework), use AskUserQuestionTool to confirm the target directory before proceeding. It's better to ask than to put files in the wrong place.
Step 3: Determine App Name
Find the app name from these sources (in priority order):
- Existing
site.webmanifest- Check the detected static assets directory for an existing manifest and extract thenamefield package.json- Extract thenamefield if it exists- Rails
config/application.rb- Extract the module name (e.g.,module MyApp→ "MyApp") - Directory name - Use the current working directory name as fallback
Convert the name to title case if needed (e.g., "my-app" → "My App").
Step 4: Ensure Static Assets Directory Exists
Check if the detected static assets directory exists. If not, create it.
Step 5: Generate Favicon Files
Run these ImageMagick commands to generate all favicon files. Replace [STATIC_DIR] with the detected static assets directory from Step 2.
Important: The -background none flag must come BEFORE the input file to properly preserve transparency when rendering SVGs. Placing it after the input will result in a white background.
favicon.ico (multi-resolution: 16x16, 32x32, 48x48)
magick -background none "$1" \
\( -clone 0 -resize 16x16 \) \
\( -clone 0 -resize 32x32 \) \
\( -clone 0 -resize 48x48 \) \
-delete 0 -alpha on \
[STATIC_DIR]/favicon.icofavicon-96x96.png
magick -background none "$1" -resize 96x96 -alpha on [STATIC_DIR]/favicon-96x96.pngapple-touch-icon.png (180x180)
magick -background none "$1" -resize 180x180 -alpha on [STATIC_DIR]/apple-touch-icon.pngweb-app-manifest-192x192.png
magick -background none "$1" -resize 192x192 -alpha on [STATIC_DIR]/web-app-manifest-192x192.pngweb-app-manifest-512x512.png
magick -background none "$1" -resize 512x512 -alpha on [STATIC_DIR]/web-app-manifest-512x512.pngfavicon.svg (only if source is SVG)
If the source file has a .svg extension, copy it:
cp "$1" [STATIC_DIR]/favicon.svgStep 6: Create/Update site.webmanifest
Create or update [STATIC_DIR]/site.webmanifest with this content (substitute the detected app name):
{
"name": "[APP_NAME]",
"short_name": "[APP_NAME]",
"icons": [
{
"src": "/web-app-manifest-192x192.png",
"sizes": "192x192",
"type": "image/png",
"purpose": "maskable"
},
{
"src": "/web-app-manifest-512x512.png",
"sizes": "512x512",
"type": "image/png",
"purpose": "maskable"
}
],
"theme_color": "#ffffff",
"background_color": "#ffffff",
"display": "standalone"
}If site.webmanifest already exists in the static directory, preserve the existing theme_color, background_color, and display values while updating the name, short_name, and icons array.
Step 7: Update HTML/Layout Files
Based on the detected project type, update the appropriate file. Adjust the href paths based on where the static assets directory is relative to the web root:
- If static files are in
public/orstatic/and served from root → use/favicon.ico - If static files are in
src/assets/→ use/assets/favicon.ico - If static files are in the same directory as HTML → use
./favicon.icoor justfavicon.ico
For Rails Projects
Edit app/views/layouts/application.html.erb. Find the <head> section and add/replace favicon-related tags with:
<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="shortcut icon" href="/favicon.ico" />
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
<meta name="apple-mobile-web-app-title" content="[APP_NAME]" />
<link rel="manifest" href="/site.webmanifest" />Important:
- If the source was NOT an SVG, omit the
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />line - Remove any existing
<link rel="icon",<link rel="shortcut icon",<link rel="apple-touch-icon", or<link rel="manifest"tags before adding the new ones - Place these tags near the top of the
<head>section, after<meta charset>and<meta name="viewport">if present
For Next.js Projects
Edit the detected layout file (app/layout.tsx or src/app/layout.tsx). Update or add the metadata export to include icons configuration:
export const metadata: Metadata = {
// ... keep existing metadata fields
icons: {
icon: [
{ url: '/favicon.ico' },
{ url: '/favicon-96x96.png', sizes: '96x96', type: 'image/png' },
{ url: '/favicon.svg', type: 'image/svg+xml' },
],
shortcut: '/favicon.ico',
apple: '/apple-touch-icon.png',
},
manifest: '/site.webmanifest',
appleWebApp: {
title: '[APP_NAME]',
},
};Important:
- If the source was NOT an SVG, omit the
{ url: '/favicon.svg', type: 'image/svg+xml' }entry from the icon array - If metadata export doesn't exist, create it with just the icons-related fields
- If metadata export exists, merge the icons configuration with existing fields
For Static HTML Projects
Edit the detected index.html file. Add the same HTML as Rails within the <head> section.
If No Project Detected
Skip HTML updates and inform the user they need to manually add the following to their HTML <head>:
<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="shortcut icon" href="/favicon.ico" />
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
<meta name="apple-mobile-web-app-title" content="[APP_NAME]" />
<link rel="manifest" href="/site.webmanifest" />Step 8: Summary
Report completion with:
- Detected project type and framework
- Static assets directory used
- List of files generated
- App name used in manifest and HTML
- Layout file updated (or note if manual update is needed)
- Note if any existing files were overwritten
Error Handling
- If ImageMagick is not installed, provide installation instructions and stop
- If the source image doesn't exist, report the exact path that was tried and stop
- If ImageMagick commands fail, report the specific error message
- If the layout file cannot be found for HTML updates, generate files anyway and instruct on manual HTML addition
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.

