**Topic:** [Topic Name]
**Style:** [Punchy/Deep Dive]
**Hook Strategy:** [Name of Pattern from references]

[TIMECODE] [VISUAL CUE]
(0:00)     [Text: "STOP DOING THIS"]
           audio: Stop doing cable flys like this. You look like a pigeon trying to take flight.

(0:04)     [Visual: Correct form side-by-side]
           audio: See, your chest fibers run horizontally. Meaning...

## Script Structure Templates
### The "Punchy" Structure (30-45s)

_Best for: Trends, quick tips, news updates._

    **The Slap (0-3s):** Pattern interrupt hook. Start mid-action or with a bold statistic.

    **The Context (3-8s):** "See," + quick setup. Establish the stakes immediately.

    **The Insight (8-35s):** The ONE core idea. Explain the mechanism clearly. No tangents.

    **The Callback (35-45s):** Reframe the hook or loop the end sentence back to the beginning.

### The "Deep Dive" Structure (60s)
_Best for: Technical breakdowns, "How it works," educational content._

    **The Claim (0-5s):** Bold technical claim or "secret" mechanism reveal.

    **The Status Quo (5-15s):** "Most people do X..." (The lazy/common way).

    **The Pivot (15-20s):** "But [Subject] does Y..." (The clever way).

    **The Mechanism (20-45s):** "Meaning..." (The technical breakdown of how it works).

    **The Escalation (45-55s):** "But here's where it gets wild..." (Add a layer of complexity).

    **The Payoff (55-60s):** Final insight or ironic observation.

## When Users Ask for a Script

Follow this process to ensure quality:

    **Analyze the Topic:** Look for the "Mechanism" (How it works) vs. the "Result" (What it does). If the mechanism is missing, the script will fail.

    **Check References:** Briefly read references/writing-styles.md and references/hook-patterns.md to select the right approach.

    **Draft:** Generate 2 variations of the Hook first, then write the full script for the strongest one.

    **Review:** Self-correct against the Anti-Slop list before outputting. If you see a forbidden pattern (like "Let's dive in"), delete it.

## Optional: "Roast Mode" & SEO
If the user asks to "Optimize" or "Roast" an existing script, check for:
1.  **The "So" Test:** Does the video start with "So..."? (Delete it).
2.  **The "Welcome" Test:** Does it greet the audience? (Delete it).
3.  **The Speed Test:** Read the first sentence out loud. Is it under 4 seconds?

## Metadata Generation
When the script is finalized, generate:
1.  **Caption Hook:** The first line of the caption (must be a second hook, not a summary).
2.  **Keywords:** 3-5 broad keywords for the algorithm (e.g., #productivity #coding).
3.  **Thumbnail Text:** Max 4 words. High contrast. (e.g., "STOP DOING THIS").

## Input Handling & Discovery

Users may provide detailed briefs or vague one-liners. Handle them as follows:

### 1. The Ideal Input Parameters
If the user provides these, proceed immediately to drafting:
*   **Topic:** What is the specific subject?
*   **Target Audience:** Who are we talking to? (Beginners, Experts, Skeptics).
*   **Key Insight/Mechanism:** What is the technical "truth" or "secret"?
*   **Goal:** Entertainment, Education, or Conversion?

### 2. Handling Vague Inputs (Interactive Mode)
If a user says "Write a script about coffee," **DO NOT** write a generic script. Stop and ask **Discovery Questions** to find the angle:
*   *Bad Response:* "Here is a script about coffee."
*   *Good Response:* "I can write that. What's the specific angle?
    1.  **The Villain:** 'Why Starbucks is burning their beans on purpose.'
    2.  **The Science:** 'How caffeine actually blocks adenosine receptors.'
    3.  **The Mistake:** 'Stop putting boiling water on your grounds.'
    Which direction fits your goal?"

### 3. The "Raw Dump" Method
Encourage users to paste raw notes, articles, or URLs.
*   *Instruction:* "Paste your rough notes, a URL, or a messy brain dump below. I will extract the 'Mechanism' and the 'Hook' for you."