docs(clone-app): accurate design-tokens schema + Unity screenshot note

plugins/clone-app/skills/clone-app/references/design-capture-guide.md

@@ -25,9 +25,12 @@ the build spec relies more on screenshots and says so.
 
 ## What to record in `design-tokens.json`
 
-colors · dimens (spacing + `sp` text sizes) · typography (font files, text
-sizes) · shapes (corner/radius dimens) · theme (name, parent, dark flag, items)
-· icon path · layout inventory (count + file names). The caller fills `package`.
+Top-level scalar fields always present: `package` (caller-supplied), `source`
+(always `"apk-resources"`), `framework` (detected framework string).
+Token groups — each an object with `values` and `confidence`: `colors` ·
+`dimens` (spacing + `sp` text sizes) · `typography` (font files, text sizes) ·
+`shapes` (corner/radius dimens) · `theme` (name, parent, dark flag, items) ·
+`icon` (launcher icon path) · `layouts` (count + file names).
 
 ## Turning tokens into a spec
 

plugins/clone-app/skills/clone-app/references/unity-re-guide.md

@@ -24,6 +24,9 @@ Best case — full logic recovered.
 `unity-assets.sh <apk> <out>` wraps **AssetRipper**
 (https://github.com/AssetRipper/AssetRipper). Extracts textures, sprites, UI
 atlases, fonts, audio, shaders, **scenes, prefabs** → the game's design system.
+Play screenshots are also downloaded to `$WORK/screenshots/` (via
+`scrape-play-store.py`) and are the **primary layout reference** for Unity since
+Android `res/` is absent.
 
 ## Graceful degradation