ti-guides

Guide Titanium SDK configuration for Alloy and Classic projects.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/macCesar/titools --skill ti-guides
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ti-guides
Source: https://github.com/macCesar/titools/tree/main/skills/ti-guides
Command: npx skills add https://github.com/macCesar/titools --skill ti-guides

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Titanium project teams frequently struggle with aligning Alloy and Classic projects to TiDev standards, leading to inconsistent memory management, bridging, and distribution practices.

Core Features & Use Cases

  • Official Titanium SDK fundamentals and configuration guidance for Alloy and Classic projects.
  • Guidance on tiapp.xml configuration, memory management, Hyperloop usage, and app distribution workflows.
  • Reference to in-depth guides and examples to accelerate onboarding and code quality.

Quick Start

Use this guide to refresh Titanium SDK basics and align your project with TiDev standards.

Frequently Asked Questions about ti-guides

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure tiapp.xml for Titanium SDK projects to meet TiDev standards?

Titanium SDK tiapp.xml configuration requires aligning Alloy and Classic projects with TiDev standards, covering memory management, Hyperloop native access, and app distribution to ensure consistent builds.

What's the best way to handle memory management in Alloy and Classic Titanium apps?

Memory management in Titanium apps requires applying TiDev best practices across Alloy and Classic workflows, using Modular CommonJS patterns to prevent leaks and optimize bridge performance.

How does Hyperloop native access work with the Titanium SDK?

Hyperloop native access in the Titanium SDK provides a bridge to native APIs, requiring specific coding conventions and bridge optimization patterns to function correctly within Alloy or Classic project structures.

Can I use Modular CommonJS patterns in both Alloy and Classic Titanium workflows?

Yes, Modular CommonJS patterns can be used in both Alloy and Classic Titanium workflows, providing ready-to-use structures that align with TiDev coding conventions and optimize project maintainability.

Why does my Titanium app distribution workflow have inconsistent bridging practices?

Inconsistent Titanium app distribution and bridging practices occur when Alloy and Classic projects fail to align with TiDev standards, requiring consolidated official references and actionable best practices to resolve.