@maccesar/titools 2.7.2 → 2.9.0

package/skills/ti-branding/SKILL.md

@@ -1,230 +0,0 @@
----
-name: ti-branding
-description: "Generate complete app branding assets for modern Titanium SDK 13.x projects — launcher icons, adaptive icons, splash-screen icons, notification icons, and marketplace artwork — from a single SVG or PNG master. Use when the user asks to brand their app, update the app icon, set up splash screens, prepare store assets, fix generic/placeholder icons, add a notification icon, generate a launcher for Android 8+/13+, replace the TiTools default icon, or anything related to visual identity of a Titanium app (Alloy or Classic). Auto-detects Alloy vs Classic layout. Outputs iOS `DefaultIcon.png` (alpha-preserved source) + `DefaultIcon-ios.png` (alpha-flattened for Apple), Android adaptive triplet (foreground + background + monochrome) across 5 densities, Android legacy launcher × 5, marketplace artwork (1024² + 512², alpha-preserved), and optionally notification icons and Android 12+ splash icons. Targets SDK 13.0–13.2 minimums without legacy cruft (post-Xcode 14 iOS minimums, no 9-patch splash, no pre-adaptive Android icons). Delegates raster work to ImageMagick + librsvg (system tools) — zero npm/pip dependencies. Invoke this skill whenever the user mentions icons, splash screens, branding, launcher, adaptive icon, mipmap, appiconset, DefaultIcon, iTunesConnect, Play Store artwork, or any visual asset for a Titanium app."
-argument-hint: "[master-path] [--bg-color <hex>] [--padding <pct>] [--with-notification] [--with-splash-icon] [--cleanup-legacy] [--aggressive] [--in-place] [--monochrome-master <path>] [--notes] [--dry-run]"
-allowed-tools: Read, Glob, Bash, Write, Edit
----
-
-# Titanium branding — icons and splash screens
-
-Generate the full set of launcher icons, adaptive icons, splash icons, notification icons, and marketplace artwork for a Titanium SDK 13.x project from ONE master input. Non-destructive by default (dry-run first, confirm before overwriting).
-
-## When to invoke this skill
-
-Invoke proactively whenever the user's work touches any of:
-
-- Replacing the generic/placeholder icon that ships with new Titanium projects
-- Adding brand identity (logo-based launcher) to an app
-- Fixing "my icon looks pixelated / pegado / cut-off on Android"
-- Setting up the Android 12+ splash screen with a custom background color
-- Generating notification icons for Firebase Cloud Messaging / local reminders
-- Preparing App Store / Google Play artwork for a release build
-- Updating icons after a rebrand or logo refresh
-- Generating adaptive icon foreground / background / monochrome layers
-- Migrating a legacy project to modern Android adaptive icons
-
-## What gets generated
-
-Every invocation produces (in a staging directory, reviewed before copy):
-
-| Asset | Path in project | Why |
-|---|---|---|
-| `DefaultIcon.png` (1024×1024, alpha preserved) | Project root | Universal source — Titanium's `ti create` template ships this with alpha. Used for Android / Alloy references and as the alpha-intact source of truth. |
-| `DefaultIcon-ios.png` (1024×1024, no alpha) | Project root | iOS SDK generates the full appiconset from this at build time. Flattened because Apple rejects alpha channels on App Store icon uploads. |
-| `iTunesConnect.png` (1024×1024, alpha preserved) | Project root | App Store artwork template. Matches `ti create` default — alpha preserved so the developer can composite over any background before upload. |
-| `MarketplaceArtwork.png` (512×512, alpha preserved) | Project root | Google Play feature graphic template. Matches `ti create` default — alpha preserved. |
-| `ic_launcher_foreground.png` × 5 densities | `app/platform/android/res/mipmap-{m,h,x,xx,xxx}hdpi/` | Adaptive icon foreground layer. Logo centered in 108dp canvas with configurable padding (default 22% ≈ 66dp safe-zone). |
-| `ic_launcher_background.png` × 5 densities | idem | Adaptive icon background layer — solid `--bg-color`. |
-| `ic_launcher_monochrome.png` × 5 densities | idem | Android 13+ themed icons (all non-transparent pixels → white). |
-| `ic_launcher.png` × 5 densities (legacy) | idem | Fallback for Android < 8 (~3% of users in 2026). |
-| `ic_launcher.xml` | `app/platform/android/res/mipmap-anydpi-v26/` | Adaptive icon definition that binds the 3 layers. |
-
-Optional (flags):
-
-| Asset | Flag | Path |
-|---|---|---|
-| `ic_stat_notify.png` × 5 densities (white + alpha) | `--with-notification` | `app/platform/android/res/drawable-{m,h,x,xx,xxx}hdpi/` |
-| `splash_icon.png` × 5 densities | `--with-splash-icon` | idem (drawable-*) — for Android 12+ `windowSplashScreenAnimatedIcon` |
-
-For Classic projects (Resources/ layout), paths resolve to `Resources/android/...` instead of `app/platform/android/...`.
-
-## Dependencies
-
-- **ImageMagick 7.x** (required) — raster ops. `brew install imagemagick` / `apt install imagemagick`
-- **librsvg** (optional, only if input is SVG) — SVG → PNG rasterization. `brew install librsvg` / `apt install librsvg2-bin`
-- **Python 3** (optional, only for `--with-notification` alpha-mask extraction) — stdlib only, no pip install needed
-
-The skill's `scripts/lib/deps.sh` detects missing tools and prints OS-specific install instructions. Do not attempt to auto-install.
-
-## Invocation
-
-Main entry point: `scripts/ti-branding`. The skill runs it via Bash and then handles the review/copy workflow in Claude.
-
-```bash
-bash scripts/ti-branding <master> [options]
-```
-
-Options:
-
-| Flag | Default | Purpose |
-|---|---|---|
-| `--bg-color <hex>` | `#FFFFFF` | Solid color for adaptive background layer. Also used for iOS alpha flatten. |
-| `--padding <pct>` | `20` | Safe-zone padding per side. Material spec floor is 19.44% — default of 20 gives a tiny buffer while keeping the logo visibly prominent across launcher masks. Range 0–40. |
-| `--ios-padding <pct>` | `4` | iOS + marketplace aesthetic padding per side. iOS icons have no launcher mask — this is purely aesthetic breathing room. Apple's HIG + production apps typically use 2-6%. Override with `--ios-padding 8` for more conservative (prior default) or `--ios-padding 2` for near-edge La Baraja-style. Range 0–40. |
-| `--with-notification` | off | Emit `ic_stat_notify.png` × 5 densities. |
-| `--with-splash-icon` | off | Emit `splash_icon.png` × 5 densities (Android 12+ SplashScreen API). |
-| `--cleanup-legacy` | off | After generating (or standalone), scan the project for legacy branding artifacts — iOS launch image PNGs, Android `default.png`, `appicon.png`, `res-long-*/res-notlong-*`, etc. — and remove them. Context-aware: reads `tiapp.xml` to decide what's safe. See `references/cleanup-legacy.md`. |
-| `--aggressive` | off | With `--cleanup-legacy`, also remove `ldpi` density folders (<1% of active devices globally in 2026). Off by default to be conservative. |
-| `--output <dir>` | `<project>/.ti-branding/` | Staging directory. Review before copying to `app/`. |
-| `--in-place` | off | Skip the staging directory and write files directly into the project root. **Overwrites existing icons.** Ideal right after `ti create` when you want to replace the default Titanium/Alloy icons in one command. `--output` takes precedence if both are passed. |
-| `--monochrome-master <path>` | — | Optional dedicated silhouette master for `ic_launcher_monochrome.png` + `ic_stat_notify.png`. Use this when your colored logo has multi-color detail that would collapse into a featureless blob when naively whitened (e.g. a painter's palette with 4 color dots — provide a monochrome variant with cutout holes instead so the detail survives in themed icons and notification status bar). Falls back to whitening the main master when not provided. |
-| `--notes` | off | Print the full tiapp.xml snippets (iOS launch storyboard, Android launcher wiring, Android 12+ splash theme with Option A/B, FCM notification tint) and the padding tuning guide. Default output is a compact summary (~15 lines). |
-| `--dry-run` | off | Print what would be generated/removed without writing or deleting. Works with both generation and `--cleanup-legacy`. |
-
-## Safety reminders
-
-This skill writes PNGs and an XML file into the project's `app/platform/android/res/` and `app/assets/iphone/` paths, and with `--cleanup-legacy` it deletes obsolete branding artifacts. The flow is designed to be safe (staging → review → copy, dry-run first, `tiapp.xml`-driven safety rules), but the user should commit the project before running destructive operations so that `git restore` is available as a rollback. The tool is provided AS IS under the MIT License. No warranty, no liability — see the repository's `LICENSE`.
-
-## Workflow
-
-1. **Detect project layout** — look for `app/` (Alloy) or `Resources/` (Classic). If neither, error.
-2. **Validate master** — run `scripts/lib/validate.sh` to confirm dimensions ≥ 1024×1024, square, and check for alpha-bleed at edges.
-3. **Check dependencies** — `scripts/lib/deps.sh` verifies `magick` + (if SVG) `rsvg-convert`.
-4. **Prepare master** — `scripts/lib/prepare-master.sh` converts SVG → 1024×1024 PNG with transparency preserved, or normalizes PNG input. Auto-crops transparent padding already in the source.
-5. **Generate assets** — call `gen-ios.sh`, `gen-android-adaptive.sh`, `gen-android-legacy.sh`, `gen-marketplace.sh` (and optionally `gen-notification.sh`, `gen-splash-icon.sh`). All outputs land in the staging directory.
-6. **Review with user** — show a diff of what will be overwritten in the project. Ask for explicit confirmation.
-
-   When opening generated PNGs for visual review, use the OS-native **lightweight previewer** — not whatever app the user has configured as the default PNG handler. Otherwise heavy editors like Affinity, Photoshop, or GIMP launch for a simple 3-file preview, which is annoying. Commands by OS:
-
-   - **macOS**: `open -a Preview <file>...` — Preview.app ships with every Mac, lightweight, always available.
-   - **Linux**: `xdg-open <file>` — desktop-agnostic, honors the user's registered image viewer. If you need something specific, `eog` (GNOME) / `gwenview` (KDE) / `feh` are common lightweight viewers. Prefer `xdg-open` as the portable default.
-   - **Windows**: `start "" <file>` (cmd) or `Invoke-Item <file>` (PowerShell). Windows doesn't ship a universal lightweight viewer equivalent to Preview — it uses whatever the user set (Photos app by default on Windows 10/11). Live with that.
-
-   Only preview 2–3 representative assets (e.g. `DefaultIcon-ios.png`, the highest-density `ic_launcher_foreground.png`, and — if generated — `splash_icon.png`). Do not open all 20+ PNGs.
-7. **Copy to project** — after confirmation, copy staging → target paths. Keep the staging directory for rollback.
-8. **Print tiapp.xml snippets** — do NOT edit `tiapp.xml` automatically. Print exact XML blocks for the user to review and paste manually. See `references/tiapp-xml-snippets.md` for the blocks.
-9. **Suggest verification build** — `ti clean && ti build -p android -T emulator` / `-p ios -T simulator`.
-
-## Padding guidance (important)
-
-The Android adaptive icon spec defines a 108dp canvas with a 66dp safe-zone. Expressed as padding: `(108-66)/2/108 ≈ 19.44%` per side. Anything inside the safe-zone is guaranteed to be visible regardless of the launcher's mask (circle, squircle, teardrop).
-
-Defaults and recommendations:
-
-| Padding | Logo fill | When to use |
-|---|---|---|
-| `19` (spec minimum) | 62% | Intricate logos needing maximum visible detail. Risky — leaves no buffer for aggressive launcher masks. |
-| `22` (default) | 56% | Balanced: compliant with spec + 3% buffer. Recommended for most apps. |
-| `25` | 50% | Logos with fine details near edges (wordmarks, thin strokes). |
-| `28`–`32` | 44%–36% | Simple icons, single-letter monograms, bold shapes. Gives visual breathing room. |
-
-If the user reports "my logo looks pegado / cramped / cut off on edges", increase padding. If the user reports "my logo looks tiny / lost in the middle", decrease padding.
-
-## iOS notes (modern)
-
-- iOS 13+ only. Targets Titanium SDK 13.0+.
-- `DefaultIcon-ios.png` is 1024×1024 with **no alpha channel** — Apple rejects transparency. The skill flattens alpha over `--bg-color`.
-- Xcode 14+ no longer requires the full 20-size appiconset. Titanium generates all required sizes from `DefaultIcon-ios.png` at build time into `build/iphone/Assets.xcassets/AppIcon.appiconset/` — the source project only needs the master.
-- `DefaultIcon-Dark.png` and `DefaultIcon-Tinted.png` (iOS 18+) are out of scope for this skill's v1. The user can add them manually later.
-- Launch images (`Default-*@3x.png`) are intentionally NOT generated. Modern Titanium uses `<enable-launch-screen-storyboard>true</enable-launch-screen-storyboard>` which adapts to any resolution via the storyboard + `<default-background-color>`. Legacy PNG launch images are dead weight.
-
-See `references/ios-appiconset.md` for full details.
-
-## Android notes (modern)
-
-- Minimum API: 21 (Lollipop). Target: API 34 (Android 14).
-- Adaptive icons (API 26+) are the primary launcher icon. Legacy `ic_launcher.png` (flat) is included only as fallback for API 21–25.
-- Monochrome layer (API 31+) is required for themed icons. The skill generates it by tinting all non-transparent foreground pixels to pure white (`RGB 255,255,255`, alpha preserved).
-- Splash screen (API 31+) uses `windowSplashScreenBackground` + `windowSplashScreenAnimatedIcon` in the app theme. Pre-12 Android falls back to the launcher icon automatically. 9-patch `background.9.png` is obsolete — not generated.
-- Notification icons (if `--with-notification`) must be white-on-transparent. Android applies a tint at runtime based on the notification's `color` property.
-
-See `references/android-adaptive-icons.md` and `references/splash-screen-api.md` for depth.
-
-## Reference files
-
-Load these on-demand when implementing specific parts of the workflow:
-
-- `references/ti-icon-paths.md` — Canonical paths for Alloy vs Classic layouts, per Titanium SDK version.
-- `references/android-adaptive-icons.md` — Safe-zone math, densities, XML bind format, monochrome rules.
-- `references/ios-appiconset.md` — Xcode 14+ minimums, DefaultIcon pipeline, alpha flattening.
-- `references/notification-icons.md` — White-only rule, runtime tinting, size table.
-- `references/splash-screen-api.md` — Android 12+ SplashScreen vs pre-12 legacy, iOS storyboard.
-- `references/master-input-guidelines.md` — SVG best practices, PNG alpha handling, bbox auto-detection, padding ergonomics.
-- `references/tiapp-xml-snippets.md` — Copy-paste blocks for `<default-background-color>`, splash theme overrides, adaptive icon manifest entries.
-- `references/cleanup-legacy.md` — What `--cleanup-legacy` removes, why each artifact is obsolete, the `tiapp.xml`-driven safety rules, and real-world space savings from dogfooding on SNAP Gym.
-
-## Non-goals
-
-- Does not generate iOS launch image PNGs (`Default-*@3x.png`) — storyboard-driven, no longer needed.
-- Does not generate Android `background.9.png` 9-patch splash — obsolete since Ti SDK 10+.
-- Does not edit `tiapp.xml` — prints snippets only. User decides what to paste.
-- **Does not create `values-v31/splash_theme.xml`, `values/colors.xml`, or any other resource XML file that depends on project-specific config (Gradle dependencies, existing themes, etc.).** Prints snippets for the user to paste after review. The only XML file the skill does write is `mipmap-anydpi-v26/ic_launcher.xml` — that one is pure adaptive-icon binding with no external library requirements.
-- Does not install ImageMagick or librsvg — detects and instructs.
-- Does not handle `DefaultIcon-Dark.png` / `DefaultIcon-Tinted.png` in v1. Leave for a future flag if users request it.
-- Does not handle tab bar / toolbar icons. Those are in-app assets, not branding.
-
-## Known limitations
-
-### `--with-splash-icon` is "PNG-only" — wire-up is user's responsibility
-
-Titanium SDK 13.x already generates a reasonable Android 12+ splash screen automatically, using the launcher icon you just created plus the `<default-background-color>` from `tiapp.xml`. For most apps this default is good enough and requires zero extra configuration.
-
-The `--with-splash-icon` flag generates `splash_icon.png × 5 densities` for advanced users who want a splash icon visually distinct from the launcher icon. Wiring it up requires a custom theme, which has TWO flavors (both printed in the post-generation notes):
-
-- **Native platform theme** (API 31+ only, no library): uses `parent="@android:style/Theme.DeviceDefault.NoActionBar"` with `android:windowSplashScreen*` attributes. Compiles out of the box. Pre-12 devices fall back to Titanium's default splash.
-- **androidx.core:core-splashscreen library** (API 21+ backward-compat): uses `parent="Theme.SplashScreen"` with unqualified attributes. Requires adding `implementation 'androidx.core:core-splashscreen:1.0.1'` to `app/platform/android/build.gradle`.
-
-The skill does NOT auto-pick or auto-create these resource files because:
-1. The user may already have custom themes that conflict
-2. The library flavor requires modifying Gradle config (can't be reversed cleanly)
-3. `tiapp.xml` meta-data registration requires opening a possibly self-closing `<application>` tag
-
-Print both options, explain the tradeoffs, let the user decide.
-
-### Do NOT set the splash theme on `<application android:theme>` or on any `<activity>`
-
-Tempting but wrong. Titanium's `Theme.AppDerived` inherits from the `<application>` theme. Setting a NoActionBar splash theme there propagates NoActionBar to every `TiActivity` in the app, stripping the ActionBar / TitleBar from every screen globally. The only correct registration is via `<meta-data android:name="io.tidev.titanium.splash.theme">`.
-
-### `<application>` in `tiapp.xml` may be self-closing
-
-When the project's `<application>` tag is self-closing (e.g. `<application android:icon="@mipmap/ic_launcher"/>`), users must expand it before adding `<meta-data>` children:
-
-```xml
-<!-- Before (self-closing) -->
-<application android:icon="@mipmap/ic_launcher"/>
-
-<!-- After (expanded) -->
-<application android:icon="@mipmap/ic_launcher">
-  <meta-data .../>
-</application>
-```
-
-The skill's post-generation notes remind the user of this.
-
-## Example invocations
-
-```bash
-# Minimal: PNG master, white background, default 22% padding
-bash scripts/ti-branding ./logo.png
-
-# SNAP Gym full kit: SVG master, navy background, notification + splash
-bash scripts/ti-branding ./docs/snap-logo.svg \
-    --bg-color "#0B1326" \
-    --padding 22 \
-    --with-notification \
-    --with-splash-icon
-
-# Tight padding for a detailed wordmark
-bash scripts/ti-branding ./logo.svg --padding 19 --bg-color "#000000"
-
-# Preview only (no files written)
-bash scripts/ti-branding ./logo.svg --bg-color "#FF6600" --dry-run
-
-# Cleanup-only mode — no master image needed, removes legacy artifacts
-bash scripts/ti-branding --cleanup-legacy --dry-run
-bash scripts/ti-branding --cleanup-legacy                # apply
-bash scripts/ti-branding --cleanup-legacy --aggressive   # also ldpi
-
-# One-shot: generate branding AND clean up legacy in a single invocation
-bash scripts/ti-branding ./logo.svg --bg-color "#0B1326" --cleanup-legacy
-```

package/skills/ti-branding/assets/ic_launcher.xml

@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
-  <background android:drawable="@mipmap/ic_launcher_background"/>
-  <foreground android:drawable="@mipmap/ic_launcher_foreground"/>
-  <monochrome android:drawable="@mipmap/ic_launcher_monochrome"/>
-</adaptive-icon>

package/skills/ti-branding/references/android-adaptive-icons.md

@@ -1,85 +0,0 @@
-# Android adaptive icons (API 26+)
-
-## Canvas and safe-zone
-
-Adaptive icons use a fixed 108×108 dp virtual canvas composed of two layers:
-
-- **Foreground**: the logo/glyph with transparency outside the safe-zone
-- **Background**: solid color, gradient, or pattern filling the full canvas
-
-The OS launcher applies a mask (circle, squircle, teardrop, rounded square — up to the OEM) and clips both layers to that shape. Only the central **66×66 dp safe-zone** is guaranteed to remain visible regardless of the mask.
-
-Translation to padding:
-
-```
-safe-zone:    66 / 108 = 61.1% of canvas
-min padding:  (108 - 66) / 2 / 108 = 19.44% per side
-```
-
-Anything beyond 66dp toward the edge is at the launcher's discretion — some masks (circle) hide more, some (squircle) hide less.
-
-## Density sizes
-
-One pixel unit equals `density_scale × 1 dp`:
-
-| Density  | Scale | Canvas size (108 dp) |
-|----------|-------|----------------------|
-| mdpi     | 1.0×  | 108 px               |
-| hdpi     | 1.5×  | 162 px               |
-| xhdpi    | 2.0×  | 216 px               |
-| xxhdpi   | 3.0×  | 324 px               |
-| xxxhdpi  | 4.0×  | 432 px               |
-
-Ship all five. The OS picks the closest match for the user's screen density.
-
-## Monochrome layer (API 31+)
-
-Android 13 introduced themed icons: the user can tell the launcher to re-color all app icons with the system accent color. The OS uses the `monochrome` drawable for this treatment.
-
-Rules for the monochrome drawable:
-
-- All non-transparent pixels become pure white at build time — the OS tint replaces white with the theme color at render time
-- Alpha channel must be preserved (same silhouette as foreground, transparency intact)
-- Do NOT include color information — it will be discarded
-
-The skill generates monochrome by taking the foreground and running ImageMagick's `-channel RGB -fill white -colorize 100 +channel` which replaces RGB with white while leaving the alpha untouched.
-
-## XML bind
-
-One file ties the three layers together. Ships to `mipmap-anydpi-v26/ic_launcher.xml`:
-
-```xml
-<?xml version="1.0" encoding="utf-8"?>
-<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
-  <background android:drawable="@mipmap/ic_launcher_background"/>
-  <foreground android:drawable="@mipmap/ic_launcher_foreground"/>
-  <monochrome android:drawable="@mipmap/ic_launcher_monochrome"/>
-</adaptive-icon>
-```
-
-The `v26` qualifier ensures only API 26+ devices use this file. Older devices fall through to the legacy `mipmap-*/ic_launcher.png` flat drawable.
-
-## Legacy flat icon
-
-For API 21–25 (~3% of active users in 2026) the launcher still uses a flat PNG:
-
-| Density  | Size |
-|----------|------|
-| mdpi     | 48   |
-| hdpi     | 72   |
-| xhdpi    | 96   |
-| xxhdpi   | 144  |
-| xxxhdpi  | 192  |
-
-Fill more of the canvas here — legacy launchers don't apply adaptive masking. The skill reduces the padding by 40% for this composite.
-
-## Verifying
-
-- Android Studio has a Resource Manager that previews adaptive icons with multiple masks. Point it at `app/platform/android/res/` to inspect.
-- On a device/emulator running API 26+, long-press the launcher icon and the animated wiggle reveals whether the adaptive layers are wired correctly.
-- On API 31+, toggle "Themed icons" in the launcher settings to verify the monochrome layer.
-
-## References
-
-- Android Developer: [Adaptive icons](https://developer.android.com/develop/ui/views/launch/icon_design_adaptive)
-- Android Developer: [Themed app icons](https://developer.android.com/about/versions/13/features#themed-app-icons)

package/skills/ti-branding/references/cleanup-legacy.md

@@ -1,112 +0,0 @@
-# `--cleanup-legacy` — removing obsolete branding artifacts
-
-Titanium project templates ship with a lot of legacy branding assets that made sense a decade ago and are dead weight today. The `--cleanup-legacy` flag scans the project and removes them, but only after verifying through `tiapp.xml` that they are genuinely unused.
-
-## Why cleanup matters
-
-Legacy branding assets bloat the project in three ways:
-
-1. **Repository size** — every `Default-XXXh@3x.png` (some 800 KB+ each) stays in git history forever unless actively deleted.
-2. **Build output size** — some legacy assets DO get copied into the APK/IPA even when modern alternatives make them unreachable at runtime. Extra MB mean slower downloads for end users and marginally longer store review times.
-3. **Cognitive load** — new contributors look at `res-long-port-hdpi/`, `Default-Landscape-2688h@3x.png`, `background.9.png`, and reasonably assume they matter. They don't, but nobody is willing to delete what they don't fully understand.
-
-## The three buckets
-
-The cleanup logic categorizes targets by how safe removal is:
-
-### SAFE — universally obsolete
-
-Removed without checking any project configuration. These artifacts are fossils from Android versions predating the current SDK's minimum target.
-
-| Artifact | Why it's dead |
-|---|---|
-| `app/assets/android/images/res-long-*/` | Android's `long` screen qualifier distinguished devices like the Motorola Droid (854×480) from the Nexus One (800×480) in 2009–2011. Since Android 3.0 the system uses dp-based layouts instead. No modern launcher or OS consults these folders. |
-| `app/assets/android/images/res-notlong-*/` | Inverse of `long` — same verdict. |
-
-These buckets are almost always empty in practice (Titanium templates create the folders but rarely populate them), so the cleanup is primarily about removing visual noise from the project tree.
-
-### CONDITIONAL — safe given the project's current configuration
-
-Removed only when `tiapp.xml` confirms the artifact is genuinely unused.
-
-| Artifact | Safety rule | Why |
-|---|---|---|
-| `app/assets/iphone/Default-*.png`, `Default@2x.png` | `<enable-launch-screen-storyboard>true</enable-launch-screen-storyboard>` | With the storyboard active, iOS adapts dynamically to any device resolution via Auto Layout. Apple mandated this in 2020. Without storyboard, these PNGs matter and must stay. |
-| `app/assets/android/images/res-*-land-*/`, `res-land-*/` | `tiapp.xml` declares portrait-only orientations | Landscape variants only load when the app can rotate to landscape. |
-| `app/assets/android/default.png` | `mipmap-anydpi-v26/ic_launcher.xml` exists (adaptive icons present) | The legacy Titanium Android splash PNG is shadowed by the modern SplashScreen API, which derives the splash from the launcher icon. Only deleted when the modern path is in place. |
-| `app/assets/android/appicon.png` | Same adaptive-icons condition | Legacy Android launcher PNG. When adaptive icons exist in `mipmap-*/`, this file is redundant. |
-
-If a safety rule is not satisfied, the artifact is preserved and the user sees a clear reason in the cleanup plan.
-
-### AGGRESSIVE — opt-in via `--aggressive`
-
-Defensible but off by default because there are edge cases.
-
-| Artifact | Reason it's usually safe |
-|---|---|
-| `app/assets/android/images/res-ldpi/`, `res-*-ldpi/` | ldpi (≤120 dpi, pre-2010 low-end devices) is below 1% of active Android devices globally. |
-| `app/platform/android/res/drawable-ldpi/`, `mipmap-ldpi/`, `values-ldpi/` | Same ldpi justification for platform-native resources. |
-
-Users targeting specific low-density markets (some IoT devices, kiosks) should leave `--aggressive` off.
-
-## Safety model
-
-The flag is opinionated about not trashing anybody's work:
-
-- `--dry-run` prints the full plan (paths, sizes, reasons) without deleting anything. Run it first.
-- The plan always shows which `tiapp.xml` flags drove each decision (storyboard on/off, orientation, adaptive-icons presence) so the user can verify the detection is correct.
-- The skill does not delete files outside the project's asset and platform resource directories.
-- It does not touch `tiapp.xml`, source code, `modules/`, `i18n/`, or any application code.
-- Conditional targets still require the safety rule to pass — even with `--cleanup-legacy`, nothing conditional deletes unless `tiapp.xml` justifies it.
-- Aggressive-bucket targets require the explicit `--aggressive` flag on top of `--cleanup-legacy`.
-
-## Real-world savings
-
-Measured on SNAP Gym, a mid-sized Titanium 13.1 Alloy project, immediately after a fresh `alloy new` template:
-
-| Bucket | Items removed | Disk freed |
-|---|---|---|
-| SAFE (`res-long-*` + `res-notlong-*`) | 11 folders | ~0 KB (empty templates) |
-| CONDITIONAL (`iphone/Default-*.png` × 15) | 15 files | ~5.4 MB |
-| CONDITIONAL (`android/default.png`, `appicon.png`) | 2 files | 52 KB |
-| **Total (default flags)** | **28 artifacts** | **~5.5 MB** |
-
-Running `--aggressive` on top would remove an additional ~40 KB of `ldpi` folders — small payoff per project, but compounds when applied across multiple apps.
-
-The 5.4 MB of iOS launch images is the largest single win: those PNGs exist in source but are not shipped in modern IPAs (storyboard-driven iOS builds ignore them). Removing them from source shrinks the repo and clears confusion for new contributors.
-
-## When NOT to run cleanup
-
-- **Classic Titanium apps pre-SDK 10**: rely on the legacy assets. Upgrading the SDK is a prerequisite to safely cleaning up.
-- **Apps with `<enable-launch-screen-storyboard>false</enable-launch-screen-storyboard>`**: the iOS PNGs are still consulted — the skill correctly skips them, but the user should enable the storyboard before running cleanup to get the savings.
-- **Apps that support landscape orientation**: the `res-*-land-*` folders are preserved, which is correct.
-
-## Usage
-
-```bash
-# Preview first — nothing deletes in dry-run mode
-bash scripts/ti-branding --cleanup-legacy --dry-run
-
-# Apply
-bash scripts/ti-branding --cleanup-legacy
-
-# Include ldpi
-bash scripts/ti-branding --cleanup-legacy --aggressive
-
-# Point at a specific project (default: current directory)
-bash scripts/ti-branding --cleanup-legacy --project /path/to/project
-
-# Combine with generation — brand the app and clean up in one pass
-bash scripts/ti-branding ./logo.svg --bg-color "#0B1326" --cleanup-legacy
-```
-
-## Verification checklist
-
-After applying cleanup, rebuild for each platform and visually confirm:
-
-- [ ] iOS app on a modern device (iPhone 11 or newer): splash reaches top and bottom (no letterboxing). The storyboard is doing its job; the deleted PNGs are confirmed unused.
-- [ ] Android app on API 31+ (Android 12 or newer): splash shows the launcher icon centered on the brand color, then transitions to the app normally.
-- [ ] Android app on API 21–30 if the minimum target is that low: app launches without the old `default.png`. Titanium's adaptive-icon fallback kicks in.
-- [ ] `git status` lists only the expected deletions. No source code changes.
-
-If any of those fail, the deletion can be reverted with `git checkout -- .` (before committing) or `git restore` (after).

package/skills/ti-branding/references/ios-appiconset.md

@@ -1,62 +0,0 @@
-# iOS appiconset (Xcode 14+)
-
-## One master, all sizes
-
-Since Xcode 14 (2022), Apple no longer requires the full matrix of 20+ icon sizes. A single 1024×1024 source is sufficient — Xcode generates the rest at build time.
-
-Titanium SDK 13.x embraces this:
-
-- Place `DefaultIcon-ios.png` (1024×1024, no alpha) at the project root
-- On `ti build`, Titanium writes the generated appiconset to `build/iphone/Assets.xcassets/AppIcon.appiconset/`
-- `build/` is regenerated on every build — you never commit the full set to the source tree
-
-If you manually place `app/assets/iphone/appicon-*.png` files, Titanium respects them and only fills in the missing sizes. This skill ignores that path — it only writes the single `DefaultIcon-ios.png` master.
-
-## Why no alpha channel
-
-Apple's review pipeline rejects icons with transparency:
-
-> Apps with app icons that include transparency will be rejected during app review.
-
-The skill flattens alpha by compositing the master over the `--bg-color` before writing `DefaultIcon-ios.png`. Same for `iTunesConnect.png` (App Store submission).
-
-## Relevant file paths
-
-At the project root:
-
-| File | Size | Purpose |
-|------|------|---------|
-| `DefaultIcon-ios.png` | 1024×1024 | Master for appiconset generation |
-| `DefaultIcon.png` | 1024×1024 | Fallback if `DefaultIcon-ios.png` missing (Android uses this too) |
-| `iTunesConnect.png` | 1024×1024 | Uploaded to App Store Connect |
-
-The skill generates the first and third; the second can be a copy of the first if the user wants a shared master.
-
-## Dark and tinted variants (iOS 18+)
-
-iOS 18 added dark-mode and tinted versions of app icons, configured via:
-
-- `DefaultIcon-Dark.png` — dark theme variant
-- `DefaultIcon-Tinted.png` — tinted grayscale variant for iOS's theme engine
-
-These are **out of scope** for this skill's v1. Users who want them can drop the files into the project root manually; Titanium SDK 13.1+ picks them up automatically.
-
-## Launch images — deliberately not generated
-
-The 30+ `Default-*@3x.png` launch image variants from Titanium documentation are legacy. Modern Titanium uses `LaunchScreen.storyboard`, configured in `tiapp.xml`:
-
-```xml
-<ios>
-  <enable-launch-screen-storyboard>true</enable-launch-screen-storyboard>
-  <default-background-color>#0B1326</default-background-color>
-</ios>
-```
-
-The storyboard adapts to any device resolution dynamically. Legacy PNG launch images were needed before iOS 14 — they are now dead weight in any app submitted to the App Store (Apple mandates storyboard-based launch as of 2020).
-
-If a user genuinely needs legacy launch images (maintaining a pre-2020 app), that's a separate tool job — this skill explicitly does not generate them.
-
-## References
-
-- Apple HIG: [App icons](https://developer.apple.com/design/human-interface-guidelines/app-icons)
-- Apple: [Configuring your project to use asset catalogs](https://developer.apple.com/documentation/xcode/configuring-your-project-to-use-asset-catalogs)

package/skills/ti-branding/references/master-input-guidelines.md

@@ -1,84 +0,0 @@
-# Master input guidelines
-
-## Preferred: SVG
-
-SVG is the best source because:
-
-- Vector: re-renders cleanly at any density, no upscaling artifacts
-- Preserves transparency natively
-- Small file size (~5–50 KB for typical logos vs 100+ KB for 1024² PNG)
-- Easy to edit by designers in Illustrator / Affinity / Figma / Inkscape
-
-**SVG requirements**:
-
-- Square viewBox (or content that's square within a rectangular viewBox)
-- Paths only — avoid `<script>`, `<foreignObject>`, web fonts
-- Solid fills or simple gradients — very complex gradients may rasterize inconsistently across densities
-- No external references (embedded images, fonts loaded by URL)
-
-The skill uses `rsvg-convert` to rasterize to 1024×1024 PNG before any further processing.
-
-## Acceptable: PNG ≥ 1024×1024 with transparency
-
-A PNG master works when SVG isn't available:
-
-- Minimum size: 1024×1024 (smaller input produces visibly soft xxxhdpi icons)
-- Square preferred — non-square inputs get center-cropped with a warning
-- Transparent background for best monochrome layer results
-
-## Accepted with warning: PNG with solid background
-
-PNGs that already have a non-transparent background still work, but:
-
-- The monochrome layer will be a solid square silhouette (every pixel is non-transparent, so "everything" becomes white)
-- You cannot change the adaptive background color — it's baked in
-- Recommend re-exporting from the source with transparency if possible
-
-## Padding and the "pegado" problem
-
-If the icon's content already fills the full canvas (logo touching the edges), every generated asset will show the same cramped look. The skill cannot add space that isn't there.
-
-Two ways to fix:
-
-1. **Prepare the master with transparent padding** — export the logo so there's ~15% empty space around it in the source
-2. **Increase the `--padding` flag** — the skill re-centers the logo inside the target canvas. Higher padding pushes the logo inward
-
-Recommended padding values:
-
-| Padding | Logo fill | When to use |
-|---------|-----------|-------------|
-| 19 (spec floor) | 62% | Intricate logos needing maximum detail; risky with aggressive launcher masks |
-| 22 (default) | 56% | Balanced, compliant with Android safe-zone spec + 3% buffer |
-| 25 | 50% | Logos with fine strokes or details near the edge |
-| 28–32 | 44–36% | Bold simple shapes, single-letter monograms |
-
-If the user sees the logo pegado after running the skill once, re-run with a higher `--padding`.
-
-## Alpha channel handling
-
-PNG inputs commonly have one of three alpha configurations:
-
-- **Straight alpha** (most common): `rgba(r, g, b, a)` — R/G/B hold true color, A holds coverage
-- **Premultiplied alpha**: `rgba(r × a, g × a, b × a, a)` — R/G/B are scaled by A
-- **No alpha channel**: opaque only
-
-ImageMagick handles straight alpha transparently. Premultiplied inputs may show dark halos at the edges when composited — if this happens, re-export from the source app with straight alpha.
-
-## Checking the master before running
-
-Quick sanity check:
-
-```bash
-# Dimensions and alpha info
-magick identify -format "%wx%h  alpha=%A\n" /path/to/logo.png
-
-# Visualize the alpha channel (useful for debugging halos)
-magick /path/to/logo.png -alpha extract /tmp/alpha.png && open /tmp/alpha.png
-```
-
-For SVG:
-
-```bash
-# Preview at output size
-rsvg-convert -w 1024 -h 1024 /path/to/logo.svg -o /tmp/preview.png && open /tmp/preview.png
-```

package/skills/ti-branding/references/notification-icons.md

@@ -1,63 +0,0 @@
-# Notification icons
-
-## The white-only rule
-
-Android notification icons, since API 21 (Lollipop), must be **white pixels on a transparent background**. The system applies a runtime tint based on the notification's `color` property — color in the source image is discarded.
-
-If the icon is not white+alpha, it renders as a blank white square on API 21+ (a common bug symptom when developers reuse their launcher icon as the notification icon).
-
-## Generation
-
-The skill's `gen-notification.sh`:
-
-1. Scales the foreground logo down to the notification size
-2. Runs ImageMagick's `-channel RGB -fill white -colorize 100 +channel` to force all RGB channels to 255 while preserving alpha
-3. Pads transparently to match the target canvas size
-
-## Sizes
-
-| Density  | Size |
-|----------|------|
-| mdpi     | 24   |
-| hdpi     | 36   |
-| xhdpi    | 48   |
-| xxhdpi   | 72   |
-| xxxhdpi  | 96   |
-
-## File naming
-
-Titanium has no hard convention, but the de-facto name is `ic_stat_notify.png`. The skill emits this name. To reference it:
-
-**In JavaScript (local notification)**:
-
-```js
-Ti.Android.NotificationManager.notify(1, Ti.Android.createNotification({
-  contentTitle: 'Hello',
-  contentText: 'Hi there',
-  icon: Ti.App.Android.R.drawable.ic_stat_notify  // white+alpha
-}))
-```
-
-**In `platform/android/AndroidManifest.xml` (Firebase default)**:
-
-```xml
-<meta-data
-  android:name="com.google.firebase.messaging.default_notification_icon"
-  android:resource="@drawable/ic_stat_notify"/>
-<meta-data
-  android:name="com.google.firebase.messaging.default_notification_color"
-  android:resource="@color/notification_tint"/>
-```
-
-With a matching `values/colors.xml`:
-
-```xml
-<color name="notification_tint">#FDD900</color>
-```
-
-The `default_notification_color` is the tint the runtime applies to the white pixels.
-
-## References
-
-- Android: [Notifications overview](https://developer.android.com/develop/ui/views/notifications)
-- Firebase: [Setting the default notification icon](https://firebase.google.com/docs/cloud-messaging/android/client#manifest)