originality-check

1# Originality Check
2 
3Decide, with evidence, whether an app is *distinct enough to exist* — before you build it or submit it.
4 
5> At portfolio scale, shipping many similar small apps risks **Guideline 4.3 (spam / duplicate)**
6> — this is the go/no-go distinctness gate that keeps that from happening.
7 
8## Where it fits (read the seams)
9 
10- **Not `rejection-handler`.** That works a rejection you *already have*. This is upstream — it
11  prevents the 4.3 by catching sameness before you ship.
12- **Not `competitive-analysis` / `market-research`.** Those size demand and position you in the
13  market. This judges *distinctness* (function + content + metadata) vs your own portfolio and vs
14  near-identical competitors — a spam risk, not a demand question.
15- **Two moments to run it:** at `validate` / `new-app` (don't build a dup) and before `submit`
16  (don't trip 4.3). Also periodically across the portfolio (internal cannibalization / template-sameness).
17 
18## Prerequisites
19 
20- The app idea or a shipped app to evaluate (name, one-line function, target metadata).
21- Optional: `.planning/VALIDATION.md` (competitor + market data). If missing/stale, gather fresh
22  via WebSearch or the `product/competitive-analysis` skill.
23- Optional ASC access to read the developer's existing portfolio (`list_apps` / `get_metadata`).
24 
25## Flow
26 
271. **Internal check (your own portfolio).** `list_apps` → for each shipped app read its positioning
28…