# Skill: Write website copy in plain human language, not generic AI prose

> Lets an AI writing/coding agent produce website copy that sounds like a real person talking -- concrete, fact-grounded, and ban-listed of filler -- applies whenever a user asks for landing page text, hero copy, about sections, or any on-site content.

Source: sodigi·learn -- vibecoding/teksty-zhivym-yazykom · https://sodigi.io/learn/vibecoding/teksty-zhivym-yazykom

## When to use
- User asks for homepage, landing page, or section copy.
- User wants to rewrite existing copy that "sounds like a robot."
- User needs help giving the AI their personal voice to match their style.
- User is reviewing AI-generated copy and noticing vague adjectives or invented statistics.

## Core rules
- **Open with something concrete** -- a specific fact, number, example, or story. Hook the explanation onto that; never lead with context-setting filler.
- **Proof instead of adjective** -- replace "fast, easy, reliable" with measurable specifics: "loads in 0.8 seconds," "three clicks to checkout," "running without downtime since 2023."
- **Short sentences, plain words** -- write the way you would talk to a friend. If reading a sentence aloud causes you to run out of breath, cut it in two.
- **Never invent facts, reviews, or numbers.** If a real figure is unavailable, insert a `[FILL IN]` placeholder and tell the user to supply it. Do not fabricate "studies" or percentages.
- **Maintain a ban-list.** These phrases must be deleted without mercy: "in today's fast-paced world," "revolutionary," "innovative," "game-changing," "team of professionals," "unique," "unforgettable experiences," "let's dive into why this matters," fake vulnerability openers ("I was scared but..."), and engagement-bait questions at the end.
- When the user provides samples of their own writing or messages, extract and replicate their personal voice (sentence length, vocabulary, tone, humor level) -- that is the brand voice.

## Procedure
1. Identify the product/service and the target reader.
2. Ask for or extract any real facts, numbers, or proof points the user has. If none, identify where `[FILL IN]` markers are needed.
3. Open the first paragraph with a concrete detail, not a welcome or a general statement.
4. Draft in short, direct sentences. Each sentence earns its place with a fact or a move forward.
5. Scan the draft against the ban-list and delete every flagged phrase.
6. If the user has supplied sample writing, re-read it before drafting and mirror the register.
7. Flag every AI-invented statistic or claim that was not sourced from the user. Ask for confirmation or replace with a placeholder.

## Ready-to-use prompt
```
Write homepage copy for [describe the product or service]. Rules:

1. Open with a specific concrete detail -- a real fact, number, or story.
   Do not open with "welcome" or general context.
2. No empty adjectives. Use only verifiable specifics:
   loading time, price, feature count, a real outcome.
3. Write short and plain, like you are telling a friend about your favorite thing.
   Short sentences. Cut anything that needs a breath-catch to read aloud.
4. Do not invent numbers, reviews, or studies. If a fact is missing,
   write [FILL IN] instead of making something up.
5. Banned words (delete on sight): innovative, revolutionary, unique, unforgettable,
   team of professionals, in today's world, game-changing.
6. [Optional] Here is a sample of how I write: [paste 2-3 of your own messages or posts].
   Match this voice and tone throughout.
```

## Pitfalls
- Opening with "welcome to the world of..." -- immediate trust loss, tab closed.
- Praising the product with adjectives ("the best," "premium quality") instead of facts -- any competitor could claim the same words.
- Accepting AI-generated copy as final without scanning for invented statistics or percentages.
- Writing long "smart-sounding" sentences -- length does not equal intelligence, it equals boredom.
- Skipping the voice-matching step -- the site ends up sounding like every other AI-generated page.
- Inserting fake vulnerability hooks or engagement questions at the end of sections -- readers recognize these patterns and distrust them.