@maccesar/titools 2.2.12 → 2.3.0

package/skills/ti-expert/references/testing-e2e-ci.md

@@ -127,21 +127,30 @@ describe('Login Flow', () => {
 
 ## Adding accessibility IDs for testing
 
+Appium uses accessibility identifiers to locate elements. The correct properties are:
+- **iOS**: `accessibilityIdentifier` — maps to `$('~id')` in WebdriverIO
+- **Android**: `contentDescription` — also maps to `$('~id')` in WebdriverIO
+
+`testId` is NOT an official Titanium view property. Use `accessibilityIdentifier` instead.
+
 ```xml
 <!-- views/auth/login.xml -->
-<Window testId="loginScreen">
-  <TextField id="emailField" testId="emailField" />
-  <TextField id="passwordField" testId="passwordField" />
-  <Button id="loginBtn" testId="loginButton" />
-  <Label id="errorLabel" testId="errorLabel" />
+<Window id="loginWindow" accessibilityIdentifier="loginScreen">
+  <TextField id="emailField" accessibilityIdentifier="emailField" />
+  <TextField id="passwordField" accessibilityIdentifier="passwordField" />
+  <Button id="loginBtn" accessibilityIdentifier="loginButton" />
+  <Label id="errorLabel" accessibilityIdentifier="errorLabel" />
 </Window>
 ```
 
 ```javascript
-// In controller or alloy.js - map testId to accessibilityLabel
-if (Alloy.CFG.debug) {
-  // Auto-set accessibilityLabel from testId during development
-  Ti.UI.defaultUnit = 'dp'
+// For Android, also set contentDescription to match the same value
+// since accessibilityIdentifier is iOS-specific.
+// In controller:
+if (OS_ANDROID) {
+  $.emailField.contentDescription = 'emailField'
+  $.passwordField.contentDescription = 'passwordField'
+  $.loginBtn.contentDescription = 'loginButton'
 }
 ```
 
@@ -412,21 +421,21 @@ end
 
 Configure in GitHub repository settings:
 
-| Rule | Setting |
+| Rule                              | Setting                                    |
 | --------------------------------- | ------------------------------------------ |
-| Require pull request reviews | 1 approval required |
-| Require status checks | lint, unit-tests, build-ios, build-android |
-| Require branches to be up to date | Yes |
-| Include administrators | Yes |
+| Require pull request reviews      | 1 approval required                        |
+| Require status checks             | lint, unit-tests, build-ios, build-android |
+| Require branches to be up to date | Yes                                        |
+| Include administrators            | Yes                                        |
 
 ## Testing best practices summary
 
-| Area | Practice |
+| Area                  | Practice                                   |
 | --------------------- | ------------------------------------------ |
-| **Unit Tests** | Test business logic in services/helpers |
+| **Unit Tests**        | Test business logic in services/helpers    |
 | **Integration Tests** | Test controller flows with mocked services |
-| **E2E Tests** | Test critical user journeys |
-| **Coverage** | Aim for 80%+ on services, 60%+ overall |
-| **CI Pipeline** | Run lint -> unit tests -> build -> E2E |
-| **Artifacts** | Save screenshots on failure |
-| **Notifications** | Slack/email on build failures |
+| **E2E Tests**         | Test critical user journeys                |
+| **Coverage**          | Aim for 80%+ on services, 60%+ overall     |
+| **CI Pipeline**       | Run lint -> unit tests -> build -> E2E     |
+| **Artifacts**         | Save screenshots on failure                |
+| **Notifications**     | Slack/email on build failures              |

package/skills/ti-expert/references/theming.md

@@ -41,9 +41,8 @@ Set the theme in `config.json`:
 }
 ```
 
-:::warning Theme is compile-time only
-Alloy themes are applied at **build time**. You cannot switch themes at runtime using this system alone. For runtime switching, use the Dynamic Theming approach below.
-:::
+> **⚠️ Theme is compile-time only**
+> Alloy themes are applied at **build time**. You cannot switch themes at runtime using this system alone. For runtime switching, use the Dynamic Theming approach below.
 
 ### Theme cascade
 
@@ -178,9 +177,8 @@ exports.ThemeService = {
 
 ### Step 4: respond to theme changes in controllers
 
-:::warning Theme change requires UI rebuild
-Since TSS is applied at controller creation time, changing `Alloy.Globals.theme` does NOT retroactively update already-rendered views. You must manually update visible elements or restart the root controller.
-:::
+> **⚠️ Theme change requires UI rebuild**
+> Since TSS is applied at controller creation time, changing `Alloy.Globals.theme` does NOT retroactively update already-rendered views. You must manually update visible elements or restart the root controller.
 
 **Approach A: Rebuild root controller (simplest)**
 
@@ -245,20 +243,15 @@ exports.ThemeService = {
 
   // Initialize system theme listener
   initSystemListener() {
-    // Detect current system theme
+    // Detect current system theme at startup
     this.followSystem()
 
-    // Listen for system theme changes
-    Ti.App.addEventListener('significantTimeChange', () => {
+    // Re-check on resume (user may have changed system Dark Mode while app was backgrounded)
+    // Note: Titanium does not fire a dedicated dark-mode-change event.
+    // `Ti.UI.semanticColorType` is the correct way to check the current setting.
+    Ti.App.addEventListener('resumed', () => {
       this.followSystem()
     })
-
-    // iOS: userInterfaceStyle change
-    if (OS_IOS) {
-      Ti.App.addEventListener('traitCollectionChange', () => {
-        this.followSystem()
-      })
-    }
   }
 }
 ```
@@ -322,10 +315,9 @@ $.container.backgroundColor = 'backgroundColor';
 - Alpha can be set from 0.0-100.0 (integer or float)
 - Light values can use hex with alpha via ARGB/AARRGGBB format
 
-:::tip When to use Semantic Colors vs Alloy.Globals
-- **Semantic Colors**: Built-in Dark Mode support, automatic switching, simpler setup. Works cross-platform.
-- **Alloy.Globals palette**: More control over when/how themes switch, easier to add custom themes beyond light/dark, runtime theme changes with UI rebuild.
-:::
+> **💡 When to use Semantic Colors vs Alloy.Globals**
+> - **Semantic Colors**: Built-in Dark Mode support, automatic switching, simpler setup. Works cross-platform.
+> - **Alloy.Globals palette**: More control over when/how themes switch, easier to add custom themes beyond light/dark, runtime theme changes with UI rebuild.
 
 ---
 

package/skills/ti-guides/SKILL.md

@@ -11,20 +11,19 @@ Use this skill to keep Titanium projects aligned with TiDev standards for stabil
 
 ## Project detection
 
-:::info Auto-detects Titanium projects
-This skill auto-detects Titanium projects. No manual command is needed.
-
-Titanium project indicator:
-- `tiapp.xml` file (definitive indicator)
-
-Applies to both:
-- Alloy projects (`app/` folder)
-- Classic projects (`Resources/` folder)
-
-Behavior:
-- If a Titanium project is detected, provide official Titanium SDK guidance, memory management best practices, and app distribution help.
-- If not detected, say this skill is only for Titanium projects.
-:::
+> **️ℹ️ Auto-detects Titanium projects**
+> This skill auto-detects Titanium projects. No manual command is needed.
+>
+> Titanium project indicator:
+> - `tiapp.xml` file (definitive indicator)
+>
+> Applies to both:
+> - Alloy projects (`app/` folder)
+> - Classic projects (`Resources/` folder)
+>
+> Behavior:
+> - If a Titanium project is detected, provide official Titanium SDK guidance, memory management best practices, and app distribution help.
+> - If not detected, say this skill is only for Titanium projects.
 
 ## Core workflow
 
@@ -52,9 +51,6 @@ Behavior:
 - Hyperloop Native Access (references/hyperloop-native-access.md): Objective-C/Swift/Java syntax, casting, debugging, XIB/Storyboards.
 - Style & Conventions (references/style-and-conventions.md): naming standards and formatting rules.
 - Reserved Words (references/reserved-words.md): ECMAScript, iOS, and Alloy reserved keywords to avoid.
-- Alloy CLI Reference (references/alloy-cli-advanced.md): extract-i18n, code generation, and build hooks.
-- Alloy Data Mastery (references/alloy-data-mastery.md): sync adapters, data binding, and Backbone collections.
-- Alloy Widgets & Themes (references/alloy-widgets-and-themes.md): widget structure, styling priorities, and theming.
 - Android Manifest (references/android-manifest.md): custom AndroidManifest.xml, permissions, and manifest merge.
 - App Distribution (references/app-distribution.md): Google Play (APK/AAB), App Store (IPA), certificates, provisioning, and deployment.
 - tiapp.xml Configuration (references/tiapp-config.md): complete reference for tiapp.xml and timodule.xml, including all elements, properties, and platform-specific settings.

package/skills/ti-guides/references/advanced-data-and-images.md

@@ -15,6 +15,26 @@
   ```
 - Do not ship large pre-populated databases. Ship a small skeleton and download data on first boot to reduce IPA/APK size. The `Resources` directory is read-only, so installing a database copies it to `applicationDataDirectory`, which creates two copies on the device.
   - Android note: in Android 2.2 and earlier, the installer could not uncompress assets over 1 MB. One workaround was to rename the file with a `.mp3` extension to prevent `aapt` compression.
+  - Pattern for downloading a replacement database on first boot:
+  ```javascript
+  const updateDatabase = (newData) => {
+    // delete existing content and rehydrate from downloaded JSON
+  }
+  downloadButton.addEventListener('click', () => {
+    const client = Ti.Network.createHTTPClient({
+      timeout: 10000,
+      onload() {
+        updateDatabase(this.responseData)
+        Ti.UI.createAlertDialog({ title: 'Info', message: 'Database installed' }).show()
+      },
+      onerror(e) {
+        Ti.UI.createAlertDialog({ title: 'Error', message: e.error }).show()
+      }
+    })
+    client.open('GET', 'https://example.com/data.json')
+    client.send()
+  })
+  ```
 
 ### Database version management
 
@@ -45,11 +65,11 @@ const addColumn = (dbname, tblName, newFieldName, colSpec) => {
 
 Choose the right format for each use case:
 
-| Format | Compression | Best for | Avoid for |
-| --- | --- | --- | --- |
-| PNG | Lossless | Icons, text, line art, buttons | Photos (large files) |
-| JPG | Lossy | Photographs | Text, icons, line drawings (artifacts) |
-| GIF | Lossless (256 colors) | Rare cases | Most cases (limited colors, animated GIF not supported everywhere) |
+| Format | Compression           | Best for                       | Avoid for                                                          |
+| ------ | --------------------- | ------------------------------ | ------------------------------------------------------------------ |
+| PNG    | Lossless              | Icons, text, line art, buttons | Photos (large files)                                               |
+| JPG    | Lossy                 | Photographs                    | Text, icons, line drawings (artifacts)                             |
+| GIF    | Lossless (256 colors) | Rare cases                     | Most cases (limited colors, animated GIF not supported everywhere) |
 
 For flip-book animations, use `ImageView.images` with an array of PNG or optimized JPG files instead of animated GIFs.
 
@@ -80,12 +100,12 @@ For flip-book animations, use `ImageView.images` with an array of PNG or optimiz
 
 Resize and compress images before including them in your app to reduce IPA/APK size and network usage.
 
-| Platform | File types | Tool |
-| --- | --- | --- |
-| Mac | PNG, JPG, GIF | ImageOptim |
+| Platform            | File types    | Tool        |
+| ------------------- | ------------- | ----------- |
+| Mac                 | PNG, JPG, GIF | ImageOptim  |
 | Mac, Windows, Linux | PNG, JPG, GIF | ImageMagick |
-| Windows/DOS | PNG | PNGCrush |
-| Windows | JPG | Nikkho |
+| Windows/DOS         | PNG           | PNGCrush    |
+| Windows             | JPG           | Nikkho      |
 
 ---
 

package/skills/ti-guides/references/application-frameworks.md

@@ -118,11 +118,11 @@ app.js:
 // Single namespace pattern
 const app = {};
 
-// Include components (Legacy)
-Ti.include('ui/ApplicationWindow.js');
+// Load components via require (Ti.include is deprecated)
+const AppWindow = require('ui/ApplicationWindow');
 
 // Create and open window
-app.mainWindow = app.ui.createApplicationWindow();
+app.mainWindow = AppWindow.createApplicationWindow();
 app.mainWindow.open();
 ```
 

package/skills/ti-guides/references/coding-best-practices.md

@@ -34,6 +34,8 @@ Ti.App.fireEvent('my_event')
 
 - Defer script loading. Only `require` modules when you need them.
 
+Defer loading to reduce startup time. Only `require` modules when you need them.
+
 Lazy script loading example:
 ```javascript
 // must be loaded at launch
@@ -56,8 +58,16 @@ win1.addEventListener('click', () => {
 });
 ```
 
-- Bridge efficiency: minimize requests for device properties like `Ti.Platform.osname`. Store them in a local variable.
-- Avoid extending the `Ti` namespace. `Ti` objects are proxies to native components. Properties set on them may not reach the native object, arrays return copies, and persistence across SDK versions is not guaranteed. Use modules instead.
+- Bridge efficiency: minimize requests for device properties like `Ti.Platform.osname`. Store them in a local variable:
+```javascript
+const isAndroid = (Ti.Platform.osname === 'android')
+if (isAndroid) { /* Android path */ } else { /* iOS path */ }
+```
+- Avoid extending the `Ti` namespace. Three reasons:
+  1. Ti objects are proxies to native OS components — your extensions may conflict with native functionality.
+  2. Arrays stored on the namespace may be immutable; objects may be null unexpectedly.
+  3. There is no guarantee properties persist across SDK versions.
+  Use your own namespace or CommonJS module instead of modifying `Ti`.
 
 ## 5. App architecture recommendations
 
@@ -85,6 +95,25 @@ const myModule = require('/MyModule');
 myModule.sayHello('User');
 ```
 
+### Namespace with deferred loading (alternative pattern)
+
+If not using CommonJS, you can still defer loading with a namespace:
+
+```javascript
+const someNameSpace = () => {
+  const API = {
+    init() {
+      // create UI or initialize
+    },
+    reset() {
+      // null objects, clean up
+    }
+  }
+  return API
+}
+const ns = new someNameSpace()
+```
+
 ### Custom objects as components
 
 Popular for rapid deployment. It uses a namespace hierarchy. This pattern is less efficient than CommonJS modules, and object references can persist after they are no longer needed.

package/skills/ti-guides/references/commonjs-advanced.md

@@ -162,7 +162,49 @@ const logger = require('logger')
 logger.info('some log statement with a timestamp')
 ```
 
-## 7. Inter-module state sharing
+## 7. Packages of related functionality
+
+Group related classes or helpers in a single module:
+
+```javascript
+// app/lib/geo.js
+class Point {
+  constructor(x, y) {
+    this.x = x
+    this.y = y
+  }
+}
+
+class Line {
+  constructor(start, end) {
+    this.start = start
+    this.end = end
+  }
+
+  slope() {
+    return (this.end.y - this.start.y) / (this.end.x - this.start.x)
+  }
+
+  yIntercept() {
+    return this.start.y - (this.slope() * this.start.x)
+  }
+}
+
+exports.Point = Point
+exports.Line = Line
+```
+
+Usage:
+```javascript
+const Geo = require('lib/geo')
+
+const start = new Geo.Point(1, -5)
+const end = new Geo.Point(10, 2)
+const line = new Geo.Line(start, end)
+Ti.API.info(line.slope())
+```
+
+## 8. Inter-module state sharing
 
 When a module assigns a primitive value to `exports`, the consumer gets a copy, not a live reference. Changes to the internal variable are not reflected in the exported property.
 
@@ -190,7 +232,7 @@ Ti.API.info(stateful.stepVal)        // 5  - still the original copy
 
 Rule: use getter/setter functions for stateful values. Direct property exports of primitives are snapshots at module load time.
 
-## 8. Antipatterns to avoid
+## 9. Antipatterns to avoid
 
 ### Do not assign directly to `exports`
 
@@ -217,7 +259,7 @@ exports.foo = 'bar'
 
 Any data a module needs should be passed during construction or initialization. Avoid globals shared across modules.
 
-## 9. Security and scope
+## 10. Security and scope
 
 All modules have private scope. Variables declared within the module are private unless added to `exports`.
 
@@ -230,7 +272,7 @@ exports.publicMethod = () => {
 }
 ```
 
-## 10. Node.js compatibility
+## 11. Node.js compatibility
 
 Titanium supports Node.js module patterns and `require()` resolution. Node.js modules can often be used directly.
 

package/skills/ti-guides/references/hello-world.md

@@ -15,23 +15,19 @@ Example:
 ti create -t app --id com.example.hello -n HelloWorld -p android,ios -d ~/Projects
 ```
 
-### Using Studio/VS Code
+### Using VS Code
 
-File > New > Mobile App Project
-
-Choose a template:
-- Alloy: MVC framework (recommended)
-- Classic: no framework
+VS Code with the Titanium extension supports project creation via the command palette. The CLI is the most reliable method and works in any editor.
 
 ## Project fields
 
-| Field | Description | Rules |
-| --- | --- | --- |
-| Project name | App name shown to users | - |
-| App ID | Reverse domain notation | `com.company.appname` |
-| Company URL | Your website | - |
-| SDK Version | Titanium SDK to use | Use latest |
-| Deployment Targets | Platforms to support | android, ios, ipad, iphone |
+| Field              | Description             | Rules                      |
+| ------------------ | ----------------------- | -------------------------- |
+| Project name       | App name shown to users | -                          |
+| App ID             | Reverse domain notation | `com.company.appname`      |
+| Company URL        | Your website            | -                          |
+| SDK Version        | Titanium SDK to use     | Use latest                 |
+| Deployment Targets | Platforms to support    | android, ios, ipad, iphone |
 
 ### App ID naming guidelines
 

package/skills/ti-guides/references/hyperloop-native-access.md

@@ -257,7 +257,10 @@ The following resources are compiled automatically: `*.storyboard`, `*.xcdatamod
 
 ## 9. iOS: customizing the Xcode build
 
-Use `appc.js` in the project root to pass custom flags to `xcodebuild`:
+> **⚠️ Legacy: `appc.js`**
+> The `appc.js` file was an Appcelerator/AMPLIFY Platform hook. It is no longer supported. For modern Titanium projects, use `tiapp.xml` or native Xcode project settings for build customization.
+
+For historical reference, `appc.js` at the project root passed custom flags to `xcodebuild`:
 ```javascript
 module.exports = {
   hyperloop: {

package/skills/ti-guides/references/javascript-primer.md

@@ -138,17 +138,25 @@ for (const name of names) {
 }
 ```
 
-### Use var/let/const correctly
+### Prefer `const` and `let` over `var`
+
+`var` is function-scoped and hoisted; `let` and `const` are block-scoped and clearer.
 
 ```javascript
-// ES5: use var (function-scoped)
+// Avoid: var (function-scoped, can be accidentally hoisted)
 var x = 10;
 
-// ES6+: use let and const (block-scoped)
-let y = 20;        // Can be reassigned
-const z = 30;       // Cannot be reassigned
+// Prefer: const for values that do not change
+const MAX_RETRIES = 3;
+const config = { timeout: 5000 };
+
+// Use let only when the binding must be reassigned
+let retryCount = 0;
+retryCount++;
 ```
 
+Rule of thumb: reach for `const` first; switch to `let` only when you need to reassign; never use `var` in new code.
+
 ---
 
 ## Common patterns

package/skills/ti-guides/references/resources.md

@@ -14,7 +14,6 @@ Community resources, support channels, tools, and learning materials for Titaniu
 ### Module resources
 
 - Module Search: https://modules.titaniumsdk.com/
-- Ti.Utils: https://github.com/TimanMax/Ti.Utils
 - From Zero to App: https://fromzerotoapp.com/
 
 ### Documentation
@@ -36,7 +35,6 @@ Community resources, support channels, tools, and learning materials for Titaniu
 
 ### Sample applications
 
-- Ti.Bluetooth: https://github.com/mwaylabs/ti.bluetooth
 - Ti.Map: https://github.com/tidev/ti.map
 - KitchenSink: https://github.com/tidev/KitchenSink
 

package/skills/ti-guides/references/style-and-conventions.md

@@ -101,3 +101,4 @@ function getCustomer(customerName) {}
 
 - Douglas Crockford's JavaScript Code Conventions
 - Google's JavaScript Style Guide: https://google.github.io/styleguide/jsguide.html
+- TiDev ESLint Configuration (rules used for SDK-related npm packages and CLI code): https://github.com/tidev/eslint-config-axway

package/skills/ti-guides/references/tiapp-config.md

@@ -243,38 +243,6 @@ Since 6.1.0. Allow or disallow custom iOS 8+ keyboard extensions. Custom keyboar
 <property name="allow-custom-keyboards" type="bool">false</property>
 ```
 
-#### `appc-sourcecode-encryption-policy`
-
-Encryption policy for app assets.
-
-```xml
-<property name="appc-sourcecode-encryption-policy">remote</property>
-```
-
-Values:
-- `embed`: key embedded in binary (padded/obfuscated)
-- `remote`: key stored remotely (requires internet, default)
-
-#### `appc-security-jailbreak-detect`
-
-Prevent running on jailbroken/rooted devices.
-
-```xml
-<property name="appc-security-jailbreak-detect">true</property>
-```
-
-Requires `appc-sourcecode-encryption-policy` set to `remote`.
-
-#### `appc-security-debugger-detect`
-
-Prevent debugger connections.
-
-```xml
-<property name="appc-security-debugger-detect">true</property>
-```
-
-Requires `appc-sourcecode-encryption-policy` set to `remote`.
-
 ---
 
 ## Android section

package/skills/ti-howtos/SKILL.md

@@ -11,18 +11,17 @@ Hands-on guide to Titanium SDK native integrations. Focuses on practical steps,
 
 ## Project detection
 
-::::info Auto-detects Titanium projects
-This skill detects Titanium projects automatically.
-
-Indicators:
-- `tiapp.xml` exists (definitive)
-- Alloy project: `app/` folder
-- Classic project: `Resources/` folder
-
-Behavior:
-- Titanium detected: provide native integration guidance, permissions, modules, and platform notes
-- Not detected: say this skill is for Titanium projects only
-::::
+> **️ℹ️ Auto-detects Titanium projects**
+> This skill detects Titanium projects automatically.
+>
+> Indicators:
+> - `tiapp.xml` exists (definitive)
+> - Alloy project: `app/` folder
+> - Classic project: `Resources/` folder
+>
+> Behavior:
+> - Titanium detected: provide native integration guidance, permissions, modules, and platform notes
+> - Not detected: say this skill is for Titanium projects only
 
 ## Integration workflow
 
@@ -61,39 +60,38 @@ Behavior:
 
 ### Platform-specific properties
 
-::::danger Platform-specific properties need modifiers
-Using `Ti.UI.iOS.*` or `Ti.UI.Android.*` without platform modifiers can break cross-platform builds.
-
-Bad example:
-```javascript
-// Wrong: adds Ti.UI.iOS to Android build
-const win = Ti.UI.createWindow({
-  statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT
-});
-```
-
-Good options:
-
-TSS modifier (Alloy):
-```tss
-"#mainWindow[platform=ios]": {
-  statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT
-}
-```
-
-Conditional code:
-```javascript
-if (OS_IOS) {
-  $.mainWindow.statusBarStyle = Ti.UI.iOS.StatusBar.LIGHT_CONTENT;
-}
-```
-
-Always require modifiers:
-- iOS: `statusBarStyle`, `modalStyle`, `modalTransitionStyle`, any `Ti.UI.iOS.*`.
-- Android: `actionBar` config, any `Ti.UI.Android.*` constant.
-
-For TSS platform modifiers, see the code conventions in `skills/ti-expert/references/code-conventions.md#platform--device-modifiers` or the platform UI guides in `references/ios-platform-deep-dives.md`.
-::::
+> **🚨 Platform-specific properties need modifiers**
+> Using `Ti.UI.iOS.*` or `Ti.UI.Android.*` without platform modifiers can break cross-platform builds.
+>
+> Bad example:
+> ```javascript
+> // Wrong: adds Ti.UI.iOS to Android build
+> const win = Ti.UI.createWindow({
+>   statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT
+> });
+> ```
+>
+> Good options:
+>
+> TSS modifier (Alloy):
+> ```tss
+> "#mainWindow[platform=ios]": {
+>   statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT
+> }
+> ```
+>
+> Conditional code:
+> ```javascript
+> if (OS_IOS) {
+>   $.mainWindow.statusBarStyle = Ti.UI.iOS.StatusBar.LIGHT_CONTENT;
+> }
+> ```
+>
+> Always require modifiers:
+> - iOS: `statusBarStyle`, `modalStyle`, `modalTransitionStyle`, any `Ti.UI.iOS.*`.
+> - Android: `actionBar` config, any `Ti.UI.Android.*` constant.
+>
+> For TSS platform modifiers, see the code conventions in `skills/ti-expert/references/code-conventions.md#platform--device-modifiers` or the platform UI guides in `references/ios-platform-deep-dives.md`.
 
 ## Reference guides