Best PromptsPersonalized Bedtime Story
A calming, age-calibrated bedtime story starring your child: gentle arc, repeated refrain, and an ending engineered for sleep, not excitement.
Write a bedtime story for my child.
Child: [NAME + AGE]
Tonight's personal details (the magic ingredients): [THEIR PET / FAVORITE ANIMAL / STUFFED ANIMAL'S NAME / SOMETHING FROM TODAY: "she lost a tooth", "we saw ducks at the pond"]
Story world they love: [e.g. "animals who talk" / "gentle dragons" / "the moon and stars" / "diggers and trucks"]
Anything to weave in gently (optional): [A LESSON OR REASSURANCE: "sharing", "first day of school is coming", "the dark is friendly", or "nothing, just cozy"]
Calibrate to age:
- Ages 3-5: 300-600 words, one simple linear thread, familiar cozy settings, concrete words, short sentences.
- Ages 6-8: 700-1,200 words, room for light adventure in the middle, a little more character feeling, but the same sleepy landing.
The shape (non-negotiable: this is a sleep tool, not entertainment):
1. **Begin in safety**: warm, familiar, settled. [NAME] is cozy; the world is kind.
2. **One small, soft problem**: a lost mitten, a star that won't twinkle, a sleepy bear who can't find his spot. Never scary, never urgent, no villains.
3. **Gentle resolution**: solved with kindness, help, or patience, about two-thirds through. All tension gone well before the end.
4. **The descent into sleep**: the final third slows down on purpose: sentences get shorter, characters yawn, lights dim, sounds soften. End with [NAME] (or the character) safe, warm, heavy-eyed, home. The last line should practically whisper.
Techniques:
- A repeated refrain 3-4 times through the story ("sleepy paws, sleepy nose, sleepy tail..."): repetition is safety, and kids join in.
- Soft sound words over rhyme-forcing. If a rhyme doesn't come naturally, don't bend the sentence for it.
- [NAME] appears throughout, not just once at the start.
Absolutely no: cliffhangers, "to be continued", exciting climaxes in the final third, new characters after the midpoint, or anything that invites "what happens next?!": the correct final reaction is a yawn.How to use
Models default to exciting story arcs (rising action, big climax) which is exactly wrong at bedtime; the descent-into-sleep structure is the fix, and the refrain is the sneaky-best part (by night three they'll say it with you). Read at about two-thirds of your normal pace, slowing further on the final page. Save the ones that work: a personalized story that lands becomes a request for weeks.
More writing prompts
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes af
Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can su
Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.