Skip to content

t1k:marketing:store:aso

FieldValue
Modulestore
Version0.14.9
Effortmedium
Tools—
/t1k:marketing:store:aso

Turns real captures of one game into its store art set, reviews the set, files it in the team’s Figma file, and leaves a draft store listing for a human to approve. This skill owns the art and its craft. The store writes belong to the store skills in § Store routing.

IntentPath
“Make the store icon”, “icon variants”§ Workflow step 4, then references/asset-recipes.md § Icon
“Seasonal icon” (Halloween, Christmas, an event)§ Seasonal icon below
“Feature graphic”references/asset-recipes.md § Feature graphic
“Store screenshots”, “captions”references/asset-recipes.md § Screenshots
“Put it in Figma”, “review the set”references/ship-and-review.md § Figma and § Review
“Push to the store”, “draft listing”§ Store routing, then references/ship-and-review.md § Drafts
Writing the title or descriptionsNot this skill: use the copywriting module, then bring finished copy here
  1. Drafts only. This skill never publishes, sends for review, or rolls out. Every store write goes through t1k-marketing-store-gate (plan, approve, apply). The approval names the app and the before-to-after values. rules/store-write-safety.md binds in full.
  2. Isolated accounts stay isolated. Some developer accounts live on their own VPS, one account per machine. Work on them only inside that VPS’s own browser. Never add a shared service account or a shared login to them, and never call their Play API from this laptop’s network. If a step stalls there, stop and hand it to the user. Offer no cross-account shortcut.
  3. Real game, real captures. Screenshots show the shipped game from a real build. AI-generated scenes may support the set, but never present one as gameplay. Reviewers reject AI-looking “in-game” shots.
  4. No secrets or identities in artifacts. Files, Figma layer names, commit messages and chat carry no tokens, passwords, VPS addresses, account IDs, developer-account names, or partner and client names. Name credentials by vault name (t1k vault get <name>) or environment variable name only.
  5. Paid generation needs the user’s yes. If an image service asks to confirm a cost, stop and ask. A job stopped for balance is not retried until the user says so.
  6. Store text stays inside policy. No superlatives or rankings, no claims that need proof, no third-party trademarks, no emoji in short fields. The full check is references/asset-recipes.md § Copy check.
  1. Intake. Confirm the title, the platforms (Play, App Store or both), the locales, the asset set, any event or season, and the deadline. Ask with AskUserQuestion for anything missing. Get the game’s own display font and palette: store art must match the game’s UI.
  2. Source captures. Take screenshots from a real build and record the build version with the set. For the icon, start from the game’s own art layers, not a fresh redraw. If no capture exists yet, stop and report that. Never fake one.
  3. Plan the set. A typical set is one icon, two to four icon variants for a test, one feature graphic, and screenshots up to the console maximum (the count and format limits are in the Play spec reference named in § Store routing). Name each file <asset>_<size>_<variant>.png.
  4. Produce. Follow references/asset-recipes.md. Generated art comes from the studio image-generation tools; check the image route with one image before any batch. Where possible, draw title text in code with the game’s font.
  5. Preview and review. Build one contact sheet per asset family. Check each icon at 48 px and each caption at phone width. Run the copy check. Confirm every screenshot is real or labelled as supporting art.
  6. File in Figma. Follow references/ship-and-review.md § Figma. This needs a Figma connector in the session. Without one, hand over the folder and name the Figma step as pending in the report.
  7. Draft the listing. Use § Store routing. Each write goes through the gate as a plan, and the approval is an AskUserQuestion for that one app. Never run a bulk apply across titles.
  8. Log and report. Add a job-log entry (t1k-marketing-core-joblog, track aso). Report what is in draft, what awaits review, and what is blocked. Name accounts by label, never by ID.

Keep the master icon’s character and layout. Change only the background palette and one prop (a hat, a pumpkin, snow), so the event icon still reads as the same game. Treat it as a variant, not a new app icon. A seasonal swap on a live listing goes through the gate. Prefer a store-listing experiment for the event, and return to the master icon when the event ends.

Store or stepSkillUse for
Google Play, manifest modet1k-marketing-store-play-console-setupGraphics and listing fields through the title’s manifest and the gate. Its references/api-surface.md holds the Play asset spec table
Google Play, headless consolet1k-marketing-store-vps-managementOnly for an account whose API refuses a draft. Work on that account’s own VPS, “Save as draft” only
App Store Connectt1k-marketing-store-asc-setupiOS listing fields and screenshots
Any store writet1k-marketing-store-gateplan, approve, apply
Per-title store configt1k-marketing-store-manifestThe manifest the gate reads
Builds (AAB, symbols)t1k-marketing-store-play-upload-buildNot art. Listed so art work never uploads a build

The compositing scripts for the existing titles sit in the private The1Studio/aso-projects repo: one folder per title, a shared output folder, and one build script per title. They hold game art and per-title data, so this kit does not copy them. A new title starts from the closest existing title’s folder. Swap the captures, palette, font and captions, and keep the layout rules in references/asset-recipes.md. Without access to that repo, the recipes still hold for any image tool.

A wrong step is recorded as a [t1k:lesson] marker, which the t1k-rsi gotcha ledger picks up for this skill, and the fix lands in the step it guards. The skill carries no ## Gotchas section by design.

Runs inline in the main session. Composition, capture review, Figma and console work need the session’s judgment and its approval gate, so no sub-agent is spawned.