Create Instagram Reels from a script

# Make an Instagram Reel from a scenario

## What to make
- Fact-check the scenario's figures and proper nouns (Claude, GitHub 180,000, Matt Pocock, skills, Codex) and submit the verification results
- In the first 2 seconds (hook), subtitle, narration, and on-screen element, all 3, deliver the same message at once
- Make 3 hook variations (same body, different first 2 seconds)
- Place a visual anchor (attention-grabbing element) in the first cut
- No boring stretch of 3 seconds or more; follow the structure hook → problem → information listing → peak → curiosity → CTA
- Compress time with jump cuts and inserts rather than speeding up playback; subtitles built for muted viewing
- Frame-accurate sync with the narration, subtitles of 1–2 lines per screen split by meaning unit
- Emphasize key keywords (skills, 180,000, Codex, free) with color and size, never 3 or more at the same time
- Fix font, position, and emphasis style across the whole video
- Place elements in safe zones that do not cover the Instagram UI (bottom caption, right-side icons)
- Use real screen recordings such as the Claude UI, GitHub page, and terminal
- Enlarge and crop text for mobile readability (no full desktop screen)
- TTS includes pacing, ending handling, a pause before emphasized words, and speed variation
- Check pronunciation of proper nouns (Claude, GitHub, Codex, Matt Pocock, skills)
- Listening review of how numbers and units are read
- Volume normalization across all sections, no clipping
- Sound effects only at hook entry, key information, rhythm shifts, and right before the CTA, not on every cut
- 9:16 vertical, observe Instagram's recommended resolution and bitrate
- CTA only once at the very end, clearly stated as 'Follow + comment "스킬" (skills)', large in the center of the screen
- Produce the caption, hashtags, cover, and posting time as a set together with the video

## Fixed: what does not change
- Scenario, editing style, subtitle style

## Variable: what the creator decides
- The video that is generated

## Evaluation criteria
- Fact verification: deliver it in a trendy way, based on facts as much as possible
- Before producing the video, check all figures and proper nouns in the scenario, and tell me if any are wrong.
- For the UI, terminal, and GitHub page shown on screen, use real screens
- Hook (0–3 seconds): make it hook within 3 seconds. The message must come across from the first frame even without sound
- Prohibited in the hook section: logo, intro animation, "Hello", blank screen
- For the hook line, the subtitle, narration, and on-screen element, all 3, must push the same message at the same time
- Make 3 hook variations so they can be compared (same body + different first 2 seconds)
- Place one visual anchor in the first cut to catch the eye
- Pacing and editing rhythm: immersive and fast-paced. No boring stretch of 3 seconds or more
- Design the rhythm to fit the scenario structure: hook (0–2 seconds) → problem statement → information listing (speed up) → peak information density → leaving curiosity (speed down) → CTA
- Do not compress time by speeding up playback; handle it with jump cuts and inserts
- Make subtitles for muted viewing
- Sync with the narration frame by frame
- 1–2 lines per screen, split by meaning unit
- Emphasize key keywords (skills, 180,000, Codex, free) with color and size, but do not emphasize 3 or more at the same time
- Font, position, and emphasis style are fixed across the whole video
- Place within a safe zone that is not covered by the Instagram UI (bottom caption/button area, right-side icons)
- Final proofreading of spelling and spacing is required
- Make the TTS narration fast-paced but still understandable. If it is mechanically uniform, it shows. Include ending handling, a short pause before emphasized words, and speed variation
- Check pronunciation of proper nouns: Claude, GitHub, Codex, Matt Pocock, skills
- Numbers and units are especially often misread, so a listening review is a must
- Normalize volume across all sections, with no clipping
- Sound effects: put sound effects in appropriate places. But do not put them on every cut. Overuse sounds cheap
- Sound effect placement points: hook entry, appearance of key information, rhythm turning points, right before the CTA
- Screen & visuals: 9:16 vertical, observe Instagram's recommended resolution and bitrate
- Build the screen composition mainly around real screen recordings (Claude UI, GitHub page, terminal)
- Enlarge and crop screen recordings so the text is readable on mobile. If you put in the full desktop screen as is, nothing is visible
- CTA & distribution
- The CTA only once at the end, clearly: "Follow + comment '스킬' (skills)"
- In the CTA section, put the subtitle large in the center of the screen. Viewers may leave here, so make it visually unmistakable
- Make the comment-prompt keyword a short word with a low chance of typos (currently "스킬" is appropriate)
- Make the caption, hashtags, cover, and posting time as a set together with the video

## Original text written by the client
> I'll give you the scenario below, so make an Instagram Reels video that fits this scenario. The reference account is https://www.instagram.com/ih8chz/reels/ . Copy its style when making it. assets Scenario: 99% of Claude users don't know this. You no longer need to study how to use Claude well. Matt Pocock, a world-renowned developer, has released all the skills he uses every day. A full 180,000 people starred it on GitHub. Just say "Install skills" in Claude and you're done. Claude works on its own like an expert, all the way from writing tests to code review and bug diagnosis. There's also a skill that turns conversation content into a planning document. And there's a skill that finds the holes in my plan through an interview. What's even more surprising is that this works as is not only in Claude but also in Codex. But the most powerful skill I found while using it is a different one. Just turn this on and the quality of the output changes completely. If you're curious about this, follow Maker Evan and leave "스킬" (skills) in the comments.