Yuv Pilot

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 table — medium → composition

When the deliverable is clear, route directly. When it's ambiguous, ask once and then route.

§3. Worked examples

Example A — "Build me something for my next AI talk"

Read: YUV.AI signal ✓ (it's his talk), medium = deck. Single-medium → route directly to yuv-decks, no need for yuv-pilot to stay involved.

Hand-off response:

Loading yuv-decks — it'll scaffold an open-slide project with the 4-act narrative arc (Boarding → Ascent → Cruise → Descent), use yuv-design-system in Decks mode (purple/yellow/grey, FlightHUD, PurpleBar, Anton headlines), and optionally pull in nano-banana-pro for hero imagery. What's the talk about, and who's the audience?

Example B — "I want to launch my new course. Need a website, a hype video, and Instagram posts."

Read: YUV.AI signal ✓, multi-medium (site + video + social). Stay in yuv-pilot and orchestrate.

Hand-off response:

Orchestrating a 3-artifact YUV.AI launch. The course is practical.yuv.ai → Warm Editorial mode across all artifacts. Build order I'd recommend:

1. Site → yuv-design-system (Warm Editorial) + Hyperframes-compatible signature video banner at the top.
2. Hype video → yuv-viral-video (or cinematic-ai-video if you want AI-generated footage) + hyperframes for composition.
3. Instagram posts → yuv-design-system (Warm Editorial) + nano-banana-pro for the editorial imagery.

Same design tokens flow through all three so the launch reads as one piece. Confirm the build order and I'll start with #1.

Example C — "Build me a snake game"

Read: No YUV.AI signal. Generic request. Whole pyramid stays out.

Hand-off response (or just: don't apply):

Generic snake game — picking an appropriate aesthetic for the game, not the YUV.AI brand. If you'd like this to be YUV.AI-branded (Neon palette, phoenix watermark), say "for YUV.AI" and I'll route through the design system.

Example D — "Build me a YUV.AI snake game"

Read: YUV.AI signal ✓, single-medium = game. Skip yuv-pilot, route directly to yuv-design-system (Neon mode) + Three.js or Canvas.

Hand-off response:

Loading yuv-design-system in Neon mode — pink player, cyan food on rich-black canvas, Anton uppercase score, phoenix watermark in the corner. Building now.

Example E — "What should I build to announce I hit 50K subscribers?"

Read: YUV.AI signal ✓ (it's his channel), strategic question — no medium picked. Stay in yuv-pilot.

Hand-off response:

A 50K announcement is canonically a 4-artifact micro-launch:

1. Instagram square infographic with a 0→50K growth chart — yuv-design-system (Neon mode) + nano-banana-pro (or inline SVG).
2. Short reel celebrating it — yuv-viral-video over a candid selfie or screen-share of the channel hitting 50K.
3. A slide in your next talk thanking the community — yuv-decks will fold it into the Boarding act.
4. A pinned X post + LinkedIn post with the infographic + a thank-you.

Which one first? I'd start with the infographic — it's the artifact every other piece will reference.

§4. When to ask the user vs. just route

Just route (no question) when:

• The medium is named in the prompt ("a deck", "a reel", "a landing page", "a tweet image").
• The brand-family is named ("for my course" → Warm Editorial, "for Hope" → Warm Editorial).
• The user has been here recently and the convention is clear.

Ask once when:

• Multi-medium and the build order matters.
• "Something for my brand" without a deliverable named.
• An ambiguous mode hint ("kind of editorial?" — could mean Warm Editorial or could mean Neon with editorial spacing).

Never ask twice for the same question. Pick a default, commit, build, let the user redirect after seeing output.

§5. The hand-off protocol

When yuv-pilot routes, it should:

1. Name the composition explicitly. "Loading yuv-design-system in Neon mode + gsap for the animation."
2. Lock the mode for any downstream call to yuv-design-system. Decks mode for slides; Neon for everything else web/app/game/dashboard/social; Warm Editorial for Hope / practical.yuv.ai family.
3. Confirm the build order for multi-artifact requests.
4. Hand off — let the specific skill take over. Don't keep narrating.

Example hand-off line:

"Routing to yuv-decks (lead) + yuv-design-system in Decks mode + slide-authoring for the open-slide contract. Starting the 4-act narrative now."

§6. Companion / external skills (not YUV.AI-prefixed)

These are the generic tools the middle tier calls down to. yuv-pilot doesn't load them directly, but should know they exist:

§7. When NOT to load yuv-pilot

• Generic requests — no YUV.AI signal. Step back.
• Third-party brand work — client X, friend's project, etc. Step back.
• Single-medium with an obvious downstream skill match — let that skill take it directly. yuv-pilot only adds value when there's ambiguity or multi-medium composition.
• The user has already named the specific tool — honor the explicit choice.

§8. Self-check before handing off

• YUV.AI signal confirmed.
• Medium identified (or clarified with one question).
• Right downstream skills named in the composition.
• Mode locked for yuv-design-system (Neon / Decks / Warm Editorial).
• Build order proposed if multi-artifact.
• Hand-off line spoken, then yuv-pilot stops narrating and lets the specific skill work.

Maintained by @hoodini · yuv.ai · @yuvalav