DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to keep one character consistent across several clips with Cinematic Video Prompt Skill

Generate a character reference sheet prompt and reuse the same description in every clip.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code

Who it is forA short-film or social video maker in Claude Code whose main character changes look from clip to clip.

The problemEach new prompt describes the character slightly differently, so the same person looks different across the story.

The outcomeA character sheet prompt with three full-body views and a close-up in one image, plus one fixed character description reused in every clip prompt.

What you need first

  • An AI chat tool: Claude Code, Claude.ai or Cowork, or any chat AI where you can paste custom instructions
  • Access to an AI video model such as Veo 3, Kling, Sora or Runway to run the prompt
  • Git installed if you use the Claude Code route

Steps

  1. Run cp -r bonus-skills/character-sheet-lite ~/.claude/skills/ after cloning the repo.
  2. Ask Claude Code for a character sheet prompt that describes your character once.
  3. Generate the sheet in the image model you use and save the result.
  4. Paste the identical character description at the start of each clip prompt for that story.

Prompt for your agent

Using the character-sheet-lite skill from the repo Rylaispirit/cinematic-video-prompt-skill, write an image prompt for a character named <character description> showing three full-body views and one close-up in a single image. Return the prompt and the reusable character description block. Verify the character description is identical in the sheet prompt and in a sample clip prompt.

Caveat. The bonus Lite skill is a limited version, and the README says the full VIP version with complete guides and lookup tables is only available from the author.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page