CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity

0.5.0: mobile apps and games positioning (README, site, og image, skills, CLI, MCP, adapters), MCP tools for subscriptions and catalog diff, tests, changelog

Browse source
This commit is contained in:
CRTkafa 2026-10-11 01:47:09 +08:00
parent 205f65828f
commit c48eead0e0
51 changed files with 960 additions and 318 deletions
Download patch file Download diff file Expand all files Collapse all files

23
skills/portfolio-originality/SKILL.md
View file

@ -1,41 +1,42 @@
---
name: portfolio-originality
description: Originality gate for studios that ship many similar mobile games - score a planned or finished game against the studio's own catalogue (mechanic, content, art, metadata, screenshots), require a clear differentiator, and suggest merging thin ideas, to avoid App Store Guideline 4.3 (spam) and Play repetitive content rejections. Use before starting a new game, before submitting one, or after a 4.3 / "repetitive content" rejection.
description: Originality gate for studios and developers that ship many similar mobile apps or games (templates, white-label apps, reskins) - score a planned or finished app or game against your own catalogue (mechanic, content, art, metadata, screenshots), require a clear differentiator, and suggest merging thin ideas, to avoid App Store Guideline 4.3 (spam) and Play repetitive content rejections. Use before starting a new app or game, before submitting one, or after a 4.3 / "repetitive content" rejection.
---
# Portfolio originality (Guideline 4.3 gate)
Apple 4.3 and Play's repetitive content policy reject apps that are near-copies of other apps, **including your own**.
Studios with a template engine hit this first. Run this gate twice: before building (idea stage) and before submitting.
Studios with a template engine and white-label / reskinned apps hit this first. Run this gate twice: before building (idea stage) and before submitting.
## Inputs
- The new game: one-paragraph pitch, core loop, controls, progression, art direction, the planned listing (name,
- The new app or game: one-paragraph pitch, core loop or main task, controls or flows, progression or features, art
direction, the planned listing (name,
subtitle, short description, keywords, screenshot captions).
- The catalogue: the same for every game the studio has published or submitted (store links are fine).
- The catalogue: the same for every app or game you have published or submitted (store links are fine).
## Score each pair (new game vs each catalogue game), 0 = identical, 2 = clearly different
## Score each pair (new app vs each catalogue app), 0 = identical, 2 = clearly different
| axis | 0 | 1 | 2 |
|---|---|---|---|
| core mechanic | same verb, same rules | same verb, new rule that changes decisions | different verb / goal |
| core mechanic or main task | same verb, same rules | same verb, new rule that changes decisions | different verb / goal |
| content | same levels / items reskinned | new content, same structure | different structure (modes, progression) |
| art and audio | same assets / palette / UI kit | same kit, new theme | own visual identity |
| metadata | same description pattern / keywords | rewritten, same promises | different promise and audience |
| screenshots | same layout and captions | same layout, new captions | different scenes and message |
Total 0-10 per pair. **Below 6 against any catalogue game: stop.** 6-7: ship only with a differentiator a player can
Total 0-10 per pair. **Below 6 against any catalogue app: stop.** 6-7: ship only with a differentiator a user can
see in the first screenshot. 8+: fine.
## Differentiator test
Write one sentence: "Unlike <our other game>, in <new game> the player <does something they cannot do there>."
Write one sentence: "Unlike <our other app>, in <new app> the user <does something they cannot do there>."
If the sentence needs the words "theme", "skin", "colours" or "levels" to work, it is not a differentiator.
## When the score is low
- **Merge** the idea into the existing game as a mode, world or event instead of a new app.
- **Merge** the idea into the existing app as a mode, feature, world or event instead of a new app.
- **Deepen** one axis until it scores 2 (usually mechanic or progression), not five axes a little.
- Never vary only the name, icon and keywords: reviewers compare binaries and screenshots, and that is the pattern
4.3 describes.
- After a 4.3 rejection: list the concrete differences in the reply (`review-rejections`); if there are none, merge.
## Output for the owner
A table per catalogue game with the five scores, the total, the differentiator sentence, and a recommendation:
ship / ship after <change> / merge into <game>.
A table per catalogue app with the five scores, the total, the differentiator sentence, and a recommendation:
ship / ship after <change> / merge into <app>.