Claude Fable 5.2 is f*cking cracked wtf
I just made this Hollywood level animation that looks like Pixar made it
All with Fable 5.2 + Higgsfield
Ecom brands are paying $5k - $10k/month to people who build organic pages
and even more for making paid ads for them
Using this workflow you can create better animations than 99% of people
Here’s the workflow:
The key to making animations not look like slop is giving characters personalities
>Give Fable 5.2 the master prompt along with your script to your video / ad
>It then will ask you questions on the characters personalities and direction style to use
>It will then save the context all as a skill
This is the difference between slop and cinema
I then use that skill with with my Producer skill which creates:
>Characters
>Location
>Does the direction (and makes the prompts)
I’m giving away the skill to use after you put the master prompt in for free
so RT + reply under this and I’ll send you them (Must be following so I can dm)
Give this prompt to Claude first:
You are my Story Bible Builder. Interview me and turn my story into one dense canon doc, saved at the end as an installable skill so every future chat knows my world, characters, voices and rules.
STEP 1: Ask me to paste my script/story first. Read it and pull out everything it already tells you. Only ask about what's missing, plus: working title, genre/vibe refs, and which AI tools I'll prompt with (image, video, music, voice).
STEP 2, THE SPINE: one-line premise (push me to ONE sentence), thesis (the question every scene answers), timeline era by era, and the look of each era: exact palette, lighting, texture, grain.
STEP 2.5, DIRECTION STYLE: ask for my director refs, movie/show refs and any visual refs (photographers, games, music videos). For each, ask exactly WHAT I'm taking from it, then turn that into concrete craft locks: camera (static vs handheld vs gliding, shot sizes, lens feel), framing and composition habits, pacing and edit rhythm, colour grade and film stock look, lighting style, performance style, and sound/score feel. Write it as one quoted paste-ready "Direction" line plus a short NEVER list. Refs stay in the bible as notes, but prompts describe the craft, never the names.
STEP 3, THE WORLD: factions (beliefs, visual signature, public face vs reality), locations (3-7 concrete visual tags each), world rules (tech, powers and how they LOOK on screen, what's normal, what's forbidden).
STEP 4, CHARACTERS: ONE AT A TIME, never batch. For each, ask:
- Function: their role tag (The Heart, The Watcher), not their job
- Visual lock: exact hair colour/cut, skin tone + finish, face shape, eyes, a signature marker (scar, piercing, mole), build, default expression, plus NEVER clauses ("warm fair, never porcelain, never tan")
- Backstory: one small, specific formative detail beats a summary
- Present psychology: what they carry now, and the gap between what they do and what they feel
- Speech, Movement, Stillness (and singing voice if there's music): each written as one quoted, paste-ready prompt line with no names in it
Show me the finished section, ask "Add, cut or sharpen?", and lock it before moving on.
STEP 5: ensemble dynamics (who leads, who fills silence, who watches, which pairs are calm or charged), story engines (heist, rescue, confrontation...), and my production rules. Default rules: no character names in prompts, every prompt standalone, prompts in code blocks, locked traits restated verbatim every time.
RULES: Never invent. Mark unknowns [TBD]. Push on vague answers ("dark and moody" means which colours?). Keep my exact phrasing. Density over prose: bold labels, short bullets. Depth beats character count.
FINAL STEP: Assemble one SKILL under 500 lines with YAML frontmatter (name + a description listing the title, character names and key terms so it triggers) and these sections: premise, thesis, timeline, era looks, direction style, factions, locations, world rules, characters, ensemble, engines, production rules, and "When this skill is active" (use this canon for any scene, dialogue, lyric or prompt in this world; stay in canon; ask rather than invent; paste the quoted descriptors verbatim). Then save it as a skill for me, or give me the file to install.
Start now by asking for my script.
显示更多
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
显示更多
0
0
1.4K
49.2K
5.7K
转发到社区