Seven-step Claude reel workflow
No stills could be taken from the video, so only the cover image was seen.
The post shares a repeatable method: Claude reads a CLAUDE.md map, applies a written taste/style skill, stores dated corrections as memory, checks plans against those corrections, builds from three inputs (mockup, style reference, rhythm reference) with Opus writing video like a web page via HyperFrames, gets reviewed by a 16-expert council, and turns every fix into a rule for the next reel.
- Create one CLAUDE.md map Claude reads first: who you are, where everything lives, and rules that never change.
- Write taste once as a style skill drawn from a post you loved so Claude copies grammar, not brand.
- When you correct something, save a small file with the date and the reason as memory.
- Before any build, have Claude check the plan against past corrections (result in the first second; every scene shows what the voice says).
- Build with only three inputs: a mockup, a style reference, and a rhythm reference.
- Have the model write the video like a web page (HyperFrames); this post’s version used steps only, no voice.
- Run a council of invented experts to review before you do.
- Turn each fix into a rule so the next reel starts better.
Write a short CLAUDE.md that states who you are, where your assets live, and three rules that must never change, then open your next Claude session by having it read that file first.
Only the cover image was seen, not the full reel or any mid-video stills; no speech transcript. Templates for steps 1, 3, and 4 and full reel rules are gated to the page in the creator’s bio—this brief does not include or invent them. Tool version details and exact HyperFrames setup beyond the caption are not shown.
A prompt for your AI
Apply this seven-step Claude reel workflow to the work in front of you. 1. Read a single map file first (identity, where assets live, unchanging rules). 2. Use a written taste/style skill that copies grammar from a loved reference, never the brand. 3. Treat past corrections as dated memory files with reasons. 4. Before building, check the plan against those corrections: is the result clear in the first second, and does every scene show what the voice or text claims? 5. Build from only three inputs: a mockup, a style reference, and a rhythm reference. Structure the piece like a web page of scenes/steps. 6. Review with a council of invented experts and score concrete failures (wrong names, blurred numbers, cut titles). 7. Turn every fix into a standing rule so the next version starts stronger. Produce the map outline, the pre-build checklist against memory, the three-input build plan, and the council review notes. Do not imitate any social caption or creator brand.
Skill from @juliendesigncraft on Instagram.
Ask SignalLab about this post
Answers come from this note only. When the post does not say, SignalLab says so.