@maccesar/titools 2.2.11 → 2.3.0

package/bin/titools.js

@@ -40,7 +40,7 @@ program
 // Update command
 program
   .command('update')
-  .description('Update installed knowledge packages and agent (not the CLI)')
+  .description('Check for newer CLI versions, then sync installed knowledge packages and agent')
   .option('-l, --local', 'Update local skills in the current project')
   .action(updateCommand);
 

package/lib/commands/update.js

@@ -1,6 +1,6 @@
 /**
  * Update command
- * Updates skills and docs to the latest version
+ * Checks for a newer CLI version, then syncs skills and docs from the installed package
  */
 
 import chalk from 'chalk';
@@ -105,7 +105,6 @@ export async function updateCommand(options) {
   if (!options.local) {
     const projectDir = process.cwd();
     const isProject = isTitaniumProject(projectDir);
-    const localPlatforms = detectPlatforms(projectDir);
     const hasLocalSkills = isProject && hasSkillsAt(projectDir);
     const hasGlobalSkills = hasSkillsAt(undefined);
 
@@ -177,7 +176,7 @@ export async function updateCommand(options) {
   try {
     const hasUpdate = await checkForUpdate(PACKAGE_VERSION);
 
-    // If there's a newer version on npm, prompt user to update CLI first
+    // If there's a newer version on npm, instruct the user to update the CLI first
     if (hasUpdate) {
       let latestVersion = '(newer)';
       try {
@@ -188,14 +187,14 @@ export async function updateCommand(options) {
 
       spinner.warn('New version available');
       console.log('');
-      console.log(chalk.yellow('A newer version is available on npm:'));
+      console.log(chalk.yellow('A newer version of titools is available on npm:'));
       console.log(`  Current: ${chalk.gray('v' + PACKAGE_VERSION)}`);
       console.log(`  Latest:  ${chalk.green(latestVersion)}`);
       console.log('');
-      console.log('To update, run:');
+      console.log('Update the CLI with:');
       console.log(`  ${chalk.cyan('npm update -g @maccesar/titools')}`);
       console.log('');
-      console.log('Then run this command again:');
+      console.log('After updating, run this command again:');
       console.log(`  ${chalk.cyan('titools update')}`);
       console.log('');
       return;

package/lib/config.js

@@ -31,6 +31,7 @@ export const REPO_API_URL = 'https://api.github.com/repos/macCesar/titools';
 // Skills to install
 export const SKILLS = [
   'ti-expert',
+  'ti-api',
   'purgetss',
   'ti-ui',
   'ti-howtos',

package/lib/downloader.js

@@ -11,6 +11,11 @@ import { unlink } from 'fs/promises';
 import { extract } from 'tar';
 import { REPO_API_URL, REPO_RAW_URL, GITHUB_API_HEADERS } from './config.js';
 
+function getTestLatestNpmVersion() {
+  const value = process.env.TITOOLS_TEST_NPM_LATEST_VERSION;
+  return value && value.trim() ? value.trim() : null;
+}
+
 /**
  * Fetch latest release info from GitHub API
  * @returns {Promise<Object>} Release information
@@ -116,6 +121,11 @@ export async function downloadRawFile(filePath, destPath, ref = 'main') {
  * @returns {Promise<string>} Latest version number
  */
 export async function fetchLatestNpmVersion() {
+  const testVersion = getTestLatestNpmVersion();
+  if (testVersion) {
+    return testVersion;
+  }
+
   const response = await fetch('https://registry.npmjs.org/@maccesar/titools');
 
   if (!response.ok) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maccesar/titools",
-  "version": "2.2.11",
+  "version": "2.3.0",
   "description": "Titanium SDK skills and agents for AI coding assistants (Claude Code, Gemini CLI, Codex CLI)",
   "main": "lib/index.js",
   "type": "module",

package/skills/alloy-guides/SKILL.md

@@ -11,20 +11,19 @@ Reference for building Titanium mobile applications with the Alloy MVC framework
 
 ## Project detection
 
-:::info AUTO-DETECTS ALLOY PROJECTS
-This skill automatically detects Alloy projects when invoked and provides framework-specific guidance.
-
-**Detection occurs automatically** - no manual command needed.
-
-**Alloy project indicators:**
-- `app/` folder (MVC structure)
-- `app/views/`, `app/controllers/` folders
-- `app/models/` folder
-
-**Behavior based on detection:**
-- **Alloy detected** → Provides Alloy MVC documentation, Backbone.js patterns, TSS styling, widgets
-- **Not detected** → Indicates this skill is for Alloy projects only, does not suggest Alloy-specific features
-:::
+> **️ℹ️ AUTO-DETECTS ALLOY PROJECTS**
+> This skill automatically detects Alloy projects when invoked and provides framework-specific guidance.
+>
+> **Detection occurs automatically** - no manual command needed.
+>
+> **Alloy project indicators:**
+> - `app/` folder (MVC structure)
+> - `app/views/`, `app/controllers/` folders
+> - `app/models/` folder
+>
+> **Behavior based on detection:**
+> - **Alloy detected** → Provides Alloy MVC documentation, Backbone.js patterns, TSS styling, widgets
+> - **Not detected** → Indicates this skill is for Alloy projects only, does not suggest Alloy-specific features
 
 ## Quick reference
 
@@ -102,40 +101,39 @@ $.index.open();
 
 ### Platform-specific properties in TSS
 
-:::danger CRITICAL: Platform-specific properties require modifiers
-Using `Ti.UI.iOS.*` or `Ti.UI.Android.*` properties in TSS without platform modifiers causes cross-platform compilation failures.
-
-Example of the failure:
-```tss
-// WRONG - Adds Ti.UI.iOS to Android project
-"#mainWindow": {
-  statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT  // FAILS on Android!
-}
-```
-
-Correct approach - use platform modifiers:
-```tss
-// 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`, any `Ti.UI.iOS.*`
-- Android: `actionBar` config, any `Ti.UI.Android.*` constant
-
-**Available modifiers:** `[platform=ios]`, `[platform=android]`, `[formFactor=handheld]`, `[formFactor=tablet]`, `[if=Alloy.Globals.customVar]`
-
-For more platform-specific patterns, see [Code conventions (ti-expert)](skills/ti-expert/references/code-conventions.md#platform--device-modifiers) or [Platform UI guides (ti-ui)](skills/ti-ui/references/platform-ui-ios.md).
-:::
+> **🚨 CRITICAL: Platform-specific properties require modifiers**
+> Using `Ti.UI.iOS.*` or `Ti.UI.Android.*` properties in TSS without platform modifiers causes cross-platform compilation failures.
+>
+> Example of the failure:
+> ```tss
+> // WRONG - Adds Ti.UI.iOS to Android project
+> "#mainWindow": {
+>   statusBarStyle: Ti.UI.iOS.StatusBar.LIGHT_CONTENT  // FAILS on Android!
+> }
+> ```
+>
+> Correct approach - use platform modifiers:
+> ```tss
+> // 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`, any `Ti.UI.iOS.*`
+> - Android: `actionBar` config, any `Ti.UI.Android.*` constant
+>
+> **Available modifiers:** `[platform=ios]`, `[platform=android]`, `[formFactor=handheld]`, `[formFactor=tablet]`, `[if=Alloy.Globals.customVar]`
+>
+> For more platform-specific patterns, see [Code conventions (ti-expert)](skills/ti-expert/references/code-conventions.md#platform--device-modifiers) or [Platform UI guides (ti-ui)](skills/ti-ui/references/platform-ui-ios.md).
 
 ## Common patterns
 

package/skills/alloy-guides/references/CONTROLLERS.md

@@ -116,15 +116,14 @@ The following are the constants defined by Alloy for use in the controller code:
 * `ENV_TEST` : true if the current compiler target is built for testing on a device
 * `ENV_PRODUCTION` : true if the current compiler target is built for production (running after a packaged installation)
 * `DIST_ADHOC` (since Alloy 1.4.0) : true if the current compiler target is built for iOS Ad Hoc distribution, for example, if you set the `-T dist-adhoc` option when building with the Titanium CLI. Note that `ENV_PRODUCTION` will be true too since this deployment is only for production builds.
-* `DIST_STORE` (since Alloy 1.4.0) : true if the current compiler target is built for deployment to the Google Play Store or iTunes App Store, for example, if you set the `-T dist-appstore` or `-T dist-playstore` option. Note that `ENV_PRODUCTION` will be true too since this deployment is only for production builds.
+* `DIST_STORE` (since Alloy 1.4.0) : true if the current compiler target is built for deployment to the Google Play Store or iTunes App Store, for example, if you set the `-T dist-store` option when building with the Titanium CLI. Note that `ENV_PRODUCTION` will be true too since this deployment is only for production builds.
 
 For example, since iOS devices do not include a back button, the application can conditionally add one to a window controller:
 
 ```javascript
 if (OS_IOS) {
   const closeButton = Ti.UI.createButton({
-        title: 'Close',
-        style: Ti.UI.iPhone.SystemButtonStyle.PLAIN
+        title: 'Close'
     });
 
     closeButton.addEventListener('click', () => {
@@ -223,9 +222,8 @@ const lib = require('library_name');
 lib.foo();
 ```
 
-::: warning ⚠️ Warning
-Titanium and Alloy do not support the Node.js concept of "folders as modules". That is, requiring a folder name does not automatically load the `index.js` or `index.json` file inside the folder, or use the `package.json` file to locate the main entry point. You need to explicitly require the file that serves as the main entry point to the library.
-:::
+> **⚠️ ⚠️ Warning**
+> Titanium and Alloy do not support the Node.js concept of "folders as modules". That is, requiring a folder name does not automatically load the `index.js` or `index.json` file inside the folder, or use the `package.json` file to locate the main entry point. You need to explicitly require the file that serves as the main entry point to the library.
 
 ### Specs Folder