/yuv-pilot

name: yuv-pilot
description: Top-of-pyramid orchestrator for Yuval Avidani's YUV.AI brand work. Apply when (a) the user wants YUV.AI output and the medium is ambiguous or multi-medium, (b) the user is planning a launch or cross-channel campaign for YUV.AI, or (c) explicitly invokes /yuv-pilot or asks "what should I build for YUV.AI / my brand". Triggers: "for YUV.AI", "for my brand", "YUV.AI launch", "ship something for me", "orchestrate", "cross-channel", "multi-platform for me", "yuv-pilot", Hebrew השקה, מולטי-פלטפורמה ל-יובל. Does NOT do the work — it identifies the right downstream YUV.AI skills (yuv-design-system across 3 modes, yuv-decks for slides, yuv-viral-video for short MP4s, hyperframes for HTML→MP4, nano-banana for in-brand imagery, gsap for animation), explains the composition, hands off. Does NOT apply to non-YUV.AI requests. When a request is clearly single-medium (just a deck, just a viral short), the specific skill wins — yuv-pilot is the front door for ambiguous or multi-output requests.

yuv-pilot — the YUV.AI skills pyramid

> The flight director. Doesn't fly the plane — tells you which crew member should.

This skill is the **top of the YUV.AI skills pyramid**. Its job is to recognise a YUV.AI brand request, identify what's actually being asked for, pick the right combination of downstream YUV.AI skills, and hand off cleanly. It does not produce visual output, write code, or render assets. It is a router.

The metaphor maps to the brand: in flight ops, the pilot doesn't refuel the aircraft, doesn't load the cargo, doesn't run ATC. The pilot decides the mission and tells the right specialist when to act.

---

§0. When to apply — strict YUV.AI gate

✅ Apply when

• The user mentions **YUV.AI**, **"my brand"**, **"my design system"**, **"for me"**, **"my launch"**, **"my channels"**, **"Let's Fly High"**, OR explicitly invokes `/yuv-pilot`.
• The deliverable spans **multiple media** — a launch needing a site + deck + reel + social cards is the canonical case.
• The user is asking *"what should I build for YUV.AI"* / *"how do I ship X for my brand"* — strategic, not yet a single artifact.
• The medium is ambiguous and clarification would help — e.g. "do something for me about MCP" (could be deck, blog, reel, social, site section).

❌ Do NOT apply when

• The request is clearly **single-medium** AND a specific downstream skill obviously owns it:
• *"Make me a YUV.AI deck about X"* → `yuv-decks` wins directly. yuv-pilot stays out.
• *"Edit this video into a viral short for me"* → `yuv-viral-video` wins. yuv-pilot stays out.
• The request is **non-YUV.AI** (generic game / app / client work / third-party brand). The whole pyramid stays out.
• The user has already named the specific tool / skill they want.

The principle: **yuv-pilot is the front door for ambiguity.** When the path is obvious, let the specific skill take the request.

---

§1. The YUV.AI skills pyramid

                          ┌─────────────────────┐
                          │     yuv-pilot       │  ← you are here
                          │  (intent → route)   │
                          └──────────┬──────────┘
                                     │
            ┌────────────────────────┼────────────────────────┐
            ▼                        ▼                        ▼
       ┌─────────┐            ┌─────────────┐          ┌──────────────┐
       │yuv-decks│            │ yuv-design- │          │ yuv-viral-   │
       │         │            │   system    │          │   video      │
       │  talks  │            │             │          │              │
       │ slides  │            │ palette,    │          │ short MP4s,  │
       │ keynotes│            │ typography, │          │ Reels, Shorts│
       │ open-   │            │ assets,     │          │ video-use +  │
       │ slide   │            │ socials,    │          │ hyperframes  │
       │ Yuval   │            │ credentials │          │ MrBeast-pace │
       │ voice   │            │ 3 modes     │          │              │
       └────┬────┘            └──────┬──────┘          └──────┬───────┘
            │                        │                        │
            ▼                        ▼                        ▼
        open-slide          tokens / components       hyperframes
        slide-authoring     brand assets               video-use
        nano-banana-pro     social link set            gsap
        mermaid-diagrams    lessons-learned            nano-banana-pro
        gsap                                           gsap
                            ╲                          ╱
                             ╲                        ╱
                              ╲                      ╱
                               ▼                    ▼
                          ┌─────────────────────────────┐
                          │ Brand DNA (Universal Fly    │
                          │ High Throughline)           │
                          │ • flight metaphors          │
                          │ • HUD + dials               │
                          │ • phoenix mark + watermark  │
                          │ • Anton + JetBrains Mono    │
                          │ • "Let's Fly High"          │
                          └─────────────────────────────┘

How to read the pyramid

• **Top tier (orchestrator):** `yuv-pilot`. Routes intent.
• **Middle tier (opinionated YUV.AI skills):** `yuv-decks`, `yuv-design-system`, `yuv-viral-video`. Each owns one mode of output. Each calls down to the bottom tier.
• **Bottom tier (generic tools):** `open-slide`, `hyperframes`, `gsap`, `nano-banana-pro`, `video-use`, `mermaid-diagrams`, `slide-authoring`. Not YUV.AI-specific; the middle tier uses them.
• **The Brand DNA layer** runs across the entire pyramid — every YUV.AI output, regardless of medium, carries the flight throughline. The palette is the chapter; the motifs are the brand.

---

§2. Routing tab