ti-expert

Guide design and review of Titanium SDK apps across Alloy and Classic stacks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Titanium SDK projects (Alloy or Classic) often suffer from unclear architecture, inconsistent boundaries between layers, and migration uncertainty. This Skill provides expert guidance to design, review, and migrate Titanium projects, helping teams establish maintainable structures, proper cleanup patterns, and robust testing practices.

Core Features & Use Cases

  • Auto-detects Alloy vs Classic project types and tailors guidance accordingly.
  • Guides on project structure, layer boundaries (controllers, views, services, models/collections), memory cleanup, and testing strategies.
  • Supports migration planning for legacy apps, architectural audits, and implementation of scalable patterns.

Quick Start

Create an architecture assessment for a Titanium project and outline a reusable skeleton with clear boundaries for controllers, services, and data access.

Frequently Asked Questions about ti-expert

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

FAQPage Schema
How do I structure a Titanium SDK project to separate controllers, views, and services properly?

Titanium SDK project structure requires strict layer boundaries between controllers, views, and services to ensure maintainability. This Skill guides you in defining per-layer boundaries and safe defaults for scaffolding scalable Alloy and Classic applications.

What is the best way to migrate a legacy Classic Titanium app to the Alloy framework?

Migrating a Classic Titanium app to Alloy requires careful planning of architectural shifts and project layout. This Skill provides migration task workflows and architectural audits to safely transition legacy codebases into structured Alloy patterns.

How does memory cleanup work for models and collections in Titanium Alloy apps?

Memory cleanup for Titanium Alloy models and collections requires explicit destruction strategies to prevent leaks. This Skill enforces safe defaults for memory management, guiding you through proper controller cleanup patterns and data access boundaries.

Can I use this to audit an existing Titanium SDK project for architectural issues?

Auditing an existing Titanium SDK project involves reviewing layer boundaries, testing strategies, and structural consistency. This Skill performs architectural audits, auto-detects Alloy or Classic setups, and outlines reusable skeletons with clear separations.

When do I need to use separate patterns for models vs collections in Titanium app development?

Separating models and collections in Titanium app development is needed when managing complex data access and state. This Skill guides you through architectural decisions, ensuring proper data layer boundaries and robust testing practices.

Does this Skill support both Alloy and Classic Titanium project types?

Support for both Alloy and Classic Titanium project types is built into the core workflow. The Skill auto-detects your project type and tailors its structural guidance, migration planning, and architectural review strategies accordingly.