public
Generates public/ directory with static assets including favicons, app icons, and site.webmanifest for Progressive Web App (PWA) support.
When & Why to Use This Skill
This Claude skill automates the generation of a standard 'public/' directory containing essential static assets for web projects. It produces a complete set of favicons, Apple touch icons, and a site.webmanifest, facilitating seamless Progressive Web App (PWA) integration and ensuring professional visual representation across various platforms and devices.
Use Cases
- Automating the boilerplate setup for web project static assets to save development time during initial project scaffolding.
- Configuring Progressive Web App (PWA) manifests and icons to improve mobile user experience and meet browser installability criteria.
- Ensuring cross-browser and cross-platform compatibility by providing a full suite of favicon sizes and formats (ICO, PNG) for iOS, Android, and desktop.
| name | public |
|---|---|
| description | Generates public/ directory with static assets including favicons, app icons, and site.webmanifest for Progressive Web App (PWA) support. |
Public Folder Skill
Purpose
Generate the public/ directory with static assets including favicons, app icons, and web manifest for Progressive Web App (PWA) support.
Input Parameters
- No user input required - uses standard favicon and icon files
Output
Create the following files in the public/ directory:
favicon.ico- Main faviconfavicon-16x16.png- 16x16 faviconfavicon-32x32.png- 32x32 faviconapple-touch-icon.png- Apple touch icon (180x180)android-chrome-192x192.png- Android icon (192x192)android-chrome-512x512.png- Android icon (512x512)site.webmanifest- Web app manifest file
Implementation
See: examples.md in this directory for implementation details and file examples.
Notes
- The public folder contains static assets that are served directly without processing
- Favicons are referenced in
index.htmlvia link tags - The site.webmanifest enables PWA features and Android app icon support
- These files should be customized for each application with brand-specific icons
- Icons support various device sizes and platforms (iOS, Android, web browsers)
- All files are served from the root path in production builds