# Transformation hook, mechanism explainer

**4,849,237 views proved it** · 5 of Damon's swipes use this format

## What it is

The outcome is settled in the opening beats — a two-panel before/after, a year-stamped then-and-now, a promise card, or the worst-looking frame offered first — and the whole rest of the runtime explains why it could be true, in rendered cutaways and labelled diagrams under a running claim caption. The hook furniture never returns after the opening block.

## Why it works

Showing the result first buys the runtime, because everything after it is the viewer looking for the catch rather than waiting for a payoff. The mechanism half then supplies a reason, so a claim the viewer has already seen the end of arrives with an explanation attached.

## The beats, in order

1. the outcome planted: a two-panel before/after, a year-stamp pair, or a promise card over the worst-looking frame
2. the same person or surface in the changed state, still inside the opening block
3. hard turn into the mechanism — a rendered cutaway or a labelled diagram, the running claim caption starting
4. the product in hand, or the routine performed, the caption continuing as one sentence
5. a second mechanism beat — the ingredient, the follicle, the muscle named
6. the last claim clause over the final rendered frame

## On-screen text

the opening carries a card, a year-stamp pair or a composited before/after panel that is gone after the first beats; everything after it is a running claim caption, one clause per beat in a fixed position, never pinned and never repeated

## Camera

two visibly different halves — the transformation half is phone footage in real rooms with no continuity between the two states, and the mechanism half is rendered animation or a pasted labelled diagram with no camera of its own

## Higgsfield — image prompt

```
vertical 9:16, opening: {subject described exactly} in {real location described exactly} in the changed state, {light source}, phone-camera look, slight grain, no retouching, no on-screen text · mechanism: 3D animation of {the structure described exactly} on a plain {colour} background with {product described exactly} acting on it, clean render, even light, no on-screen text
```

## Higgsfield — motion

```
the transformation beats are static phone shots with no camera relationship to each other; the mechanism beats are slow rendered pushes into {the structure} — cut hard between the two halves
```

## Produce it

Paste those into the Higgsfield employee: https://higgsfield.ai/supercomputer/skills?employeeId=0d38d619-0ac2-45c9-bfd5-3371837ccad3

## The references in this folder

- **@alphainfuse** — 4,849,237 views — https://www.instagram.com/p/DZzgwi7NHoc/
- **@leochanglow** — 2,720,073 views — https://www.instagram.com/p/DY5OteWRmNQ/
- **@locdwithp** — 1,748,867 views — https://www.instagram.com/p/DTvte0ADxr5/
- **@dillonxlatham** — 585,737 views — https://www.instagram.com/p/DVFIVo_AV2A/
- **@alphainfuse** — 107,616 views — https://www.instagram.com/p/DTsAVrkCGWM/

Each `.md` beside this file is one reference torn down: its beats with
timestamps, what carries the value, how to shoot it, and its own prompts.
`frames/` holds the six beats of each as one picture.
