[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NVC9N3MYE3FH8M2XVC6R9H":3,"skill-same:01M6NVC9N3MYE3FH8M2XVC6R9H":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6NVC9N3MYE3FH8M2XVC6R9H","favicon",null,"Generate favicons from a source image","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdesign-favicon\u002Fsickn33\u002Ffavicon\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34],"image","generate","Bash","community","cp","mkdir","which","path","source","unknown","fork","2026-11-10 10:12:30",false,"---\nname: favicon\nargument-hint: [path to source image]\ndescription: Generate favicons from a source image\nallowed-tools: Bash(magick *), Bash(which *), Bash(cp *), Bash(mkdir *)\ncontext: fork\nrisk: unknown\nsource: community\nmetadata:\n  author: Shpigford\n  version: \"1.0\"\n---\n\nGenerate a complete set of favicons from the source image at `$1` and update the project's HTML with the appropriate link tags.\n\n## When to Use\n\n- You need to generate a complete favicon set from a single source image.\n- The task includes placing the assets in the correct framework-specific static directory and updating HTML link tags.\n- You want one workflow that validates the source image, detects the project type, and writes the right favicon outputs.\n\n## Prerequisites\n\nFirst, verify ImageMagick v7+ is installed by running:\n```bash\nwhich magick\n```\n\nIf not found, stop and instruct the user to install it:\n- **macOS**: `brew install imagemagick`\n- **Linux**: `sudo apt install imagemagick`\n\n## Step 1: Validate Source Image\n\n1. Verify the source image exists at the provided path: `$1`\n2. Check the file extension is a supported format (PNG, JPG, JPEG, SVG, WEBP, GIF)\n3. If the file doesn't exist or isn't a valid image format, report the error and stop\n\nNote whether the source is an SVG file - if so, it will also be copied as `favicon.svg`.\n\n## Step 2: Detect Project Type and Static Assets Directory\n\nDetect the project type and determine where static assets should be placed. Check in this order:\n\n| Framework | Detection | Static Assets Directory |\n|-----------|-----------|------------------------|\n| **Rails** | `config\u002Froutes.rb` exists | `public\u002F` |\n| **Next.js** | `next.config.*` exists | `public\u002F` |\n| **Gatsby** | `gatsby-config.*` exists | `static\u002F` |\n| **SvelteKit** | `svelte.config.*` exists | `static\u002F` |\n| **Astro** | `astro.config.*` exists | `public\u002F` |\n| **Hugo** | `hugo.toml` or `config.toml` with Hugo markers | `static\u002F` |\n| **Jekyll** | `_config.yml` with Jekyll markers | Root directory (same as `index.html`) |\n| **Vite** | `vite.config.*` exists | `public\u002F` |\n| **Create React App** | `package.json` has `react-scripts` dependency | `public\u002F` |\n| **Vue CLI** | `vue.config.*` exists | `public\u002F` |\n| **Angular** | `angular.json` exists | `src\u002Fassets\u002F` |\n| **Eleventy** | `.eleventy.js` or `eleventy.config.*` exists | Check `_site` output or root |\n| **Static HTML** | `index.html` in root | Same directory as `index.html` |\n\n**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.\n\nReport the detected project type and the static assets directory that will be used.\n\n**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.\n\n## Step 3: Determine App Name\n\nFind the app name from these sources (in priority order):\n\n1. **Existing `site.webmanifest`** - Check the detected static assets directory for an existing manifest and extract the `name` field\n2. **`package.json`** - Extract the `name` field if it exists\n3. **Rails `config\u002Fapplication.rb`** - Extract the module name (e.g., `module MyApp` → \"MyApp\")\n4. **Directory name** - Use the current working directory name as fallback\n\nConvert the name to title case if needed (e.g., \"my-app\" → \"My App\").\n\n## Step 4: Ensure Static Assets Directory Exists\n\nCheck if the detected static assets directory exists. If not, create it.\n\n## Step 5: Generate Favicon Files\n\nRun these ImageMagick commands to generate all favicon files. Replace `[STATIC_DIR]` with the detected static assets directory from Step 2.\n\n**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.\n\n### favicon.ico (multi-resolution: 16x16, 32x32, 48x48)\n```bash\nmagick -background none \"$1\" \\\n  \\( -clone 0 -resize 16x16 \\) \\\n  \\( -clone 0 -resize 32x32 \\) \\\n  \\( -clone 0 -resize 48x48 \\) \\\n  -delete 0 -alpha on \\\n  [STATIC_DIR]\u002Ffavicon.ico\n```\n\n### favicon-96x96.png\n```bash\nmagick -background none \"$1\" -resize 96x96 -alpha on [STATIC_DIR]\u002Ffavicon-96x96.png\n```\n\n### apple-touch-icon.png (180x180)\n```bash\nmagick -background none \"$1\" -resize 180x180 -alpha on [STATIC_DIR]\u002Fapple-touch-icon.png\n```\n\n### web-app-manifest-192x192.png\n```bash\nmagick -background none \"$1\" -resize 192x192 -alpha on [STATIC_DIR]\u002Fweb-app-manifest-192x192.png\n```\n\n### web-app-manifest-512x512.png\n```bash\nmagick -background none \"$1\" -resize 512x512 -alpha on [STATIC_DIR]\u002Fweb-app-manifest-512x512.png\n```\n\n### favicon.svg (only if source is SVG)\nIf the source file has a `.svg` extension, copy it:\n```bash\ncp \"$1\" [STATIC_DIR]\u002Ffavicon.svg\n```\n\n## Step 6: Create\u002FUpdate site.webmanifest\n\nCreate or update `[STATIC_DIR]\u002Fsite.webmanifest` with this content (substitute the detected app name):\n\n```json\n{\n  \"name\": \"[APP_NAME]\",\n  \"short_name\": \"[APP_NAME]\",\n  \"icons\": [\n    {\n      \"src\": \"\u002Fweb-app-manifest-192x192.png\",\n      \"sizes\": \"192x192\",\n      \"type\": \"image\u002Fpng\",\n      \"purpose\": \"maskable\"\n    },\n    {\n      \"src\": \"\u002Fweb-app-manifest-512x512.png\",\n      \"sizes\": \"512x512\",\n      \"type\": \"image\u002Fpng\",\n      \"purpose\": \"maskable\"\n    }\n  ],\n  \"theme_color\": \"#ffffff\",\n  \"background_color\": \"#ffffff\",\n  \"display\": \"standalone\"\n}\n```\n\nIf `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.\n\n## Step 7: Update HTML\u002FLayout Files\n\nBased 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:\n- If static files are in `public\u002F` or `static\u002F` and served from root → use `\u002Ffavicon.ico`\n- If static files are in `src\u002Fassets\u002F` → use `\u002Fassets\u002Ffavicon.ico`\n- If static files are in the same directory as HTML → use `.\u002Ffavicon.ico` or just `favicon.ico`\n\n### For Rails Projects\n\nEdit `app\u002Fviews\u002Flayouts\u002Fapplication.html.erb`. Find the `\u003Chead>` section and add\u002Freplace favicon-related tags with:\n\n```html\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" href=\"\u002Ffavicon-96x96.png\" sizes=\"96x96\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>\n\u003Clink rel=\"shortcut icon\" href=\"\u002Ffavicon.ico\" \u002F>\n\u003Clink rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"\u002Fapple-touch-icon.png\" \u002F>\n\u003Cmeta name=\"apple-mobile-web-app-title\" content=\"[APP_NAME]\" \u002F>\n\u003Clink rel=\"manifest\" href=\"\u002Fsite.webmanifest\" \u002F>\n```\n\n**Important**:\n- If the source was NOT an SVG, omit the `\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>` line\n- Remove any existing `\u003Clink rel=\"icon\"`, `\u003Clink rel=\"shortcut icon\"`, `\u003Clink rel=\"apple-touch-icon\"`, or `\u003Clink rel=\"manifest\"` tags before adding the new ones\n- Place these tags near the top of the `\u003Chead>` section, after `\u003Cmeta charset>` and `\u003Cmeta name=\"viewport\">` if present\n\n### For Next.js Projects\n\nEdit the detected layout file (`app\u002Flayout.tsx` or `src\u002Fapp\u002Flayout.tsx`). Update or add the `metadata` export to include icons configuration:\n\n```typescript\nexport const metadata: Metadata = {\n  \u002F\u002F ... keep existing metadata fields\n  icons: {\n    icon: [\n      { url: '\u002Ffavicon.ico' },\n      { url: '\u002Ffavicon-96x96.png', sizes: '96x96', type: 'image\u002Fpng' },\n      { url: '\u002Ffavicon.svg', type: 'image\u002Fsvg+xml' },\n    ],\n    shortcut: '\u002Ffavicon.ico',\n    apple: '\u002Fapple-touch-icon.png',\n  },\n  manifest: '\u002Fsite.webmanifest',\n  appleWebApp: {\n    title: '[APP_NAME]',\n  },\n};\n```\n\n**Important**:\n- If the source was NOT an SVG, omit the `{ url: '\u002Ffavicon.svg', type: 'image\u002Fsvg+xml' }` entry from the icon array\n- If metadata export doesn't exist, create it with just the icons-related fields\n- If metadata export exists, merge the icons configuration with existing fields\n\n### For Static HTML Projects\n\nEdit the detected `index.html` file. Add the same HTML as Rails within the `\u003Chead>` section.\n\n### If No Project Detected\n\nSkip HTML updates and inform the user they need to manually add the following to their HTML `\u003Chead>`:\n\n```html\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" href=\"\u002Ffavicon-96x96.png\" sizes=\"96x96\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>\n\u003Clink rel=\"shortcut icon\" href=\"\u002Ffavicon.ico\" \u002F>\n\u003Clink rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"\u002Fapple-touch-icon.png\" \u002F>\n\u003Cmeta name=\"apple-mobile-web-app-title\" content=\"[APP_NAME]\" \u002F>\n\u003Clink rel=\"manifest\" href=\"\u002Fsite.webmanifest\" \u002F>\n```\n\n## Step 8: Summary\n\nReport completion with:\n- Detected project type and framework\n- Static assets directory used\n- List of files generated\n- App name used in manifest and HTML\n- Layout file updated (or note if manual update is needed)\n- Note if any existing files were overwritten\n\n## Error Handling\n\n- If ImageMagick is not installed, provide installation instructions and stop\n- If the source image doesn't exist, report the exact path that was tried and stop\n- If ImageMagick commands fail, report the specific error message\n- If the layout file cannot be found for HTML updates, generate files anyway and instruct on manual HTML addition\n","Generate a complete set of favicons from the source image at `$1` and update the project's HTML with the appropriate link tags.\n\n## When to Use\n\n- You need to generate a complete favicon set from a single source image.\n- The task includes placing the assets in the correct framework-specific static directory and updating HTML link tags.\n- You want one workflow that validates the source image, detects the project type, and writes the right favicon outputs.\n\n## Prerequisites\n\nFirst, verify ImageMagick v7+ is installed by running:\n```bash\nwhich magick\n```\n\nIf not found, stop and instruct the user to install it:\n- **macOS**: `brew install imagemagick`\n- **Linux**: `sudo apt install imagemagick`\n\n## Step 1: Validate Source Image\n\n1. Verify the source image exists at the provided path: `$1`\n2. Check the file extension is a supported format (PNG, JPG, JPEG, SVG, WEBP, GIF)\n3. If the file doesn't exist or isn't a valid image format, report the error and stop\n\nNote whether the source is an SVG file - if so, it will also be copied as `favicon.svg`.\n\n## Step 2: Detect Project Type and Static Assets Directory\n\nDetect the project type and determine where static assets should be placed. Check in this order:\n\n| Framework | Detection | Static Assets Directory |\n|-----------|-----------|------------------------|\n| **Rails** | `config\u002Froutes.rb` exists | `public\u002F` |\n| **Next.js** | `next.config.*` exists | `public\u002F` |\n| **Gatsby** | `gatsby-config.*` exists | `static\u002F` |\n| **SvelteKit** | `svelte.config.*` exists | `static\u002F` |\n| **Astro** | `astro.config.*` exists | `public\u002F` |\n| **Hugo** | `hugo.toml` or `config.toml` with Hugo markers | `static\u002F` |\n| **Jekyll** | `_config.yml` with Jekyll markers | Root directory (same as `index.html`) |\n| **Vite** | `vite.config.*` exists | `public\u002F` |\n| **Create React App** | `package.json` has `react-scripts` dependency | `public\u002F` |\n| **Vue CLI** | `vue.config.*` exists | `public\u002F` |\n| **Angular** | `angular.json` exists | `src\u002Fassets\u002F` |\n| **Eleventy** | `.eleventy.js` or `eleventy.config.*` exists | Check `_site` output or root |\n| **Static HTML** | `index.html` in root | Same directory as `index.html` |\n\n**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.\n\nReport the detected project type and the static assets directory that will be used.\n\n**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.\n\n## Step 3: Determine App Name\n\nFind the app name from these sources (in priority order):\n\n1. **Existing `site.webmanifest`** - Check the detected static assets directory for an existing manifest and extract the `name` field\n2. **`package.json`** - Extract the `name` field if it exists\n3. **Rails `config\u002Fapplication.rb`** - Extract the module name (e.g., `module MyApp` → \"MyApp\")\n4. **Directory name** - Use the current working directory name as fallback\n\nConvert the name to title case if needed (e.g., \"my-app\" → \"My App\").\n\n## Step 4: Ensure Static Assets Directory Exists\n\nCheck if the detected static assets directory exists. If not, create it.\n\n## Step 5: Generate Favicon Files\n\nRun these ImageMagick commands to generate all favicon files. Replace `[STATIC_DIR]` with the detected static assets directory from Step 2.\n\n**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.\n\n### favicon.ico (multi-resolution: 16x16, 32x32, 48x48)\n```bash\nmagick -background none \"$1\" \\\n  \\( -clone 0 -resize 16x16 \\) \\\n  \\( -clone 0 -resize 32x32 \\) \\\n  \\( -clone 0 -resize 48x48 \\) \\\n  -delete 0 -alpha on \\\n  [STATIC_DIR]\u002Ffavicon.ico\n```\n\n### favicon-96x96.png\n```bash\nmagick -background none \"$1\" -resize 96x96 -alpha on [STATIC_DIR]\u002Ffavicon-96x96.png\n```\n\n### apple-touch-icon.png (180x180)\n```bash\nmagick -background none \"$1\" -resize 180x180 -alpha on [STATIC_DIR]\u002Fapple-touch-icon.png\n```\n\n### web-app-manifest-192x192.png\n```bash\nmagick -background none \"$1\" -resize 192x192 -alpha on [STATIC_DIR]\u002Fweb-app-manifest-192x192.png\n```\n\n### web-app-manifest-512x512.png\n```bash\nmagick -background none \"$1\" -resize 512x512 -alpha on [STATIC_DIR]\u002Fweb-app-manifest-512x512.png\n```\n\n### favicon.svg (only if source is SVG)\nIf the source file has a `.svg` extension, copy it:\n```bash\ncp \"$1\" [STATIC_DIR]\u002Ffavicon.svg\n```\n\n## Step 6: Create\u002FUpdate site.webmanifest\n\nCreate or update `[STATIC_DIR]\u002Fsite.webmanifest` with this content (substitute the detected app name):\n\n```json\n{\n  \"name\": \"[APP_NAME]\",\n  \"short_name\": \"[APP_NAME]\",\n  \"icons\": [\n    {\n      \"src\": \"\u002Fweb-app-manifest-192x192.png\",\n      \"sizes\": \"192x192\",\n      \"type\": \"image\u002Fpng\",\n      \"purpose\": \"maskable\"\n    },\n    {\n      \"src\": \"\u002Fweb-app-manifest-512x512.png\",\n      \"sizes\": \"512x512\",\n      \"type\": \"image\u002Fpng\",\n      \"purpose\": \"maskable\"\n    }\n  ],\n  \"theme_color\": \"#ffffff\",\n  \"background_color\": \"#ffffff\",\n  \"display\": \"standalone\"\n}\n```\n\nIf `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.\n\n## Step 7: Update HTML\u002FLayout Files\n\nBased 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:\n- If static files are in `public\u002F` or `static\u002F` and served from root → use `\u002Ffavicon.ico`\n- If static files are in `src\u002Fassets\u002F` → use `\u002Fassets\u002Ffavicon.ico`\n- If static files are in the same directory as HTML → use `.\u002Ffavicon.ico` or just `favicon.ico`\n\n### For Rails Projects\n\nEdit `app\u002Fviews\u002Flayouts\u002Fapplication.html.erb`. Find the `\u003Chead>` section and add\u002Freplace favicon-related tags with:\n\n```html\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" href=\"\u002Ffavicon-96x96.png\" sizes=\"96x96\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>\n\u003Clink rel=\"shortcut icon\" href=\"\u002Ffavicon.ico\" \u002F>\n\u003Clink rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"\u002Fapple-touch-icon.png\" \u002F>\n\u003Cmeta name=\"apple-mobile-web-app-title\" content=\"[APP_NAME]\" \u002F>\n\u003Clink rel=\"manifest\" href=\"\u002Fsite.webmanifest\" \u002F>\n```\n\n**Important**:\n- If the source was NOT an SVG, omit the `\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>` line\n- Remove any existing `\u003Clink rel=\"icon\"`, `\u003Clink rel=\"shortcut icon\"`, `\u003Clink rel=\"apple-touch-icon\"`, or `\u003Clink rel=\"manifest\"` tags before adding the new ones\n- Place these tags near the top of the `\u003Chead>` section, after `\u003Cmeta charset>` and `\u003Cmeta name=\"viewport\">` if present\n\n### For Next.js Projects\n\nEdit the detected layout file (`app\u002Flayout.tsx` or `src\u002Fapp\u002Flayout.tsx`). Update or add the `metadata` export to include icons configuration:\n\n```typescript\nexport const metadata: Metadata = {\n  \u002F\u002F ... keep existing metadata fields\n  icons: {\n    icon: [\n      { url: '\u002Ffavicon.ico' },\n      { url: '\u002Ffavicon-96x96.png', sizes: '96x96', type: 'image\u002Fpng' },\n      { url: '\u002Ffavicon.svg', type: 'image\u002Fsvg+xml' },\n    ],\n    shortcut: '\u002Ffavicon.ico',\n    apple: '\u002Fapple-touch-icon.png',\n  },\n  manifest: '\u002Fsite.webmanifest',\n  appleWebApp: {\n    title: '[APP_NAME]',\n  },\n};\n```\n\n**Important**:\n- If the source was NOT an SVG, omit the `{ url: '\u002Ffavicon.svg', type: 'image\u002Fsvg+xml' }` entry from the icon array\n- If metadata export doesn't exist, create it with just the icons-related fields\n- If metadata export exists, merge the icons configuration with existing fields\n\n### For Static HTML Projects\n\nEdit the detected `index.html` file. Add the same HTML as Rails within the `\u003Chead>` section.\n\n### If No Project Detected\n\nSkip HTML updates and inform the user they need to manually add the following to their HTML `\u003Chead>`:\n\n```html\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" href=\"\u002Ffavicon-96x96.png\" sizes=\"96x96\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>\n\u003Clink rel=\"shortcut icon\" href=\"\u002Ffavicon.ico\" \u002F>\n\u003Clink rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"\u002Fapple-touch-icon.png\" \u002F>\n\u003Cmeta name=\"apple-mobile-web-app-title\" content=\"[APP_NAME]\" \u002F>\n\u003Clink rel=\"manifest\" href=\"\u002Fsite.webmanifest\" \u002F>\n```\n\n## Step 8: Summary\n\nReport completion with:\n- Detected project type and framework\n- Static assets directory used\n- List of files generated\n- App name used in manifest and HTML\n- Layout file updated (or note if manual update is needed)\n- Note if any existing files were overwritten\n\n## Error Handling\n\n- If ImageMagick is not installed, provide installation instructions and stop\n- If the source image doesn't exist, report the exact path that was tried and stop\n- If ImageMagick commands fail, report the specific error message\n- If the layout file cannot be found for HTML updates, generate files anyway and instruct on manual HTML addition\n",{"name":5,"risk":33,"source":27,"context":34,"metadata":40,"description":7,"allowed-tools":43,"argument-hint":44},{"author":41,"version":42},"Shpigford","1.0","Bash(magick *), Bash(which *), Bash(cp *), Bash(mkdir *)",[45],"path to source image","main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","design-favicon\u002Fsickn33\u002Ffavicon",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill favicon",{"tool":59,"command":60},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill favicon",{"tool":62,"command":63},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill favicon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fdesign-favicon\u002Fsickn33\u002Ffavicon\u002FSKILL.md",true,[],[68,103,117,135,156,182],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":82,"publishedAt":35},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[74,77],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":35},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[110,111,84,112,113,94,114,115,116],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":126,"publishedAt":35},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000038","人力资源",[127,128,129,33,130,131,132,133,27,134,101],"wiki","architect","wiki architect","you","documentation architect","guides","structured","onboarding",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":35},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[111,142,143,144,130,145,146,114,147,148,46,149,150,151,152,153,101,154,155],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":35},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[163,164,94,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":190,"publishedAt":35},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[188,189],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[191,192,175,152,84,193,91,194,195,196,197,198,199,200,201,98,202,203,102,204],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]