@maccesar/titools 3.3.0 → 4.0.0

package/skills/purgetss/references/svg-pipeline.md

@@ -0,0 +1,249 @@
+# SVG-Aware Compile-Time Image Pipeline
+
+Added in PurgeTSS v7.11.0 (refined in v7.11.1), the SVG pipeline runs as a **post-step of `purgetss`** — after the regular purge finishes and `app.tss` is finalized. It scans your views and controllers for SVG references, resolves each SVG's display size from the utility classes on the same node, and generates the matching multi-density PNGs. You do **not** call `purgetss images` separately or declare dimensions anywhere else. The cascade of `w-*` / `h-*` classes in your XML decides the size.
+
+For the standalone `purgetss images` command (all files under `purgetss/images/`, CLI flags, format conversion), see [Multi-density images](./multi-density-images.md).
+
+> **INFO — At a glance**
+>
+> Drop an SVG into `purgetss/images/`, reference it from a view as `image="/images/<sub>/<name>.svg"` with a numeric `w-*` or `h-*` class, and run `purgetss`. The pipeline emits 8 density variants (5 Android + 3 iPhone PNGs). Titanium loads the generated `.png` at runtime even though your XML still says `.svg`. The SVG attribute in your source is never rewritten.
+
+## Why this exists
+
+Titanium doesn't load `.svg` files natively in `Ti.UI.ImageView`. Without help you have two options, both manual:
+
+1. Hand-rasterize every SVG into `app/assets/{iphone,android}/images/.../*.png` for every density. Tedious, easy to get wrong, and easy to forget when you swap a logo.
+2. Run `purgetss images` manually after every SVG edit. Better, but still manual, and you have to know the dimensions in advance.
+
+The SVG pipeline removes both chores: you reference the `.svg` from a view, size it with the same utility classes you use everywhere else, and `purgetss` generates the PNGs on the next run.
+
+## The runtime trick
+
+When a view requests `image="/foo.svg"` and Titanium cannot use that file as SVG, the image loader falls back to a `.png` with the same basename in the platform assets folder. If PurgeTSS writes `foo.png` plus `@2x`, `@3x`, and the Android densities, the view loads correctly even though the XML still references `.svg`. The pipeline never touches the `.svg` string in your source.
+
+## How it works (the short version)
+
+```text
+purgetss
+├─ regular purge → writes app.tss with .w-32, .h-auto, .w-(300), etc.
+└─ SVG post-step:
+   1. Parse app.tss → class → props map
+   2. Scan views (.xml) and controllers (.js) for SVG references
+   3. For each SVG, resolve width/height by applying its classes against app.tss
+   4. Sync images.files in config.cjs (autoSync ON)
+   5. Generate PNGs with Sharp, using a hash-based cache to skip unchanged files
+```
+
+The pipeline only touches SVGs you actually reference from views or controllers. Files that sit in `purgetss/images/` but are not referenced anywhere are ignored by the pipeline (the standalone `purgetss images` command still processes them).
+
+## What gets detected
+
+**XML views:** any node attribute ending in `.svg` is captured along with its `class=""` attribute:
+
+```xml
+<ImageView class="w-32 h-auto" image="/images/logos/logo.svg" />
+<ImageView class="w-(300) bg-red-500" image="/images/banners/hero.svg" />
+<View backgroundImage="/images/textures/grain.svg" class="wh-screen" />
+```
+
+Both `image` and `backgroundImage` (and any other attribute whose value ends in `.svg`) are picked up.
+
+**Controllers:** objects passed to `$.UI.create(...)` (or similar) that mix `image: '...svg'` and `classes: '...'` are captured by an AST walker:
+
+```javascript
+$.UI.create('ImageView', {
+  image: '/images/logos/logo.svg',
+  classes: 'w-(300) bg-red-500'
+})
+```
+
+### Static-scanner limitation
+
+The scanner sees **literal string values only**, not computed paths. Dynamically composed paths are not detected:
+
+```javascript
+// NOT detected — path is concatenated at runtime
+image: '/images/' + variant + '.svg'
+```
+
+For dynamic references, pin the dimensions manually under `images.files` (see [Manual pinning](#manual-pinning-for-undetected-references)) so the pipeline still generates the PNGs.
+
+## How dimensions get resolved
+
+For each SVG reference, the cascade of classes is applied against `app.tss` in declaration order (later-wins, matching Alloy semantics). The pipeline pulls the final `width` and `height` numbers:
+
+| Class on the view              | What `app.tss` resolves            | What the pipeline pins                                          |
+| ------------------------------ | ---------------------------------- | -------------------------------------------------------------- |
+| `class="w-32"`                 | `width: 128`                       | `widthDp = 128`                                                |
+| `class="w-40 h-12"`            | `width: 160`, `height: 48`         | `widthDp = 160`, `heightDp = 48`                               |
+| `class="w-(300)"`              | `width: 300` (arbitrary value)     | `widthDp = 300`                                                |
+| `class="h-44"` (no `w-*`)      | `height: 176`                      | `heightDp = 176`; width derived from viewBox at generation time |
+| `class="w-32 h-auto"`          | `width: 128`, `height: Ti.UI.SIZE` | `widthDp = 128`; height derived from viewBox                   |
+| `class="w-full"` (non-numeric) | `width: Ti.UI.FILL`                | skipped with a warning; no usable dim                          |
+
+Note the spacing convention: PurgeTSS multiplies the Tailwind-style numeric scale, so `w-32` resolves to `width: 128` (128 dp), not 32.
+
+### Auto-derived dimensions stay out of config
+
+If you used `h-auto` (or no `h-*`), the height field does **not** appear in the `images.files` entry. The generator re-derives it from the SVG's `viewBox` on every run. The same applies to width when only `h-*` is pinned. This keeps stale values out of `config.cjs` — the unpinned side stays `null` and is always recomputed from the current viewBox.
+
+## Multiple references to the same SVG
+
+If two views reference the same SVG with different classes, the pipeline takes the **max of each dimension across all references**. The generated PNGs are then sharp enough for the largest use:
+
+```xml
+<!-- view A -->
+<ImageView class="w-32" image="/images/logos/logo.svg" />
+<!-- view B -->
+<ImageView class="w-(800)" image="/images/logos/logo.svg" />
+```
+
+Resolved: `widthDp = 800`. The generated PNGs cover both views; the smaller one just downsamples at runtime.
+
+## How `config.cjs` is synced (autoSync ON)
+
+After resolving dimensions, the pipeline upserts an entry in `images.files`:
+
+```javascript title="./purgetss/config.cjs"
+images: {
+  autoSync: true,
+  files: [
+    { filename: 'images/logos/logo.svg', width: 176 }
+  ]
+}
+```
+
+### The current run wins (v7.11.1 cascade policy)
+
+Policy in plain terms: **the current run's cascade wins.** If you change `w-32` to `w-40`, the entry updates to `width: 160`. If you bump back to `w-32`, it updates back to `128`. On every run, the entry mirrors what the views ask for.
+
+This is **not** a high-water mark. The old (pre-7.11.1) policy used `max(existing, derived)`, which froze sizes when you shrank a class — for example `h-52` → `h-16` kept the 208 dp height cemented in config. The 7.11.1 policy follows the cascade, so shrinks propagate correctly. Manual pinning is still available via `autoSync: false`.
+
+### Symmetric width/height cascade (v7.11.1)
+
+`deriveDimensions` accepts width-only, height-only, or both. The unpinned side stays `null` in `images.files`, and `gen-scales` derives it from the SVG viewBox on every run — no more stale auto-derived heights cemented in config. For a height-only source, `gen-scales` computes the width from the inverse aspect ratio.
+
+### No gratuitous rewrites (v7.11.1)
+
+If a run is byte-identical to the previous one (no inserts, no updates — `inserted === 0 && updated === 0`), `config.cjs` is **not** rewritten. Its `mtime` does not change, so downstream `utilities.tss` rebuilds are not triggered for nothing.
+
+### Manual mode: `autoSync: false`
+
+```javascript title="./purgetss/config.cjs"
+images: {
+  autoSync: false,
+  files: [
+    { filename: 'images/logos/logo.svg', width: 1024 }
+  ]
+}
+```
+
+With `autoSync: false`:
+
+- The pipeline still derives dimensions and generates PNGs, using the values you wrote in `images.files` — or the cascade fallback for files not listed.
+- `config.cjs` is **never** written. Those entries are yours to maintain.
+
+Use this when you want to pin sizes by hand and not have PurgeTSS overwrite your work.
+
+## Force-PNG output
+
+The SVG pipeline **always emits `.png`**, regardless of `images.format`. This is deliberate:
+
+1. Titanium's `image="/foo.svg"` fallback resolves to `.png` only. `.webp`, `.jpeg`, and `.avif` are not picked up through the `.svg` reference.
+2. Having a sibling `.webp` (or any non-`.png`) next to `.png` on disk for the same basename **breaks the fallback entirely**. Titanium then shows nothing.
+
+So even if you set `format: 'webp'` (which is honored by `purgetss images` for raster sources and unlisted SVGs), the post-purge pipeline emits `.png` for every SVG it processes. The `--debug` output line reads `png (forced; ignores format: webp)`.
+
+If you genuinely want a `.webp` of an SVG, reference it as `image="/.../foo.webp"` in your XML, not as `.svg`. The standalone `purgetss images` command will then generate `.webp` for that file. See the [WebP and SVG warning](./multi-density-images.md) in the multi-density reference.
+
+## The PNG cache
+
+PurgeTSS keeps a cache at `purgetss/.cache/svg-images.json`:
+
+```json
+{
+  "logos/logo.svg": {
+    "svgHash": "<sha1>",
+    "widthDp": 176,
+    "heightDp": null,
+    "targets": [
+      "app/assets/android/images/res-mdpi/logos/logo.png",
+      "app/assets/iphone/images/logos/logo@2x.png",
+      "..."
+    ]
+  }
+}
+```
+
+A cached entry is reused, and Sharp is **not** invoked, when all of these hold:
+
+- The SVG's bytes haven't changed (SHA-1 match).
+- `widthDp` resolved is the same as cached.
+- `heightDp` resolved is the same as cached.
+- Every target PNG path matches and exists on disk.
+
+Otherwise, PurgeTSS regenerates the image. If you `git clean`, delete a PNG by hand, or change a class in XML/JS, the next run regenerates only the affected SVGs. Unaffected entries stay cached.
+
+> **Add `purgetss/.cache/` to `.gitignore`.** It is a per-machine artifact.
+
+## Manual pinning for undetected references
+
+When the static scanner cannot see a reference (dynamic/concatenated paths) or a view has no resolvable `w-*` / `h-*` class, pin the entry by hand so the pipeline still generates the PNGs:
+
+```javascript title="./purgetss/config.cjs"
+images: {
+  files: [
+    { filename: 'images/<sub>/<name>.svg', width: 256 }
+  ]
+}
+```
+
+## Standalone command vs post-purge pipeline
+
+| Aspect                  | `purgetss` (post-purge SVG pipeline) | `purgetss images` (standalone)                    |
+| ----------------------- | ------------------------------------ | ------------------------------------------------- |
+| What it processes       | Only SVGs referenced from XML/JS     | All files under `purgetss/images/`                |
+| Source of dimensions    | Class cascade in `app.tss`           | CLI `--width` > `images.files` > viewBox / source |
+| Touches `images.files`? | Yes (autoSync ON)                    | No; only reads it as overrides                    |
+| Output format for SVGs  | Always PNG                           | PNG for SVGs in `files`; `format` otherwise       |
+| When to run             | Automatic on every `purgetss`        | Manual, after raster source edits                 |
+
+Both share the same `images.files` array and the same generation engine (`gen-scales`). They do not fight each other: the pipeline edits `images.files`; the standalone command reads it as overrides. Run either, or both.
+
+## Troubleshooting
+
+### "no class resolved width or height to a number; skipping"
+
+The SVG is referenced from a view with no resolvable `w-*` or `h-*` class (just `w-full`, `w-screen`, `bg-*`, etc.). Add a numeric `w-*` or `h-*` utility, or pin the size manually in `images.files`:
+
+```javascript
+files: [
+  { filename: 'images/<sub>/<name>.svg', width: 256 }
+]
+```
+
+### My change to a class didn't update the PNG
+
+Check that the class actually exists in `app.tss` after purging. The Tailwind-style spacing scale skips numbers like `h-50`; only `h-48`, `h-52`, `h-56` are emitted by default. Add custom values under `theme.extend.spacing` if you need them, or use arbitrary values: `h-(50)`, `h-(200px)`, `h-(12.5rem)`.
+
+If the class is correct but the image didn't refresh on device, it might be the Titanium simulator's image cache. Do a clean build.
+
+### The pipeline didn't detect my SVG reference
+
+The static scanner sees literal string values, not computed paths. Concatenated strings (`'/images/' + variant + '.svg'`) are not detected. Pin the entry in `images.files` manually so the pipeline still generates the PNGs.
+
+### `<ImageView image="/.../foo.svg" />` shows nothing
+
+Two common causes:
+
+1. There is no `.png` next to the `.svg`. Titanium falls back from `.svg` references to `.png` siblings; if the pipeline hasn't generated them yet, the fallback can't fire. Run `purgetss` (or `purgetss images`) and verify the `.png` exists under `app/assets/iphone/images/` and `app/assets/android/images/res-*/`.
+2. Both `.png` and `.webp` (or another non-png) sit next to each other for the same basename. That breaks the fallback entirely. Delete the non-`.png` siblings, or let the force-PNG pipeline own the SVG.
+
+### I want to opt out for a specific run
+
+Switch `autoSync: false` and manage the `images.files` entries yourself, or delete the SVG cache entry. The pipeline still derives dimensions and generates the PNGs so views keep working, but it does not write to `config.cjs`.
+
+## See also
+
+- [Multi-density images](./multi-density-images.md) — the standalone `purgetss images` command, `--width`, format conversion, and `images.files` overrides.
+- [PurgeTSS Configuration Deep Dive](./customization-deep-dive.md) — the `images:` config block and the config syntax validator.

package/skills/purgetss/references/tikit-components.md

@@ -316,7 +316,7 @@ Colors: `black`, `dark`, `light`, and `white` themes that affect background and
 
 Use this for code examples. Set `copy="true"` to add a copy button.
 
-**Pro tip — recommended monospace fonts:** For best results, install a monospaced font (like Fira Code or JetBrains Mono) and configure `font-mono` in your PurgeTSS config. (Source: official tikit docs, `tikit.md` line ~390.)
+**Pro tip — recommended monospace fonts:** For best results, install a monospaced font (like Fira Code or JetBrains Mono) and configure `font-mono` in your PurgeTSS config. (Source: the official tikit docs.)
 
 **Localization:** The copy button uses `L('copy', 'Copy')` for its title and `L('code_copied', 'Code copied!')` for the confirmation message. Add these keys to your `strings.xml` files for translation.
 
@@ -512,4 +512,4 @@ You can mix and match icons from different libraries throughout your app.
 
 ## License
 
-TiKit UI Components is open source under the MIT License (Copyright 2023-2025 Cesar Estrada).
+TiKit UI Components is open source under the MIT License (Copyright (c) 2023-2025 César Estrada).

package/skills/purgetss/references/titanium-resets.md

@@ -30,7 +30,7 @@ The most important reset is for the `View` element. By default, `View` is set to
 - Grow to accommodate explicit dimensions (`w-64`, `h-32`, etc.)
 - Expand to fill margins (`m-4`, `mx-2`, `mt-6 mb-4`, etc.)
 
-> **See also**: the "Explicit SIZE vs native undefined" callout under [Community-Discovered Patterns](#community-discovered-patterns) explains when to use `h-auto`, `w-auto`, and `wh-auto` to prevent unwanted stretching.
+> **See also**: [Width/Height Inheritance](#widthheight-inheritance) explains when to use `h-auto`, `w-auto`, and `wh-auto` to prevent unwanted stretching.
 
 ### Practical Examples
 
@@ -264,7 +264,7 @@ This generates classes for ALL color properties:
 When PurgeTSS generates your `app.tss`, these resets appear first:
 
 ```tss
-/* PurgeTSS v7.6.0 */
+/* PurgeTSS v7.11.1 */
 /* Created by César Estrada */
 /* https://purgetss.com */
 

package/skills/purgetss/references/ui-ux-design.md

@@ -75,7 +75,8 @@ The catalog below collects real-world UI patterns verified against Titanium's co
 ```xml
 <View class="horizontal border-b border-gray-200 bg-white">
   <View class="ml-4 my-4 rounded-full-12 bg-blue-500">
-    <Label class="center text-lg font-bold text-white" text="JD" />
+    <!-- A child with no top/left centers itself in a composite parent -->
+    <Label class="text-lg font-bold text-white" text="JD" />
   </View>
 
   <View class="vertical ml-3 my-4">
@@ -93,7 +94,7 @@ The catalog below collects real-world UI patterns verified against Titanium's co
     <ItemTemplate name="cardTemplate" class="h-20">
       <View bindId="container" class="horizontal mx-4 my-2 rounded-lg bg-white shadow-lg">
         <View bindId="iconWrap" class="ml-4 my-4 rounded-full-10 bg-blue-100">
-          <Label bindId="icon" class="center fas fa-home text-blue-500" />
+          <Label bindId="icon" class="fas fa-home text-blue-500" />
         </View>
 
         <View class="vertical ml-3 my-4">
@@ -190,8 +191,9 @@ For an icon-with-text pair, use a horizontal `View` containing an icon `Label` a
 
 ```xml
 <View class="h-14 w-screen bg-white border-b border-gray-200">
-  <Label class="left-4 center text-lg font-bold text-gray-800" text="Dashboard" />
-  <Label class="right-4 center fas fa-bars text-gray-700" />
+  <!-- Omitting top/bottom lets each child center vertically in the composite bar -->
+  <Label class="left-4 text-lg font-bold text-gray-800" text="Dashboard" />
+  <Label class="right-4 fas fa-bars text-gray-700" />
 </View>
 ```
 
@@ -267,7 +269,7 @@ For an icon-with-text pair, use a horizontal `View` containing an icon `Label` a
 <Window class="bg-gray-100">
   <View class="vertical h-screen w-screen">
     <View class="h-14 w-screen border-b border-gray-200 bg-white">
-      <Label class="left-4 center text-xl font-bold text-gray-800" text="Screen Title" />
+      <Label class="left-4 text-xl font-bold text-gray-800" text="Screen Title" />
     </View>
 
     <ScrollView class="vertical content-w-screen content-h-auto">

package/skills/purgetss/references/version-history.md

@@ -8,6 +8,18 @@ When in doubt about whether a class, flag, or config key exists in the user's in
 
 ---
 
+## v7.11.1
+- Symmetric width/height cascade in the SVG image pipeline: a class can pin width-only, height-only, or both; the unpinned side stays `null` in `images.files` and is re-derived from the SVG viewBox on every run (no stale auto-derived dimensions frozen in config).
+- `syncConfigImages` mirrors the **current** run instead of taking `max()` across past runs — shrinking a class (e.g. `h-52` → `h-16`) now propagates to `config.cjs`. Pin manually with `images.autoSync: false`.
+- Fix: `purgetss images` respects `--yes` for overwrite confirmations (prompt no longer reappears).
+- Fix: SVGs listed in `images.files` always emit `.png` regardless of `images.format` (Titanium's `.svg → .png`-only runtime fallback). Raster files and SVGs not in `images.files` still honor `format`.
+
+## v7.11.0
+- SVG-aware compile-time image pipeline runs as a `purgetss` post-step. When XML/controllers reference `image="/images/x.svg"` (or `backgroundImage`) alongside utility classes that resolve to numeric width/height (`w-32`, `w-(300)`, `h-auto`), purge compiles the SVG into the 8 Titanium density PNGs (5 Android + 3 iPhone) using dimensions resolved from `app.tss`. Titanium loads the generated `.png` at runtime; the `.svg` attribute in your source is never rewritten. Cache: `purgetss/.cache/svg-images.json` (add to `.gitignore`). See [multi-density-images.md](multi-density-images.md).
+- `images.files` array in `config.cjs` — per-file width/height override: `[{ filename: 'images/logos/logo.png', width: 128, height: 52 }]`. CLI `--width` still wins over entries. SVGs detected by the pipeline populate entries automatically (subject to `images.autoSync`); hand-added raster entries survive untouched.
+- `images.autoSync` boolean (default `true`) — opt-out for devs managing `images.files` by hand. When `false`, purge still computes dimensions and generates PNGs but never writes back to `config.cjs`.
+- `config.cjs` syntax validator emits a formatted `Config Syntax Error` block (file, JSON path, context, issue, fix snippet) for type mismatches in known fields, currently `theme.fontFamily.*` — must be a **string** — replacing cryptic crashes like `rule.startsWith is not a function`.
+
 ## v7.10.2
 - Pre-v7.7.0 `brand:` configs (flat layout: `brand.padding: <number>`, `brand.iosPadding`, `brand.bgColor`, top-level `brand.notification`/`brand.splash`) auto-migrate to the grouped layout in memory. A one-time per-session notice lists the migrated keys.
 

package/skills/ti-api/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: ti-api
+description: 'Use when looking up properties, methods, events, constants, or type signatures for any Titanium API: `Ti.UI`, `Ti.Android`, `Ti.App`, `Ti.Media`, `Ti.Network`, `Ti.Database`, `Ti.Filesystem`, `Ti.Geolocation`, `Ti.Contacts`, `Ti.Calendar`, `Global`, `Ti.XML`, or third-party modules (Map, BLE, NFC, Facebook, Identity, CoreMotion, URLSession). Triggers include `tiapp.xml` in the project root, or any code that references `Ti.*` or `Modules.*`.'
+---
+
+# ti-api
+
+## Overview
+
+API reference for the Titanium SDK and TiDev-maintained modules. Use it to look up properties, methods, events, constants, and type signatures across ~360 APIs grouped into 20 reference files.
+
+## When to use
+
+Use this skill when:
+
+- Writing or reviewing code that calls any `Ti.*` or `Modules.*` API
+- Verifying a property name, type, default, or platform availability
+- Confirming a method signature, parameter list, or return type
+- Looking up event names and event-object payloads
+- Checking platform support (`android`, `ios`, or `both`) for an API
+
+Do NOT use for:
+
+- Alloy MVC concepts, controllers, models (use `alloy-guides`)
+- Alloy CLI and configuration files (use `alloy-howtos`)
+- Titanium project setup, `tiapp.xml`, distribution, Hyperloop (use `ti-guides`)
+- Native module dependency updates (use `ti-module-update`)
+
+## How to use this skill
+
+1. Identify which namespace the API belongs to.
+2. Look up the matching reference file in the table below.
+3. Read the reference file for full property / method / event tables.
+
+## Namespace lookup
+
+| Namespace examples | Reference | Coverage |
+|---|---|---|
+| `Ti.UI.View`, `Ti.UI.Label`, `Ti.UI.Button`, `Ti.UI.ImageView`, ... | [api-ui-views.md](references/api-ui-views.md) | Ti.UI Core Views (13 APIs) |
+| `Ti.UI.Window`, `Ti.UI.NavigationWindow`, `Ti.UI.TabGroup`, `Ti.UI.Tab`, ... | [api-ui-windows-navigation.md](references/api-ui-windows-navigation.md) | Ti.UI Windows & Navigation (7 APIs) |
+| `Ti.UI.TextField`, `Ti.UI.TextArea`, `Ti.UI.SearchBar`, `Ti.UI.AttributedString`, ... | [api-ui-text-input.md](references/api-ui-text-input.md) | Ti.UI Text & Input (9 APIs) |
+| `Ti.UI.ListView`, `Ti.UI.ListItem`, `Ti.UI.ListSection`, `Ti.UI.TableView`, ... | [api-ui-lists.md](references/api-ui-lists.md) | Ti.UI Lists & Tables (8 APIs) |
+| `Ti.UI.Animation`, `Ti.UI.Matrix2D`, `Ti.UI.Matrix3D`, `Ti.UI.WebView`, ... | [api-ui-extras.md](references/api-ui-extras.md) | Ti.UI Extras (13 APIs) |
+| `Ti.UI.iOS` | [api-ui-ios.md](references/api-ui-ios.md) | Ti.UI.iOS (36 APIs) |
+| `Ti.UI.iOS` Animator / Physics | [api-ui-ios-animator.md](references/api-ui-ios-animator.md) | Ti.UI.iOS Animator & Physics (8 APIs) |
+| `Ti.UI.Android`, `Ti.UI.iPad` | [api-ui-android.md](references/api-ui-android.md) | Ti.UI.Android (10 APIs) |
+| `Ti.Android`, `Ti.Android.ActionBar`, `Ti.Android.Activity`, ... | [api-android.md](references/api-android.md) | Ti.Android (17 APIs) |
+| `Ti.App`, `Ti.App.Properties`, `Ti.App.iOS`, `Ti.Platform`, ... | [api-app-platform.md](references/api-app-platform.md) | Ti.App & Ti.Platform (18 APIs) |
+| `Ti.Media`, `Ti.Media.AudioPlayer`, `Ti.Media.AudioRecorder`, ... | [api-media.md](references/api-media.md) | Ti.Media (9 APIs) |
+| `Ti.Network`, `Ti.Database`, `Ti.Database.DB`, `Ti.Filesystem`, ... | [api-data-network.md](references/api-data-network.md) | Ti.Network, Ti.Database & Ti.Filesystem (14 APIs) |
+| `Ti.Geolocation`, `Ti.Contacts`, `Ti.Calendar`, `Ti.WatchSession`, ... | [api-services.md](references/api-services.md) | Ti.Geolocation, Ti.Contacts, Ti.Calendar & Ti.WatchSession (15 APIs) |
+| `Titanium`, `Ti.UI` (root), `Ti.API`, `Ti.Accelerometer`, ... | [api-core.md](references/api-core.md) | Ti Core (16 APIs) |
+| `Ti.XML`, `Ti.XML.Attr`, `Ti.XML.CDATASection`, Global APIs | [api-xml-global.md](references/api-xml-global.md) | Ti.XML & Global (25 APIs) |
+| `Modules.Map`, `Modules.Map.Annotation`, `Modules.Map.Camera`, ... | [api-modules-map.md](references/api-modules-map.md) | Modules: Map (11 APIs) |
+| `Modules.Applesignin`, `Modules.Barcode`, `Modules.Crypto`, Facebook, Identity, ... | [api-modules-social-misc.md](references/api-modules-social-misc.md) | Modules: Facebook, Identity, Crypto & More (16 APIs) |
+| `Modules.BLE`, `Modules.BLE.Beacon`, `Modules.BLE.BeaconRegion`, ... | [api-modules-ble-bluetooth.md](references/api-modules-ble-bluetooth.md) | Modules: BLE & Bluetooth (20 APIs) |
+| `Modules.Nfc`, `Modules.Nfc.MifareTagTechnology`, `Modules.Nfc.NdefMessage`, ... | [api-modules-nfc.md](references/api-modules-nfc.md) | Modules: NFC (28 APIs) |
+| `Modules.CoreMotion`, `Modules.CoreMotion.Accelerometer`, URLSession, ... | [api-modules-coremotion-urlsession.md](references/api-modules-coremotion-urlsession.md) | Modules: CoreMotion & URLSession (12 APIs) |
+
+## Quick lookup by common task
+
+| Task | API | Reference |
+|---|---|---|
+| Create a window | `Ti.UI.Window` | [api-ui-windows-navigation.md](references/api-ui-windows-navigation.md) |
+| HTTP request | `Ti.Network.HTTPClient` | [api-data-network.md](references/api-data-network.md) |
+| Show an alert | `Ti.UI.AlertDialog` | [api-ui-windows-navigation.md](references/api-ui-windows-navigation.md) |
+| Play audio | `Ti.Media.AudioPlayer` | [api-media.md](references/api-media.md) |
+| Read a file | `Ti.Filesystem.File` | [api-data-network.md](references/api-data-network.md) |
+| SQLite query | `Ti.Database.DB` | [api-data-network.md](references/api-data-network.md) |
+| GPS location | `Ti.Geolocation` | [api-services.md](references/api-services.md) |
+| Push notifications | `Ti.App.iOS` / Android FCM | [api-app-platform.md](references/api-app-platform.md) |
+| ListView | `Ti.UI.ListView` | [api-ui-lists.md](references/api-ui-lists.md) |
+| Camera / gallery | `Ti.Media` | [api-media.md](references/api-media.md) |
+| Map view | `Modules.Map.View` | [api-modules-map.md](references/api-modules-map.md) |
+| BLE scanning | `Modules.BLE` | [api-modules-ble-bluetooth.md](references/api-modules-ble-bluetooth.md) |
+| Animation | `Ti.UI.Animation` | [api-ui-extras.md](references/api-ui-extras.md) |
+| WebView | `Ti.UI.WebView` | [api-ui-extras.md](references/api-ui-extras.md) |
+| Contacts | `Ti.Contacts` | [api-services.md](references/api-services.md) |
+
+## Reading the reference tables
+
+Each API entry includes:
+
+- **Summary** — one-line description
+- **Extends** — parent type (inherited properties / methods are not repeated)
+- **Platforms** — `both` (Android + iOS), `android`, or `ios`
+- **Properties table** — unique properties (not inherited), with type, default, platform
+- **Methods table** — unique methods with parameters, return type, platform
+- **Events table** — unique events with platform and description
+- **Related Types** — inline struct definitions used by that API
+
+### Property counts
+
+Tables show `unique: X / Y` where `X` is properties defined on this class and `Y` is total including inherited. For inherited properties, check the parent class.
+
+## API coverage
+
+| Category | APIs | Reference |
+|---|---|---|
+| Ti.UI Core Views | 13 | `api-ui-views.md` |
+| Ti.UI Windows & Navigation | 7 | `api-ui-windows-navigation.md` |
+| Ti.UI Text & Input | 9 | `api-ui-text-input.md` |
+| Ti.UI Lists & Tables | 8 | `api-ui-lists.md` |
+| Ti.UI Extras | 13 | `api-ui-extras.md` |
+| Ti.UI.iOS | 36 | `api-ui-ios.md` |
+| Ti.UI.iOS Animator & Physics | 8 | `api-ui-ios-animator.md` |
+| Ti.UI.Android | 10 | `api-ui-android.md` |
+| Ti.Android | 17 | `api-android.md` |
+| Ti.App & Ti.Platform | 18 | `api-app-platform.md` |
+| Ti.Media | 9 | `api-media.md` |
+| Ti.Network, Ti.Database & Ti.Filesystem | 14 | `api-data-network.md` |
+| Ti.Geolocation, Ti.Contacts, Ti.Calendar & Ti.WatchSession | 15 | `api-services.md` |
+| Ti Core | 16 | `api-core.md` |
+| Ti.XML & Global | 25 | `api-xml-global.md` |
+| Modules: Map | 11 | `api-modules-map.md` |
+| Modules: Facebook, Identity, Crypto & More | 16 | `api-modules-social-misc.md` |
+| Modules: BLE & Bluetooth | 20 | `api-modules-ble-bluetooth.md` |
+| Modules: NFC | 28 | `api-modules-nfc.md` |
+| Modules: CoreMotion & URLSession | 12 | `api-modules-coremotion-urlsession.md` |
+
+## Related skills
+
+| Task | Use this skill |
+|---|---|
+| Alloy MVC concepts, controllers, models, data binding | `alloy-guides` |
+| Alloy CLI, `alloy.jmk`, `config.json`, debugging | `alloy-howtos` |
+| Titanium SDK config, Hyperloop, app distribution | `ti-guides` |
+| Native module dependency updates | `ti-module-update` |