Telar
v0.17.0 · plugin for Claude Code + Codex

Telar

plan · build · review · ship — with agents

A multi-agent engineering framework that takes a feature from idea to production: orchestrated planning, adversarial review gates, a persistent knowledge base, cross-model verification, and a new OKF domain-knowledge layer agents consult before touching your data model. It spans cross-platform apps end to end: mobile (React Native & Flutter) with deep native integration, web (Astro, Next.js/shadcn, Vite/TanStack admin panels), Rust service layers, and desktop — stack-aware across every domain.

Get started → View on GitHub
48
Agents
122
Skills
24
Commands
4
Hooks
7
Rules
29
Scripts

Explore the framework

Every component is documented with what it does, when to use it, and a link to its source.

🤖

Agents

51 specialists

Mobile & native platform experts, native bridges, architects, security, testing, release, orchestration, plus a web stack (Astro/Next.js/TanStack + framework-agnostic React, and web security/performance/accessibility), Rust service, and desktop (Electron/Tauri) agents.
🧩

Skills

126 modules

Reusable reference modules — navigation, state, performance, payments, blueprints, workflow, web stack, and Rust services.
⌘

Commands

24 workflows

Slash commands that drive end-to-end workflows: create, add-feature, review, orchestrate, release.
📐

Rules

7 always-on

Standards applied automatically — security, quality gates, performance, simplicity, requirements.
🎼

Orchestration

opt-in pipeline

Plan & design review gates, a 4-phase execution loop, knowledge base, and external AI delegation.
📘

Examples

end-to-end

Real command flows for building, optimizing, releasing, auditing, and migrating cross-platform apps.

The workflow

The recommended path for building a feature with Telar.

  1. Explore — always read the existing codebase first (codebase-first rule).
  2. Requirements — establish what to build in REQUIREMENTS.md.
  3. Research — decide how to build it in RESEARCH.md (brainstorm first).
  4. Plan — break work into atomic tasks in PLAN.md + PROGRESS.md.
  5. Build — iterate with simulator verification.
  6. Debug — find the root cause before fixing.
  7. Verify — require fresh evidence before claiming done.
  8. Review — two-stage gates: requirement compliance + code quality.

Install

Claude Code

# Add the marketplace
claude plugin marketplace add zekiyugnak/telar-framework

# Install the plugin
claude plugin install tl-telar@telar

Codex

# Latest development build
codex plugin marketplace add zekiyugnak/telar-framework --ref develop
codex plugin add tl-telar@telar
codex plugin list --marketplace telar

For stable installs, use --ref main. Then start a new Codex thread and invoke Telar with @tl-telar or bundled skills such as $orchestrate. See Getting Started for the full guide.