"You don't need a team", "you can grow without hiring specialists" — phrases like these instantly give away generated text, even when the underlying claim is true. The problem isn't the model, it's a prompt with no context: Claude simply doesn't know your tone of voice or what counts as a cliche in your niche. The fix isn't a longer prompt — it's a separate style file you attach to the request.
The idea: a file instead of a from-scratch prompt
A prompt like "write a script about X" starts from a blank page every time — Claude has to guess the tone, dodge cliches blind, and reinvent the structure. A style file solves this once: it pins down examples of your hooks, your delivery, and a list of phrases that are off limits. After that you attach the file to your message and keep the prompt short.
Step 1 — pin down what makes text read as AI
Before you build the file, it helps to write out the specific cliches that show up in your niche — vague phrases with no numbers or detail, corporate-speak, sweeping generalizations like "many experts believe". The list ends up short, but it's exactly what goes into the file.
Step 2 — build the style file
The file is a plain text document you attach to your message in Claude. A structure that works:
Style and structure for Reels scripts
Tone: direct, no corporate-speak, no formal address.
Niche: [fill in yours].
Banned phrases:
— "you don't need a team" / "you can grow without specialists";
— any generalization with no specifics ("many experts believe");
— cliche openers ("in today's world", "everyone wants").
Examples of hooks in my style:
— [drop in 2-3 of your real hooks that performed];
Required script structure:
1. Hook (0-3 sec) — a conflict or a question, no preamble.
2. Key points — 2-3 items with concrete actions.
3. Mini-example — a short illustration of the point.
4. Call to action — one clear action.
The more specific your hook examples and banned-phrase list, the fewer edits you'll need after generation.
Step 3 — a short request on top of the file
With the file attached, the prompt in the chat stays simple — the file does the heavy lifting:
You are a Reels content producer.
Niche: [fill in yours].
Write a 30-45 second script: hook, key points, mini-example,
call to action. Before you start, read the attached file
and follow its rules strictly.
Step 4 — what to do when a cliche slips through
If corporate-speak or a generalization still made it into the text, don't rewrite the script from scratch. Ask Claude to point to the exact phrase and replace it, then add that phrase to the banned list in the file — the next generation won't repeat it.
How we do it
The style file is a working technique straight out of our own practice: the qvib.pro knowledge base holds over five hundred cards on prompts and copywriting for Claude, including breakdowns of formats and style — all open, no DMs or reposts required. The same "pin the style down once" principle sits at the core of the qvib engine: it holds a project's tone and structure explicitly instead of re-deriving them on every generation.
Related links
- Prompt template for a Reels script: qvib.pro/arsenal/prompts/scenariy-dlya-reels
- Claude Skills section: qvib.pro/arsenal/skills/claude-skills
- How to write viral scripts: qvib.pro/arsenal/docs/kak-pisat-virusnye-scenarii