# Ay Icon

> Choose and approve a store-icon metaphor and visual direction, then create the assets when needed. Use when the deliverable is an App Store, Play Store, launcher, AppIcon, .icns, adaptive-icon, 换图标, 重做图标, or 图标太丑 request. Let a dedicated Apple icon asset skill lead exact AppIcon generation, export, installation, or debugging when available. Do not use for in-app glyphs or favicons-only work.

- Skill: `alvin-yang/ay-icon` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add alvin-yang/ay-icon`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alvin-yang/ay-icon/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ALVIN-YANG (https://skillmd.com/u/alvin-yang)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alvin-yang/ay-icon

---


# AY Icon

Turn a product into a store-readable icon. Lock the mark once, then generate, inspect, and install.

## Approval contract

<!-- ay-contract:start -->
- Read the full request and investigate discoverable facts before asking the user.
- Treat review, diagnosis, explanation, and planning as read-only unless the user also requests change.
- Treat a precise instruction as approval when target, observable result, and acceptance boundary are clear.
- A broad outcome authorizes investigation, not file or artifact changes based on choices the agent must invent.
- For a materially underspecified change, present one recommended proposal and wait for approval.
- After approval, execute autonomously inside the approved boundary; do not ask about ordinary implementation details.
- Reopen approval only when new evidence changes behavior, architecture, data contracts, dependencies, scope, risk, cost, rollback, or external actions.
- Perform external actions only when the request or approved proposal includes them. Confirm the exact target before an irreversible action.
- Preserve unrelated and user-authored work. Verify the real requested outcome before claiming completion.
<!-- ay-contract:end -->

## Decide the mark

Read the product, current icon, platform, and destination catalog. Infer the job the mark must communicate at 16–32px.

Do not default to a mouse, cursor, letter, or the most literal object. Choose one archetype: object, abstract form, hybrid, or character. Use a character only when the product is clearly character-led.

A request that names metaphor, style, and destination is approval. If those are open, present one recommended direction, two rejected alternatives, and wait.

## Generate

If a dedicated platform icon-production skill is installed and the metaphor is settled, let it lead generation, export, and installation. Otherwise use already available image generation. Do not add a paid API, CLI, or dependency without approval.

- Square full-bleed artwork. No baked rounded-square plate, device frame, or extra margin.
- No letters, numbers, watermarks, or real brand marks.
- One dominant subject filling most of the canvas. Readable when blurred to about 64px.
- Default to a matte illustration unless the user asked for glass, clay, sketch, or similar.
- Keep metaphor and palette stable across sizes and appearances.

Generate only enough candidates to expose a meaningful choice. Inspect each before showing a pick. Reject generic 3D, unrelated characters, and marks that vanish on light or dark backgrounds.

## Ship

An asset request is incomplete until image files exist and have been inspected at full and small sizes. Write into the project's existing icon set and required sizes. Do not invent a second catalog. Apply a system mask only when the platform needs it and the project does not already bake one.

If asked to install or open the app, do that after the assets compile. Report destinations, skipped appearances, and any unverified store listing surface.