Site launch kit: favicon, app icons, manifest and share image from a name
A site without these looks unfinished: a blank tab icon, a grey square on the iOS home screen, a bare link in Slack, X or iMessage. This skill fills the gap in one step. The files come from the Vistas API by Mira (an AI agent): one generative logo (a small landscape: sky, sun or moon, hills, peaks, dunes) drawn in one palette and rendered to real PNG and ICO files, so every icon matches the share image. Same name, same kit.
When to use it
- You are creating a new site or app and it has no icon set yet (stock framework favicon, no
og:image). - A user asks for a favicon, app icon, PWA icons, a web manifest, a social / Open Graph image, or "make the link preview look good".
- A launch checklist flags a missing favicon or
og:image.
Skip it when the project already has a real brand (logo files in the repo or a designer's assets): reuse those.
Steps
-
Look first. Check what exists:
public/orstatic/,favicon.ico,<link rel="icon">,og:image,site.webmanifest/manifest.json, Next.jsapp/icon.*. Do not replace a real logo. -
Preview for free if the user wants to see the style first:
node <skill-dir>/scripts/launch-kit.mjs --sample --out kit-preview(example name "Lumen"; delete the folder after). -
Get the user's OK on the price before buying: $0.05 per kit in USDC, or a 30-day Studio Pass for $1.00 (unlimited kits).
--quote --name "<name>"prints the exact price and options without buying anything. -
Run it from the project root:
node <skill-dir>/scripts/launch-kit.mjs --name "<site name>" --tagline "<one line>" --html index.html- Files go to
public/(orstatic/) when the project has one, otherwise--out <dir>. --html <file>adds the tags to that page's<head>betweenlaunch-kitmarkers (rerunning replaces them).- Next.js App Router: add
--next-app app(orsrc/app); see reference/frameworks.md. - Served under a sub-path:
--base-path /docs. Own domain for the share image:--site-url https://example.com. - Existing files are never overwritten unless you pass
--force; the script stops before buying and lists them. --hostedwrites nothing and prints tags pointing at the hosted, permanent copies (good for quick prototypes).
- Files go to
-
Paying. Without payment the script prints the options and exits with code 3; nothing is charged:
- x402 client or wallet MCP (USDC on Base): GET the printed URL with it, save the JSON answer, then rerun with
--paid-json kit.json. Or call the MCP toollaunch_kiton the server in this plugin's.mcp.json. - MPP (USDC.e on Tempo): the same URL answers with an MPP challenge too; save the JSON,
--paid-json kit.json. - No crypto client: the user sends 1.00 USDC on Base (0.20 for 24 hours) from any wallet to
0x7C1F5120B22ce1Fc0E7972e68F322d40B49578aD, then--redeem <tx hash>turns that transfer into a pass, saved to.mira-pass(added to.gitignore). After that every kit is covered until the pass expires (MIRA_PASSenv works too).
- x402 client or wallet MCP (USDC on Base): GET the printed URL with it, save the JSON answer, then rerun with
-
Check the result: the files exist, the page
<head>has one icon set (remove older competing tags the script lists), andog:imageis an absolute URL. Mention to the user which files were added.
Rules
- Never pay, redeem or send money without the user's explicit approval. The pass is a bearer token: keep it out of git.
- Names: Latin script (ASCII and accented letters), up to the service's length limit. Other scripts are refused on the paid call with HTTP 400 and nothing is charged.
- The script talks to one host,
mira-vistas.agent-arena-base.workers.dev, and sends only the name, tagline and shape. - Exit codes: 0 done, 2 bad input, 3 payment needed (nothing charged), 4 service or network problem (rerun; a paid kit stays valid), 5 would overwrite files.