For our editors and designers
How the whole thing runs, start to finish. An ad that already worked goes in at one end; a live ad, with its numbers, comes out the other. Seven stages, seven roles, ten tools — on this one page.
Prizm Labs is our internal system — not for sale.
01 · The flow
Each stage takes one thing in and hands one thing on. The colour of a card says what kind of thing it holds, before the words do.
01 · Swipe
Pull what is already winning: a competitor's paid ad or an organic post, in My Feeds. Ranked by how hard the market is betting on it — how long it has run, how many copies exist.
My Feeds · organic · paid
02 · Teardown
Take it apart to the structure underneath: the hook, the beats, the argument, the offer — with the brand that made it stripped out. Every part labelled from one element library.
Video teardown · Image teardown
03 · Brief
Same structure, the brand's product, its customer's own words — nothing invented the market didn't say first. Every brief gets a number, and that number travels with everything made from it.
Copywriter · Language layer
04 · Make
One brief becomes the assets: the video's voice, scenes and motion, and the statics — as a batch, with hooks and variations. Edits are programmed, not hand-calibrated: the edit runs itself and stops twice for review, at the timeline and at the captions.
Video production · Image production · Video edit · Asset index
05 · Hand-off
Work leaves the machine as one folder with one instruction file. A role — an agent first, a person when needed — picks it up, does its job, and puts the result in returned/.
Editor onboarding · the seven roles below
06 · Live
The uploader sets the ad or the email up, ready to publish — and stops there. Once the go is given, the live id comes back and sits beside the brief it came from.
Ad uploader · Klaviyo uploader
07 · Performance
What the live ad does is read back against its brief and its swipe. When one lands, the machine makes more like it. When one misses, the prompt that made it is fixed once, and everything after is better.
Back to 01
02 · The thread
Every brief gets a number once. Every file made from it carries that number in its name, the hand-off carries it, the ad name carries it, and the live id comes back to sit beside it.
swipe what was taken, and where from construct its structure, the brand stripped out brief-NNNN the brief, numbered once brief-NNNN · asset every file made from it <role>-handoff the folder it left in live id what came back — the trace is closed
One record per asset, so anything live can be traced back to the swipe it came from, and any swipe forward to what it earned. That is the whole reason a miss can be fixed at the prompt rather than at the output.
Nothing in the tools names a brand. The brand arrives from its folder when a run starts, so the same chain serves every brand and never has to be explained twice.
03 · The roles
A role reads its hand-off folder, runs its tools, and puts its work in returned/. A person can take the same folder and do the same job, because the folder is the instruction.
| Role | Gets | Makes | Hands back | Stops at |
|---|---|---|---|---|
| creator-manager | New creator briefs, and the talent cards | The match: each brief to a creator, with due dates | Sent and delivered status for every creator hand-off | Sending a brief to a creator |
| creator | Their own folder of briefs, with references and the product's record | Raw footage and pictures for those briefs | Files named with the brief and asset numbers | Hands back only |
| clipper | The open briefs of a drop: scenes, references, captions | Clips and slideshows | The finished clips and where they were posted | Posting a clip |
| graphic-designer | Image, sequence, email and page briefs, with exact words and layout | Static ads, sequences, emails, landing pages | Finished files named to the standard | Hands back only |
| video-editor | The edit kit: clips per scene, voice, music, cut sheet, caption look | Finished cuts | One 9:16 master per brief, plus hook versions | Hands back only |
| ad-uploader | Named ads, copy, the landing page by link id, the ad set plan | The ads set up in Meta, ready to publish | The live ad id for every ad | Publishing |
| klaviyo-uploader | Finished emails, subject lines, send date, audience | The emails set up in Klaviyo, ready to send | The campaign id for every send | Scheduling or sending |
Roles, never people. The folder says who it is for by job, so an agent or any person in that job can pick it up.
04 · The folder
Every hand-off is one folder and one instruction file the receiver's own tool can read, explain back, and act on.
Shared Assets/handoffs/<role>/<brand>/<name>/. Open it, read handoff.md, do the job, and put the finished files in returned/, each named <brief id>_asset-NN. The team then runs the take-back, which files it against its brief.<role>-handoff_<brand>_<date>/ handoff.md the instructions manifest.json every id inside, checks passed briefs/ one brief per piece assets/ what they work from or upload references/ swipes, inspiration, the product record returned/ their finished work
Before a folder is sent, every product, offer and link inside it is checked against the catalog, every link is opened, and every name is checked against the standard. A folder with an unknown id does not leave.
One line: the job, the brand, the batch.
The role, never a name.
Every brief and asset, by id.
The steps, in order.
The product, the words, the offer, the link.
Each link id with its working address.
What to look at before handing back.
Into returned/, each file named <brief id>_asset-NN. The team takes it back from there.
05 · Use it
Anyone who makes work with us — clippers, creators, editors, designers — uses Prizm Labs from their own Claude Code or Higgsfield Supercomputer account. The repo is public: open it in your account, point it at a brand, run the tool.
In Higgsfield Supercomputer, clone github.com/daemnapps/prizm-labs into your workspace. In Claude Code, open the same repo on your machine.
Say which brand you are working on. The brand folder holds the product, the customer and the look; every tool reads it, so a brand is never explained twice.
Say what you want in plain words: "tear this video down for the brand", "make the scenes for this brief", "edit this kit". The tool does the rest and stops where a person needs to look.
Higgsfield runs everything in its own workspace, so nothing is installed on your computer. Claude Code runs the same tools on your machine. Say "pull for updates" in either and the tools stay current.
06 · The tools
Every tool carries the name it has in production, and sits on one stage of the line.
| Stage | Tool | What it does | |
|---|---|---|---|
| Swipe | My Feeds | What already works, organic and paid: the formats pulled apart from posts that worked, and thousands of live competitor ads reduced to the angle shapes that keep working. The index over both is on this site. | team-only library build |
| Teardown | Video teardown | Any video in, a brief out. Written for someone who has never done this. | |
| Teardown | Image teardown | Paste a picture ad — one still or a carousel. Get its structure and a brief for your brand, for the machine or for a creator. | |
| Brief | Copywriter | The copy: primary text, captions, headlines. | |
| Brief | Language layer | Every word the tools use comes from what the market said; this is the query over the brand's language, with the receipt on every row. | |
| Make | Video production | An AI video brief in; the voice, the stills and the clips out. | |
| Make | Image production | Brief to finished static ad — the twin of video production. | |
| Make | Video edit | An approved kit becomes the finished, captioned video. It stops twice for review: the timeline, then the captions. | |
| Make | Asset index | A folder of footage becomes records you can search by what is in the clip. | |
| Hand-off | Editor onboarding | The front door for editors and designers: the walkthrough, the SOP, the prompts, the brief queue. The page. | team-only queue |
Team-only means the part that builds it reads our private workspace. What it publishes — the page, the SOP, the prompts — is here for everyone. Everything else runs on any brand folder that is set up the way the template shows.
Then again
One ad that already worked goes in. Every format, every variation, every brief comes out, goes live on the go, and what it earns decides the next swipe. If you make the ads, start with onboarding.