t1k:marketing:store:aso
| Field | Value |
|---|---|
| Module | store |
| Version | 0.14.9 |
| Effort | medium |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:marketing:store:asoStore Art (ASO) for One Title
Section titled “Store Art (ASO) for One Title”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.
Decision Tree
Section titled “Decision Tree”| Intent | Path |
|---|---|
| “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 descriptions | Not this skill: use the copywriting module, then bring finished copy here |
Hard rules
Section titled “Hard rules”- 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.mdbinds in full. - 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.
- 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.
- 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. - 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.
- 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.
Workflow
Section titled “Workflow”- 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
AskUserQuestionfor anything missing. Get the game’s own display font and palette: store art must match the game’s UI. - 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.
- 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. - 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. - 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.
- 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. - Draft the listing. Use § Store routing. Each write goes through the gate as a plan, and the approval
is an
AskUserQuestionfor that one app. Never run a bulk apply across titles. - Log and report. Add a job-log entry (
t1k-marketing-core-joblog, trackaso). Report what is in draft, what awaits review, and what is blocked. Name accounts by label, never by ID.
Seasonal icon
Section titled “Seasonal icon”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 routing
Section titled “Store routing”| Store or step | Skill | Use for |
|---|---|---|
| Google Play, manifest mode | t1k-marketing-store-play-console-setup | Graphics 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 console | t1k-marketing-store-vps-management | Only for an account whose API refuses a draft. Work on that account’s own VPS, “Save as draft” only |
| App Store Connect | t1k-marketing-store-asc-setup | iOS listing fields and screenshots |
| Any store write | t1k-marketing-store-gate | plan, approve, apply |
| Per-title store config | t1k-marketing-store-manifest | The manifest the gate reads |
| Builds (AAB, symbols) | t1k-marketing-store-play-upload-build | Not art. Listed so art work never uploads a build |
Renderer
Section titled “Renderer”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.
Self-improvement
Section titled “Self-improvement”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.
Execution
Section titled “Execution”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.