From icon-designer
Create application icons, launcher icons, brand marks, and platform-ready icon concepts for iOS, Android, web apps, desktop apps, and developer tools. Activate when the request involves designing a recognizable, scalable icon that must work across multiple sizes, shapes, and operating systems.
npx claudepluginhub koi-language/plugins --plugin icon-designerThis skill uses the workspace's default tool permissions.
This skill handles icon creation for apps and software products — mobile app icons, launcher icons, desktop icons, PWA icons, favicon concepts, and brand-first symbol design.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
This skill handles icon creation for apps and software products — mobile app icons, launcher icons, desktop icons, PWA icons, favicon concepts, and brand-first symbol design.
Before generating anything, identify the core icon requirements:
If the request is ambiguous, infer the most likely app category and icon usage from the user’s description.
A strong app icon should be legible, memorable, and simple.
Define:
You must reduce the concept to one central idea.
If the icon needs more than 1–2 visual ideas, simplify it.
The icon must work at very small sizes.
Apply these constraints:
If the request is for app-store / launcher use, default to:
If the user did not specify a style, present 2–3 concise directions via prompt_user:
Include a one-line explanation of each option.
Skip this step if the user already gave a clear style.
Combine all decisions into ONE comprehensive prompt.
The prompt should include:
Always include an explicit output constraint such as:
Output a final standalone app icon asset only — not a mockup, not a UI presentation card, not an icon preview sheet, and never with checkerboard transparency patterns.
Prompt structure should typically describe:
Example prompt structure:
Create a premium mobile app icon for an AI productivity tool. The icon features a single glowing knot-like symbol forming a clean abstract spark. Centered composition, bold silhouette, minimal internal detail, high contrast, subtle 3D depth, polished glass-like highlights, deep dark background, modern iOS and Android app icon aesthetic. No text, no tiny details, no poster-like composition. Highly legible at small sizes. Output a final standalone app icon asset only — not a mockup, not a UI presentation card, not an icon preview sheet, and never with checkerboard transparency patterns.
Generate multiple directions when possible:
When the request is broad, prefer 2–4 distinct icon concepts instead of many tiny variations.
Review the generated result and check:
If weak:
Up to 3 attempts.
When presenting the result, explain what it is suitable for:
If needed, mention follow-up production assets that may be derived later:
Call show_result with resourceType: "image" to display the icon in the UI. Then return with file paths.