@maccesar/titools 5.3.0 → 5.4.0

package/CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to TiTools
 
-TiTools distributes thirteen Titanium SDK skills, a research agent and slash
+TiTools distributes fourteen Titanium SDK skills, a research agent and slash
 commands through an npm CLI and a Claude Code marketplace plugin. Product
 content lives in `skills/`, `agents/` and `commands/`; CLI source lives in
 `bin/` and `lib/`. Both channels use this source tree.

package/README.md

@@ -6,7 +6,7 @@
 
 </div>
 
-TiTools is a Titanium SDK toolkit for AI coding assistants. It ships 13 skills — 8 specialist skills (`ti-reuse-first`, `ti-expert`, `purgetss`, `ti-ui`, `ti-game`, `ti-game-assets`, `ti-synthengine`, `ti-admob-unified`) plus 5 documentation-mirror skills (`ti-api`, `ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos`) — a research agent, and reference files covering reuse and simplification, Titanium architecture, API reference, native how-tos, Alloy MVC, PurgeTSS styling and resource automation, UI/UX patterns, 2D games, and native sound synthesis.
+TiTools is a Titanium SDK toolkit for AI coding assistants. It ships 14 skills — 9 specialist skills (`ti-reuse-first`, `ti-expert`, `purgetss`, `ti-ui`, `ti-game`, `ti-game-assets`, `ti-synthengine`, `ti-admob-unified`, `ti-create-release`) plus 5 documentation-mirror skills (`ti-api`, `ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos`) — a research agent, and reference files covering reuse and simplification, Titanium architecture, API reference, native how-tos, Alloy MVC, PurgeTSS styling and resource automation, UI/UX patterns, 2D games, and native sound synthesis.
 
 The reference files are maintained against official documentation whenever an official source exists, so the assistant can retrieve current framework behavior instead of guessing from generic training data. As of v5.0.0 those sources are the Titanium SDK's own API definitions and the rewritten guides at [titaniumsdk.com](https://titaniumsdk.com). [Where the references come from](#where-the-references-come-from) has the detail.
 
@@ -36,7 +36,7 @@ The fastest way to get started with Claude Code. One command to add the marketpl
 ```
 
 What you get:
-- All 13 TiTools skills (`ti-reuse-first`, `ti-expert`, `purgetss`, `ti-ui`, `ti-game`, `ti-game-assets`, `ti-synthengine`, `ti-admob-unified`, `ti-api`, `ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos`)
+- All 14 TiTools skills (`ti-reuse-first`, `ti-expert`, `purgetss`, `ti-ui`, `ti-game`, `ti-game-assets`, `ti-synthengine`, `ti-admob-unified`, `ti-create-release`, `ti-api`, `ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos`)
 - ti-pro research agent
 - Session hook that auto-detects Titanium projects (`tiapp.xml`, Alloy, PurgeTSS, `ti.game`, `ti.synthengine`)
 - Slash commands: `/ti-check`, `/ti-new-screen`, `/ti-audit`
@@ -70,7 +70,7 @@ claude   # or gemini, or codex
 ```
 
 What gets installed:
-- The 13 TiTools skills to `~/.agents/skills/`
+- The 14 TiTools skills to `~/.agents/skills/`
 - ti-pro agent for Claude Code
 - Platform symlinks for Claude Code (Gemini CLI and Codex CLI auto-discover from `~/.agents/skills/` — no symlinks needed)
 - Knowledge index in your project's `AGENTS.md`/`CLAUDE.md`/`GEMINI.md`
@@ -174,14 +174,15 @@ The knowledge index is based on the latest Titanium SDK documentation. If your p
 | ti-game-assets   | Visual and sound assets             | Image generation/editing, synthesis variants, stereo placement, alpha cleanup, manifests, parallax and complete exports                                                                                                                                                                              |
 | ti-synthengine   | Sound design with `ti.synthengine`  | TiSynth 2.0 reusable Sound presets, independent playback controls, tones/chords, held notes, native repetitions/patterns, ADSR, FM, filters, binaural positioning, shared effects, variation, TypeScript and troubleshooting |
 | ti-admob-unified | Advertising, privacy and mediation  | Official `ti.admob.unified` guides, copy-ready library, banners/fullscreen, UMP/ATT and selected-provider configuration                                                                                                                                                                              |
-| ti-api           | Complete Titanium API reference     | Looking up properties, methods, events                                                                                                                                                                                                                                                               |
+| ti-create-release | Native module releases | Build and verify ZIPs, follow repository release conventions, publish authorized GitHub releases and configure directory discovery |
+| ti-api           | Titanium API lookup     | Looking up properties, methods, events                                                                                                                                                                                                                                                               |
 | ti-guides        | SDK fundamentals                    | tiapp.xml, Hyperloop, distribution, JDK/Xcode compatibility, release notes                                                                                                                                                                                                                           |
 | ti-howtos        | Native feature integration          | Location, push, media, platform APIs                                                                                                                                                                                                                                                                 |
 | alloy-guides     | Alloy MVC framework reference       | Controllers, models, views, widgets                                                                                                                                                                                                                                                                  |
-| alloy-howtos     | Alloy CLI, configuration, debugging | alloy.jmk, config.json, custom XML tags                                                                                                                                                                                                                                                              |
+| alloy-howtos     | Alloy CLI, configuration, debugging | alloy.jmk, config.json, build constants and debugging                                                                                                                                                                                                                                                              |
 
 Notes:
-- The first eight (`ti-reuse-first`, `ti-expert`, `purgetss`, `ti-ui`, `ti-game`, `ti-game-assets`, `ti-synthengine`, `ti-admob-unified`) are specialist workflow skills reflecting TiTools' Titanium conventions and native-module contracts.
+- The first nine (`ti-reuse-first`, `ti-expert`, `purgetss`, `ti-ui`, `ti-game`, `ti-game-assets`, `ti-synthengine`, `ti-admob-unified`, `ti-create-release`) are specialist workflow skills reflecting TiTools' Titanium conventions and native-module contracts.
 - `ti-reuse-first` runs before the others. It asks whether a thing needs to exist and what already does it — a search order that stops at the first rung that holds — and sweeps an existing `app/` for near-identical controllers, single-listener events, wrappers around one call, and layout recomputed in JavaScript. It is deliberately two-sided: it says when adding a module or a Widget is the right answer, so the bias does not simply invert.
 - `ti-game` documents the `ti.game` native module (2D sprite engine using OpenGL ES 2.0 on Android and Metal on iPhone, iPad and Mac Catalyst). Its API reference was verified against the module source and records the reviewed upstream commit and fork documentation snapshot; it applies to Alloy and Classic projects alike and does not depend on PurgeTSS.
 - `ti-synthengine` translates sound requests into checked JavaScript for published Android/iOS `ti.synthengine` 2.0.0. It covers reusable Sound definitions, independent held/repetition/pattern controls, atomic preset edits, temporary overrides, processing units and migration from supported direct methods. Practical references, curated recipes, runnable examples and TypeScript declarations support implementation and troubleshooting.
@@ -193,24 +194,28 @@ Notes:
 
 ## Where the references come from
 
-The Titanium documentation was rewritten during 2026, and v5.0.0 moved TiTools onto the new sources. No skill, command or flag was renamed and the references answer the same questions. What changed is what they are checked against.
+The Titanium documentation was rewritten during 2026, and v5.0.0 moved TiTools onto the new sources. The current guide and UI skills follow what the new official site publishes. Historical recipes that have not been ported are excluded from these skills.
 
 | Source                                                                                | Feeds                                                    | Why it is the one                                                                                                      |
 | ------------------------------------------------------------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
 | [`tidev/titanium-sdk`](https://github.com/tidev/titanium-sdk) → `apidoc/*.yml`        | `ti-api`                                                 | The API definitions the SDK team edits. Every other copy of the API is compiled from these.                            |
-| [`tidev/titaniumsdk.com`](https://github.com/tidev/titaniumsdk.com) → `content/docs/` | `ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos` | The rewritten guides, and what [titaniumsdk.com](https://titaniumsdk.com) serves.                                      |
+| [`tidev/titaniumsdk.com`](https://github.com/tidev/titaniumsdk.com) → `content/docs/` | `ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos`, `ti-ui` | The rewritten guides, and what [titaniumsdk.com](https://titaniumsdk.com) serves.                                      |
 | `tidev/titaniumsdk.com` → `registry/sdk/<version>/`                                   | `ti-api`, as a cross-check                               | The API compiled per published release. It answers which version actually shipped an API, which the YAML alone cannot. |
-| [`tidev/titanium-docs`](https://github.com/tidev/titanium-docs)                       | all five, as an archive                                  | The previous corpus, now frozen. Kept for what the rewrite left out.                                                   |
+| [`tidev/titanium-docs`](https://github.com/tidev/titanium-docs)                       | historical provenance only                              | The previous corpus; excluded from current guide/UI content.                                                   |
 
 ### Why the API comes from the SDK
 
 The website does not write API documentation. It compiles it from `apidoc/*.yml` and commits the result, so it trails the SDK by construction. `ti-api` reads the YAML for what exists and the compiled registry for which release shipped it, and documents the newest GA rather than `main`. An API merged into the SDK today reaches these references when the release carrying it ships, because until then you cannot call it.
 
-### The archive is additive
+### Current guides and API verification
 
-`tidev/titanium-docs` is frozen and being archived upstream. TiDev's own migration audit classifies its 336 guide pages as 121 rewritten, 121 merged, 2 kept and 92 archived. Of those 92, 91 are release notes and the last is the discontinued Atom package, so no guide topic was dropped. The difference is density: 1390 KB of legacy prose became 219 KB.
+Use [llms.txt](https://titaniumsdk.com/llms.txt) to discover official routes and append `.md` to a guide URL to read its Markdown representation. The new documentation source is `tidev/titaniumsdk.com`.
 
-TiTools keeps the full corpus. The archive never overrides a live source on a question of fact, and nothing is deleted from a reference merely because the rewritten site no longer covers it. These skills still answer questions the official guides have not been rewritten to cover yet, such as the conditional `if=` attribute in Alloy XML and TSS, custom XML tags via `app/lib/`, and `alloy compile`.
+`ti-guides`, `ti-howtos`, `alloy-guides`, `alloy-howtos` and `ti-ui` include current official guide topics. They do not supplement missing sections with the old `titanium-docs` corpus or unpublished community recipes. Topics can return when the official site publishes them.
+
+A guide's scope does not guarantee every example is correct. References identify verified conflicts with released API/compiler contracts, including Alloy configuration precedence and hooks, notification registration and safe-area defaults. The core API baseline is SDK 13.4.1.GA, with explicit version links; unreleased SDK 14 features remain excluded. Native modules have independent versions and authorities.
+
+PurgeTSS and the native-module skills retain their own official sources and declared curated resources. Their source policies are independent of the website migration.
 
 ---
 
@@ -220,14 +225,14 @@ In addition to skills, this repository includes sub-agents for Claude Code. Sub-
 
 ### ti-pro
 
-Deep-dive research specialist that can combine the complete 13-skill TiTools catalog.
+Deep-dive research specialist that can combine the complete 14-skill TiTools catalog.
 
 | Aspect           | Details                                     |
 | ---------------- | ------------------------------------------- |
 | Location         | `~/.claude/agents/ti-pro.md`                |
 | Model            | Sonnet (comprehensive analysis)             |
 | Tools            | Read, Grep, Glob, Bash                      |
-| Preloaded Skills | All 13 skills registered in `lib/config.js` |
+| Preloaded Skills | All 14 skills registered in `lib/config.js` |
 
 When to use the agent vs skills:
 
@@ -269,7 +274,7 @@ TiTools provides slash commands for common tasks. Both channels ship them: the p
 These commands automatically invoke the relevant skills:
 - `/ti-check` reads `tiapp.xml`, validates declared native modules, and reports project health
 - `/ti-new-screen` uses `ti-expert` + `purgetss` to create properly structured files
-- `/ti-audit` routes all 13 skills: the reuse sweep first, core Titanium checks always, Alloy/PurgeTSS checks when detected, integration how-tos when used, `ti-game-assets` checks for game asset workflows, and `ti-game` / `ti-synthengine` / `ti-admob-unified` checks when those modules are declared
+- `/ti-audit` routes all 14 skills: the reuse sweep first, core Titanium checks always, Alloy/PurgeTSS checks when detected, integration how-tos when used, `ti-game-assets` checks for game asset workflows, and `ti-game` / `ti-synthengine` / `ti-admob-unified` checks when those modules are declared
 
 ---
 
@@ -331,11 +336,12 @@ Why this matters:
 | Whether to build it at all | `ti-reuse-first`, first                                                     |
 | Architecture and UI        | `ti-expert`, `ti-ui`, `purgetss` when configured                            |
 | Game assets                | `ti-game-assets` for visual and sound creation, preparation and integration |
+| Native module releases     | `ti-create-release` when preparing or publishing a module release |
 | Native modules             | `ti-game`, `ti-synthengine`, `ti-admob-unified` when declared or requested  |
 | Exact SDK/API guidance     | `ti-api`, `ti-guides`, `ti-howtos`                                          |
 | Alloy MVC and tooling      | `alloy-guides`, `alloy-howtos` for Alloy projects                           |
 
-All thirteen ship with TiTools; no second skill package is required.
+All fourteen ship with TiTools; no second skill package is required.
 
 ---
 
@@ -679,7 +685,7 @@ Behavior depends on where you run it:
 | With `--local` flag        | Installs skills locally to `./.agents/skills/` in the current project |
 
 What it does:
-- Installs the 13 TiTools skills (global or local depending on context)
+- Installs the 14 TiTools skills (global or local depending on context)
 - Installs ti-pro agent for Claude Code
 - Installs the `/ti-check`, `/ti-new-screen` and `/ti-audit` slash commands into `~/.claude/commands/`
 - Detects installed AI platforms and lets you choose which to link (only Claude Code needs platform symlinks; Gemini CLI and Codex CLI auto-discover from `~/.agents/skills/`)
@@ -840,45 +846,9 @@ titools --version # CLI version only
 
 ---
 
-## Community-Discovered Patterns
-
-The TiTools skills include **Community-Discovered Patterns** — verified iOS behaviors not present in the official Titanium documentation. These sections are protected from removal during skill audits.
-
-### Large Title + ScrollView (iOS)
-
-When using Large Titles with a ScrollView inside NavigationWindow or TabGroup, three Window properties must be set together. Without all three, the ScrollView content overlaps behind the navigation bar — or the large title renders with a visible delay.
-
-| Class                            | Property                     | Purpose                                               |
-| -------------------------------- | ---------------------------- | ----------------------------------------------------- |
-| `auto-adjust-scroll-view-insets` | `autoAdjustScrollViewInsets` | Adjusts ScrollView insets to prevent content overlap  |
-| `extend-edges-all`               | `extendEdges`                | Content extends behind bars (blur/translucent effect) |
-| `large-title-enabled`            | `largeTitleEnabled`          | Large title that collapses on scroll                  |
-
-**Recommended:** set the base properties as global Window defaults in `config.cjs`:
-
-```js
-module.exports = {
-  theme: {
-    Window: {
-      ios: {
-        apply: 'auto-adjust-scroll-view-insets extend-edges-all status-bar-style-light-content'
-      }
-    }
-  }
-};
-```
-
-Then only add `large-title-enabled` per-window as needed:
-
-```xml
-<Window title="Home" class="large-title-enabled">
-  <ScrollView class="vertical w-screen" contentHeight="Ti.UI.SIZE">
-    <!-- Content starts below the nav bar automatically -->
-  </ScrollView>
-</Window>
-```
+## Curated resources
 
-This pattern is documented across four bundled TiTools skills: `ti-ui`, `ti-expert`, `purgetss`, and `ti-api`, which covers the underlying Window properties.
+Specialist skills such as PurgeTSS, native games and synthesis retain their declared practical resources and their own source authorities. The website-based guide/UI skills follow current official documentation only; they do not carry archived-only or community-only sections.
 
 ---
 
@@ -889,16 +859,17 @@ This pattern is documented across four bundled TiTools skills: `ti-ui`, `ti-expe
 | ti-reuse-first   | Reuse Before You Write        | 5 files (the ladder, Alloy reuse, indirection, PurgeTSS reuse, diagnostics)                                                                                                                          |
 | ti-expert        | Architecture + Implementation | 27 files (patterns, feedback surfaces, file type association, sharing, testing, security, etc.)                                                                                                      |
 | purgetss         | Setup + Critical Rules        | 39 files (Classic compatibility, grid, animations, icons, class-index, SVG pipeline, etc.)                                                                                                           |
-| ti-ui            | UI Rules + Platform Diffs     | 14 files (layouts, lists, gestures, etc.)                                                                                                                                                            |
+| ti-ui            | UI Rules + Platform Diffs     | 5 current official guides (native UI, layouts, lists, icons and platform conventions)                                                                                                                                                            |
 | ti-game          | Native 2D Game Workflow       | 12 files (API, input, source notes, setup, physics, patterns, recipes, tile maps, debugging, roadmap)                                                                                                |
 | ti-game-assets   | Visual and Sound Assets       | 10 guides and a manifest example; alpha and contract validation scripts                                                                                                                              |
 | ti-admob-unified | Unified Advertising           | 20 Markdown references including production, rewarded interstitial, mediation parity, integration library guidance, provenance and game monetization; source/hash checks and official example assets |
 | ti-synthengine   | Native Sound Synthesis        | TiSynth 2.0 Sound interface and migration, native parameter reference, practical sound design/recipes, runnable example and TypeScript declarations |
+| ti-create-release | Native Module Releases | Release workflow plus current module-directory discovery reference |
 | ti-api           | Titanium API                  | 20 references for core/platform APIs and native modules                                                                                                                                              |
-| ti-guides        | SDK Fundamentals              | 16 references for setup, configuration, CLI and distribution                                                                                                                                         |
-| ti-howtos        | Native Integrations           | 18 references for platform features and integration workflows                                                                                                                                        |
-| alloy-guides     | Alloy MVC                     | 11 references for controllers, views, models, styling and widgets                                                                                                                                    |
-| alloy-howtos     | Alloy CLI and Debugging       | 6 references for commands, configuration and practical workflows                                                                                                                                     |
+| ti-guides        | SDK Fundamentals              | 12 current references for setup, configuration, CLI and distribution                                                                                                                                         |
+| ti-howtos        | Native Integrations           | 9 current references for platform features and integration workflows                                                                                                                                        |
+| alloy-guides     | Alloy MVC                     | 10 references for current Alloy guides and independently sourced PurgeTSS integration                                                                                                                                    |
+| alloy-howtos     | Alloy CLI and Debugging       | 5 current references for app workflows, configuration and debugging                                                                                                                                     |
 
 ---
 

package/agents/ti-pro.md

@@ -10,6 +10,7 @@ skills:
   - ti-game-assets
   - ti-synthengine
   - ti-admob-unified
+  - ti-create-release
   - ti-api
   - ti-guides
   - ti-howtos
@@ -30,11 +31,12 @@ When invoked, research complex topics by consulting the applicable skills from t
 - `ti-reuse-first` - Whether the thing should exist at all, and what already does it; duplication and dead-structure sweeps
 - `ti-expert` - Architecture, patterns, conventions
 - `purgetss` - Utility-first styling classes (optional add-on; use when the project already has it or the user asks about it)
-- `ti-ui` - UI/UX patterns, layouts, gestures
+- `ti-ui` - Current official native UI, layout, list, icon and platform guides
 - `ti-game-assets` - Visual and sound asset contracts, raster generation, alpha/export validation, synthesis variants and stereo coordination when assets are involved
 - `ti-game` - Native `ti.game` architecture and API when the module is declared
 - `ti-synthengine` - TiSynth 2.0 reusable Sound definitions, independent playback controls, direct-method migration, timing/processing units, synthesis and platform caveats when the module is declared or requested
 - `ti-admob-unified` - Official unified advertising/privacy/mediation module contract and provider setup when declared or requested
+- `ti-create-release` - Native-module release-readiness and discovery research; read-only here, with publication reserved for an explicit user release request
 - `ti-api`, `ti-guides`, `ti-howtos` - Exact Titanium APIs, SDK fundamentals and native integrations
 - `alloy-guides`, `alloy-howtos` - Alloy MVC, CLI, configuration and compiler workflows when the project is Alloy
 

package/commands/ti-audit.md

@@ -11,13 +11,13 @@ Core Titanium audit:
 2. Invoke `ti-expert` — check architecture, navigation ownership, event/timer cleanup, memory leaks, bridge pressure, testing boundaries, adaptive layouts and code conventions.
 3. Invoke `ti-guides` — check `tiapp.xml`, CommonJS/Hyperloop usage, Titanium CLI/build assumptions, memory and bridge guidance, distribution settings, and toolchain compatibility.
 4. Invoke `ti-api` — verify every audited `Ti.*` API, event, property, constant and third-party module call against its exact signature. Do not report a suspected API defect from memory.
-5. Invoke `ti-ui` when the project creates Titanium UI — check layouts, list performance, event bubbling, gestures, animations, accessibility, orientation and platform-specific UI.
-6. Invoke `ti-howtos` when the project implements a native integration such as location, maps, push, camera, media, SQLite, HTTPClient, WebView, intents, Keychain/iCloud, Hyperloop or CI/CD — audit the complete integration and platform setup, not only the JavaScript call site.
+5. Invoke `ti-ui` when the project creates Titanium UI — check current layout, list, icon/launch-screen and platform-convention guidance. Use `ti-api` for event, gesture, animation, accessibility and orientation contracts.
+6. Invoke `ti-howtos` when the project implements a native integration such as location, maps, push, camera, media, SQLite, HTTPClient, native modules, Hyperloop or CLI plugins — audit the complete integration and platform setup, not only the JavaScript call site.
 
 Project-type audit:
 
-7. If the project is Alloy (`app/views/`, `app/controllers/`, `app/styles/`), invoke `alloy-guides` — check controllers, XML/TSS, models, collections, widgets, sync adapters and cleanup patterns.
-8. If the Alloy project uses `alloy.jmk`, `config.json`, `widget.json`, conditional views, custom XML tags or Alloy CLI workflows, invoke `alloy-howtos` — check configuration precedence, build hooks, generated structures and compilation/debugging conventions.
+7. If the project is Alloy (`app/views/`, `app/controllers/`, `app/styles/`), invoke `alloy-guides` — check controllers, XML/TSS, models, collections, widgets, persistence and cleanup patterns.
+8. If the Alloy project uses `alloy.jmk`, `config.json`, `widget.json`, conditional views or current Alloy CLI workflows, invoke `alloy-howtos` — check configuration precedence, build hooks, generated structures and compilation/debugging conventions.
 9. If the project uses PurgeTSS (`purgetss/`, `purgetss/config.cjs`, a PurgeTSS-generated `app.tss`, or `purgetss.{ui,colors,fonts}.js`), invoke `purgetss` and detect Alloy vs. Classic before applying findings. In Alloy, audit unsupported utility classes, padding on Views, unnecessary manual TSS, dynamic components, grids, icons and animations. In Classic, audit only the supported standalone asset/CommonJS commands and their `Resources/` outputs; do not require or recommend `alloy.jmk`, generated TSS, utility classes, or `$.UI.create()`.
 
 Native-module audit:
@@ -29,6 +29,8 @@ Native-module audit:
 
 13. If the project declares `ti.admob.unified`/mediation complements or uses this module, invoke `ti-admob-unified` — verify public release/platform requirements, consent/request eligibility/initialization, ATT status versus permission, test IDs, independent banner lifecycle and deliberate fullscreen ownership. Check rewarded interstitial's reward introduction, visible Skip, reward-event credit and pending-context cancellation. Use the production guide for app IDs, app-ads.txt, privacy entry points and account readiness. Separate linking, Google test ads, selected-provider delivery and physical acceptance; preserve game frequency and pause/audio/input policy.
 
+For a native-module release-readiness review, consult `ti-create-release` in read-only mode to check source/artifact provenance and discovery metadata. An audit does not authorize publishing a release or changing GitHub metadata.
+
 If a conditional skill does not apply, record it as `not applicable` with the detected reason instead of inventing findings from it.
 
 Report findings grouped by severity: critical, warning, info.

package/docs/examples.md

@@ -98,3 +98,12 @@ existing components, then check scene input, native audio ownership and cleanup
 using the appropriate references."
 
 See [how the knowledge index works](knowledge-index.md) for reference discovery.
+
+
+## Native module releases — ti-create-release
+
+- "Prepare an iOS-only release of this Titanium module using its existing tag and build conventions."
+- "Publish the agreed Android/iOS ZIPs from the verified source commit and check the module's discovery topics and description."
+- "Review this fork's release readiness without publishing or changing GitHub metadata."
+
+Use [the release skill](../skills/ti-create-release/SKILL.md) for artifact provenance, authorized publication and directory discovery. App-store releases use their own workflows.

package/docs/knowledge-index.md

@@ -25,7 +25,7 @@ and generating an index in a consuming app are separate operations.
 
 ## Choose the relevant skills
 
-The catalog contains thirteen public skills:
+The catalog contains fourteen public skills:
 
 | Task | Skill |
 | --- | --- |
@@ -37,6 +37,7 @@ The catalog contains thirteen public skills:
 | Visual and sound asset production | `ti-game-assets` |
 | Native synthesis | `ti-synthengine` |
 | Unified advertising | `ti-admob-unified` |
+| Native module releases and discovery | `ti-create-release` |
 | Exact Titanium APIs | `ti-api` |
 | SDK fundamentals | `ti-guides` |
 | Native integrations | `ti-howtos` |

package/lib/config.js

@@ -38,6 +38,7 @@ export const SKILLS = [
   'ti-game-assets',
   'ti-synthengine',
   'ti-admob-unified',
+  'ti-create-release',
   'ti-api',
   'ti-guides',
   'ti-howtos',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maccesar/titools",
-  "version": "5.3.0",
+  "version": "5.4.0",
   "description": "Titanium SDK skills and agents for AI coding assistants, including native game and sound synthesis modules",
   "main": "lib/index.js",
   "type": "module",

package/skills/alloy-guides/SKILL.md

@@ -1,188 +1,27 @@
 ---
 name: alloy-guides
-description: 'Use when working with Alloy MVC projects: writing or reviewing Alloy controllers (`app/controllers/`), XML views (`app/views/`), TSS styles (`app/styles/`), Backbone models and collections (`app/models/`), sync adapters, migrations, widgets, or the Alloy compilation flow. Triggers include the `app/views/` + `app/controllers/` + `app/styles/` folder structure, or `app/models/` for data work. Alloy XML is not HTML; TSS is not CSS; controllers follow Alloy-specific patterns, not web MVC.'
+description: Use when writing or reviewing Titanium Alloy XML views, TSS styles, controllers, models and collections, persistent list binding, widgets or build-time themes. Applies to app/views, app/styles, app/controllers and app/models. Uses the current official Titanium guides; Alloy is a compiler over the Titanium API, not web MVC.
 ---
 
-# alloy-guides
+# Alloy guides
 
-## Overview
+Use this skill for Alloy screen structure, styling, controller lifecycle, persistent data and reusable widgets. Load the relevant reference before writing code.
 
-Reference for the Alloy MVC framework on top of Titanium SDK. Covers core concepts, controllers, models / collections / data binding, XML markup, TSS styling (static and dynamic), widgets, and the compile pipeline.
+| Task | Reference |
+| --- | --- |
+| MVC, project directories and generated output | [Concepts](references/CONCEPTS.md) |
+| Arguments, opening windows, shared modules and cleanup | [Controllers](references/CONTROLLERS.md) |
+| Model definition, ListView binding, filters and transforms | [Models](references/MODELS.md) |
+| Persistence choices and schema migrations | [Persistence](references/MODELS_ADVANCED.md) |
+| XML, IDs, namespaces, conditional elements and composition | [Views](references/VIEWS_XML.md) |
+| TSS selectors, precedence, queries and build-time themes | [Styles](references/VIEWS_STYLES.md) |
+| Runtime class changes and their required class tracking | [Dynamic styles](references/VIEWS_DYNAMIC.md) |
+| Creating, declaring, using and isolating widgets | [Widgets](references/WIDGETS.md) |
+| Creating, converting and running an Alloy app | [App workflow](references/CLI_TASKS.md) |
+| PurgeTSS integration, with its independent source | [PurgeTSS](references/PURGETSS.md) |
 
-## When to use
+Keep XML, TSS and JavaScript in their corresponding `app` directories. `Resources/` and `build/` are generated; do not edit or commit them. A controller creates its views but does not automatically open a Window. Read `$.args` at the top, export deliberate operations and clean up listeners/subscriptions separately from `$.destroy()`.
 
-Use this skill when:
+For configuration, compiler constants, hooks and debugging use `alloy-howtos`. For API signatures and platform availability use `ti-api`. Use `ti-guides` for toolchain, native modules and distribution, `ti-howtos` for service setup, and `ti-ui` for current Titanium layout and list behavior.
 
-- The project contains `app/views/`, `app/controllers/`, `app/styles/`, or `app/models/`
-- Writing or reviewing Alloy XML markup (`<Alloy>`, `<Window>`, `<View>`, ...)
-- Writing or reviewing TSS styles (static and conditional/dynamic)
-- Defining Backbone models/collections, data binding, or sync adapters
-- Creating, consuming, or packaging widgets
-- Understanding the Alloy compilation pipeline (`alloy.jmk`, code generation)
-- Diagnosing TSS, XML, or model schema issues
-
-Do NOT use for:
-
-- Alloy CLI usage and configuration files (use `alloy-howtos`)
-- Titanium SDK fundamentals, `tiapp.xml`, distribution (use `ti-guides`)
-- Looking up Titanium API surfaces (use `ti-api`)
-- Native module dependency updates (use `ti-module-update`)
-
-## Quick reference
-
-| Topic | Reference |
-|---|---|
-| Core concepts, MVC, Backbone.js, conventions | [CONCEPTS.md](references/CONCEPTS.md) |
-| Controllers, events, conditional code, arguments | [CONTROLLERS.md](references/CONTROLLERS.md) |
-| Models, collections, data binding | [MODELS.md](references/MODELS.md) |
-| Sync adapters, migrations, plain Backbone, Backbone version migration | [MODELS_ADVANCED.md](references/MODELS_ADVANCED.md) |
-| XML markup, elements, attributes, events | [VIEWS_XML.md](references/VIEWS_XML.md) |
-| TSS styling, themes, platform-specific styles | [VIEWS_STYLES.md](references/VIEWS_STYLES.md) |
-| Dynamic styles, autostyle, runtime styling | [VIEWS_DYNAMIC.md](references/VIEWS_DYNAMIC.md) |
-| Controllers-less views, patterns | [VIEWS_WITHOUT_CONTROLLERS.md](references/VIEWS_WITHOUT_CONTROLLERS.md) |
-| Creating and using widgets | [WIDGETS.md](references/WIDGETS.md) |
-| CLI commands, code generation | [CLI_TASKS.md](references/CLI_TASKS.md) |
-| PurgeTSS integration (optional addon) | [PURGETSS.md](references/PURGETSS.md) |
-
-## Project structure
-
-Standard Alloy project layout:
-
-```
-app/
-├── alloy.js              # Initializer file
-├── alloy.jmk             # Build configuration
-├── config.json           # Project configuration
-├── assets/               # Images, fonts, files (→ Resources/)
-├── controllers/          # Controller files (.js)
-├── i18n/                 # Localization strings (→ i18n/)
-├── lib/                  # CommonJS modules
-├── migrations/           # DB migrations (<DATETIME>_<name>.js)
-├── models/               # Model definitions (.js)
-├── platform/             # Platform-specific resources (→ platform/)
-├── specs/                # Test-only files (dev/test only)
-├── styles/               # TSS files (.tss)
-├── themes/               # Theme folders
-├── views/                # XML markup files (.xml)
-└── widgets/              # Widget components
-```
-
-## MVC quick start
-
-**Controller** (`app/controllers/index.js`)
-```javascript
-function doClick (e) {
-    alert($.label.text);
-}
-$.index.open();
-```
-
-**View** (`app/views/index.xml`)
-```xml
-<Alloy>
-    <Window class="container">
-        <Label id="label" onClick="doClick">Hello, World</Label>
-    </Window>
-</Alloy>
-```
-
-**Style** (`app/styles/index.tss`)
-```javascript
-'.container': { backgroundColor: 'white' }
-'Label': { color: '#000' }
-```
-
-## Key concepts
-
-- **Models / Collections** — Backbone.js objects with sync adapters (`sql`, `properties`)
-- **Views** — XML markup with TSS styling
-- **Controllers** — JavaScript logic with `$` reference to view components
-- **Data Binding** — Bind collections to UI components automatically
-- **Widgets** — Reusable components with their own MVC structure
-- **Conventions** — File naming and placement drive code generation
-
-## Critical rules
-
-### Platform-specific properties in TSS
-
-> **Warning: Platform-specific properties require modifiers**
->
-> Using `Ti.UI.iOS.*` or `Ti.UI.Android.*` properties in TSS without platform modifiers causes cross-platform compilation failures.
->
-> ```tss
-> // WRONG — adds Ti.UI.iOS to Android project
-> '#mainWindow': {
->     statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT  // FAILS on Android
-> }
->
-> // CORRECT — only adds to iOS
-> '#mainWindow[platform=ios]': {
->     statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT
-> }
->
-> // CORRECT — only adds to Android
-> '#mainWindow[platform=android]': {
->     actionBar: { displayHomeAsUp: true }
-> }
-> ```
->
-> Properties that always require platform modifiers:
->
-> - **iOS:** `statusBarStyle`, `modalStyle`, `modalTransitionStyle`, anything under `Ti.UI.iOS.*`
-> - **Android:** `actionBar` config, anything under `Ti.UI.Android.*`
->
-> Available modifiers: `[platform=ios]`, `[platform=android]`, `[formFactor=handheld]`, `[formFactor=tablet]`, `[if=Alloy.Globals.<expression>]`
->
-> See [VIEWS_DYNAMIC.md](references/VIEWS_DYNAMIC.md) for the full set of conditional / platform modifier patterns.
-
-## Common patterns
-
-### Creating a model
-
-```bash
-alloy generate model book sql title:string author:string
-```
-
-### Data binding
-
-```xml
-<Collection src="book" />
-<TableView dataCollection="book">
-    <TableViewRow title="{title}" />
-</TableView>
-```
-
-### Platform-specific code
-
-```javascript
-if (OS_IOS) {
-    // iOS-only code
-}
-if (OS_ANDROID) {
-    // Android-only code
-}
-```
-
-### Widget usage
-
-```xml
-<Widget src="mywidget" id="foo" />
-```
-
-## Compilation process
-
-1. **Cleanup** — `Resources` folder cleaned
-2. **Build config** — `alloy.jmk` loaded (`pre:load` task)
-3. **Framework files** — Backbone.js, Underscore.js, sync adapters copied
-4. **MVC generation** — Models, widgets, views, controllers compiled to JS
-5. **Main app** — `app.js` generated from template
-6. **Optimization** — UglifyJS optimization, platform-specific code removal
-
-## Related skills
-
-| Task | Use this skill |
-|---|---|
-| Alloy CLI, `alloy.jmk`, `config.json`, debugging compilation | `alloy-howtos` |
-| Titanium SDK config, Hyperloop, app distribution | `ti-guides` |
-| Titanium API lookup (Ti.UI, Ti.Network, modules) | `ti-api` |
-| Native module dependency updates | `ti-module-update` |
+The current guide pages are at [titaniumsdk.com/docs/alloy.md](https://titaniumsdk.com/docs/alloy.md). References include released-compiler caveats where a published recipe conflicts with released behavior. PurgeTSS keeps its own source and is outside the official Alloy guide refresh.