Telar
Guide

Examples

Real command flows for common tasks. Each one chains the right agents, skills, and rules behind a single command.

Create a new app

/tl-telar:create-app fitness tracking app with Supabase

Gathers requirements, brainstorms architecture, sets up navigation and state management, and scaffolds CI/CD — producing REQUIREMENTS.md and a working project skeleton.

Add a feature

/tl-telar:add-feature push notifications with deep linking

Explores the existing codebase first, brainstorms the approach, plans atomic tasks, implements with simulator verification, and runs the two-stage review gates before completion.

Optimize performance

/tl-telar:optimize-perf slow list rendering

Profiles the bottleneck, applies quick wins (FlashList migration, memoization, image caching), then deeper optimizations — measuring before and after.

Set up CI/CD

/tl-telar:setup-cicd with GitHub Actions

Configures build, test, and deploy automation with Fastlane/EAS, including code-signing handling for both platforms.

Release to the stores

/tl-telar:release-app to App Store and Play Store

Runs pre-release quality gates, builds signed artifacts, prepares store metadata, submits, and sets up release monitoring.

Security audit

/tl-telar:audit-security full

Audits against the OWASP Mobile Top 10 and returns P1/P2/P3 priority-ranked, evidence-based findings.

Migrate a native app

/tl-telar:migrate-app from native iOS to Flutter

Plans and executes a migration from native iOS/Android to cross-platform React Native or Flutter, preserving behavior.

Set up OTA updates

/tl-telar:setup-ota with Expo Updates

Configures over-the-air updates (CodePush, Expo Updates, or Shorebird) with update policies and rollback strategy.

End-to-end orchestrated build

# Enable orchestration once
/tl-telar:setup-orchestration

# Drive the full pipeline
/tl-telar:orchestrate Add authentication with email + password and biometrics

Runs the design gate, drafts and reviews a plan, decomposes it into Work Units, and executes them through the 4-phase loop — with independent Work Units running in parallel (deps satisfied + non-overlapping file_scope, bounded by execution.max_parallel_wus) — ending at COMMIT-READY. See Orchestration → Parallel dispatch for details.

Using workflow skills individually

You don't have to use full orchestration. The workflow skills compose on their own:

/tl-telar:add-feature authentication
# → requirements-gather → brainstorm-first → plan-and-track
# → iterative-build-loop → review-gates → verification-before-completion