You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Use Descriptor** when you target multiple screen sizes, need Android precision, or want live adaptability — **recommended**.
146
+
**Use JSON Capture** when you want a quick pixel-perfect result on a single device or to verify layout visually.
147
+
148
+
---
149
+
132
150
## Quick start
133
151
134
-
### 1. Wrap your screen
152
+
### Option A — Descriptor ⭐ (recommended, cross-platform)
153
+
154
+
The inspector can **auto-generate** a `.ts` descriptor from your live layout. Click **Save Descriptor (.ts)** after capturing — it writes a starting-point `.ts` file you can refine. Or write one by hand:
> `<Skeleton>` measures its own width via `onLayout` and runs `computeLayout()` automatically — no manual width tracking needed. Works identically on iOS and Android at any screen size.
203
+
204
+
### Option B — JSON Capture (pixel-perfect on capture device)
205
+
206
+
Run the [Skeleton Inspector](#capturing-skeletons-with-skeleton-inspector), click **Capture → Save skeletons.json**, then use the generated file:
After saving, the inspector shows a **ready-to-paste code snippet** with the exact import line and `<Skeleton>` usage — just copy and drop it into your screen file.
336
+
255
337
---
256
338
257
339
## Using saved skeletons
@@ -558,7 +640,7 @@ We welcome contributions of all sizes — bug fixes, new features, docs improvem
0 commit comments