{"id":22375,"plugin_id":"plugins_6ab0aed0959c8191b18c646c14b0244c","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:17:14.640Z","digest":"4e3bd961d35d4921589fca3e42a5cfdafbaf70cf1b055ad197cd43d0a29708bf","against":null,"payload":{"description":"Create unique plugin logos, composer icons, favicons, and supporting brand assets.","included_files":[],"name":"branding-and-assets","skill_md_contents":"---\nname: branding-and-assets\ndescription: Create unique plugin logos, composer icons, favicons, and supporting brand assets.\n---\n\nGenerate a distinct square PNG for every converted plugin unless the user explicitly requests supplied branding. Never reuse a previous plugin's logo or composer icon by filename, copy, or visual design. Derive a new asset identity from the plugin name and purpose, record its SHA-256 hashes in the build manifest, and verify that logo and composer-icon hashes differ from the previous plugin's assets.\n\nEnsure the asset is usable at directory and composer sizes, has no accidental text or third-party marks, and is referenced by both `interface.logo` and `interface.composerIcon`. Create favicon or alternate-size assets only when useful. Check dimensions, file format, square geometry, transparency, and hashes before packaging. If image generation or local asset writing needs permission, request it once and resume from the branding checkpoint.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}