ti-guides_skill
- Shell
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill maccesar/titanium-sdk-skills --skill ti-guides- SKILL.md5.7 KB
Overview
This skill is the Titanium SDK fundamentals and configuration guide for inspecting and improving Titanium (Alloy and Classic) projects. It focuses on stability, bridge performance, memory hygiene, Hyperloop native access, tiapp.xml configuration, CLI usage, and app distribution. Use it to review code, optimize runtime behavior, and prepare builds for App Store or Google Play.
How this skill works
The skill auto-detects Titanium projects by locating a tiapp.xml file and examines project layout (app/ for Alloy, Resources/ for Classic). It runs checklist-style reviews: architecture patterns, event listener cleanup, bridge access hotspots, database transactions, Hyperloop usage, and distribution settings. Results include concrete recommendations, ES6+ code snippets, and short rationales tied to performance and reliability.
When to use it
- When auditing a Titanium project for stability or performance
- Before app distribution to App Store or Google Play
- When reviewing Hyperloop/native integration or thread usage
- During code reviews to enforce CommonJS or Alloy modular patterns
- When investigating memory leaks or bridge-related slowness
Best practices
- Always detect project type via tiapp.xml and branch guidance for Alloy vs Classic
- Remove Ti.App and Ti.Geolocation listeners during controller cleanup to avoid leaks
- Cache native properties outside loops (avoid bridge calls inside iterations)
- Use Hyperloop with explicit casting and run UI work on main thread only
- Wrap SQLite work in transactions and always close resultsets and DB handles
Example use cases
- Audit an Alloy app for unremoved global listeners and propose fixes
- Optimize a screen by replacing repeated Ti.Platform/Ti.DisplayCaps calls with cached values
- Review Hyperloop usage to ensure correct selector naming and proper threading
- Prepare tiapp.xml and signing configuration for App Store and Google Play builds
- Identify long-running DB queries and convert to transactions with proper resultset closure
FAQ
It looks for a tiapp.xml file; presence indicates Alloy or Classic Titanium and triggers SDK-specific guidance.
What common bridge mistakes do you flag?
Accessing Ti.Platform, Ti.DisplayCaps, or native properties inside loops instead of caching them, and excessive cross-bridge object marshalling.
Does the guide include code examples?
Yes. Recommendations include modern ES6+ implementation examples and minimal rationale on performance or memory impact.