Beginner

The email you have been avoiding.
Anyone can use this page. Copy the prompt and try it today.
$5.99
Everyday AI
Edit what you started. Sound like you.
You stay the editor. The model drafts. You decide.
$4.99 · 20 pages
Beginner shelf · drafts you already own · you stay the writer
CONTENTS
Read pages 3 through 6. Then copy one cream box.
THE IDEA
At 9:47 p.m., Lena has an email open and one sentence she hates. She knows what happened. She knows what she needs. The hard part is making the note clear without turning it into a speech.
Dates, promises, names, costs, feelings, and limits come from you. If the draft adds one, delete it.
A note to a sibling is not a note to a landlord. Warm, firm, and brief mean different things with different people.
Read the result aloud. Keep useful cuts. Reject borrowed-sounding language. Check every promise.
A chat can cut repetition, uncover a buried ask, flag accidental heat, or offer subject lines. It cannot remember the conversation for you. It was not in the room.
Hard nos: No invented facts. No borrowed personality. No sending without review.
Then do this: Bring a rough sentence or true notes. Ask for one editing job, not magic.
WHAT THE LABS FOUND
The useful evidence here is modest. It shows how people use writing tools and how clearer prompt structure can help. It does not prove that every generated draft is good.
OpenAI reports that writing is about 40% of work-related messages. About two-thirds of writing messages ask ChatGPT to modify user text.
That is a usage pattern, not a quality guarantee. A shorter message can still be untrue or wrong for the relationship.
Anthropic advises putting long material first and the query last. In its tests, this improved quality by up to 30%, especially with complex multi-document inputs.
Google’s guidance includes objective, persona, context, constraints, and response format.
Hard nos: Do not treat “up to 30%” as a promise. Do not treat common use as proof of accuracy.
Then do this: Bring your draft, state the editing job, and check the result yourself.
BEFORE YOU PASTE
Jon is about to paste six angry paragraphs about a canceled repair visit. Before he does, he writes five lines on paper.
BEFORE-YOU-PASTE SCRIPT
Facts: [what I know]
Person: [recipient and relationship]
Outcome: [one thing I need]
Limit: [what I will not promise]
Privacy: I removed unnecessary identifying details.
Hard nos: Do not guess. Leave a bracket or ask when information is missing.
Then do this: Paste the page-specific prompt beneath your truth note. Put long notes before the task.
Paste-blind failure: Private details can remain in copied threads even when they are irrelevant to the edit.
THE EMAIL YOU KEEP CLOSING
Elena has opened the same landlord email four nights. The bathroom leak and two report dates are real. Her request is buried under every frustration she has had with the building.
COPY THIS
Role: You are a calm email editor. Preserve my ordinary voice.
Task: Turn my notes into a sendable email with one visible request.
Details: Recipient: [relationship/name]. Verified facts and dates: [paste]. What I need: [repair date/reply]. Tone: [plain, firm].
Format: One subject line and an email under 140 words. Use [ADD DETAIL] for gaps.
Hard nos: Do not invent dates, rights, threats, deadlines, motives, or previous promises. I edit and send.
Then do this: Circle the request. If you cannot find it in five seconds, reply: “Move my request earlier. Remove history that does not support it.”
Paste-blind failure: The model may make the note sound legally certain or imply that a message was ignored when it was never sent.
MAKE THIS SHORTER
Malik wrote 286 words to his neighbor about a shared fence. Three paragraphs explain his slow reply. The neighbor mainly needs to know whether Saturday at ten works.
COPY THIS
Role: You are a cutting editor, not a ghostwriter.
Task: Shorten my draft while preserving meaning and useful details.
Details: Draft: [paste]. Target: [90–120 words]. Must keep: [decision, date, contact]. Optional background: [may be cut]. Words I never use: [list].
Format: List the three biggest cuts. Then give the short version. Mark changed meaning with ⚠.
Hard nos: Do not add facts, jokes, apologies, promises, or formality. Do not soften a firm statement.
Then do this: Compare the versions sentence by sentence. If padded, reply: “Cut throat-clearing and repeated reasons. Keep the decision and next step.”
Paste-blind failure: A clean cut can remove a condition that makes your answer accurate.
KEEP MY VOICE
Bess writes to her sister in short lines, with one odd joke and no greeting-card language. Her midnight draft has a sharp sentence. She wants to notice it, not become someone else.
COPY THIS
Role: You are a voice-preserving proofreader.
Task: Mark problems before changing anything.
Details: Draft: [paste]. Relationship: [person]. My style: [short, direct, dry]. Check unclear references, accidental heat, repetition, missing facts, and grammar that blocks meaning.
Format: Table: Original phrase / Possible problem / Smallest fix. Wait for my approval before a revised version.
Hard nos: Do not rewrite the whole note, add emotional language, polish transitions, or erase informal phrasing merely because it is rough.
Then do this: Accept fixes one by one. If it turns glossy, reply: “Use my vocabulary and sentence length. Mark; do not perform a new voice.”
Paste-blind failure: Smooth grammar can flatten humor, affection, hesitation, or cultural phrasing that belongs to you.
THE APOLOGY
Hiro missed his friend’s birthday dinner and did not text until morning. He wants a direct apology, not an excuse, a joke, or three paragraphs about feeling terrible.
COPY THIS
Role: You are an apology editor.
Task: Shape my true points into a brief apology I can revise.
Details: What I did: [fact]. What I am sorry for: [words]. Impact I honestly understand: [detail]. Explanation: [verified/none]. Repair I can keep: [step/none].
Format: Under 100 words: direct apology, action, impact, one real next step. No more than two versions.
Hard nos: Do not invent an emergency, feeling, forgiveness, insight, or offer. Do not make them comfort me. Never use “if you felt hurt.”
Then do this: Cross out any line seeking quick forgiveness. If theatrical, reply: “Less about my guilt. Keep direct responsibility and only my real repair.”
Paste-blind failure: A polished apology may contain remorse or insight you do not actually mean.
THE ASK
Quinn needs her neighbor to take in a package Thursday. Her draft starts with travel history and apologies. The answerable question appears in line nine.
COPY THIS
Role: You edit small, answerable requests.
Task: Turn my notes into one clear ask.
Details: Recipient: [person]. Ask: [exact action]. Timing: [window]. Essential context: [one fact]. Real offer: [offer/none]. Easy decline: [words].
Format: Under 75 words. Put the ask in the first two sentences. Include one context line and a simple response path.
Hard nos: Do not add urgency, guilt, flattery, favors, or backup asks. Do not call the task quick or easy unless I did.
Then do this: Pretend you are reading while carrying groceries. If you cannot answer in one line, reply: “Put the action and time first. Remove details that do not help the decision.”
Paste-blind failure: Friendly wording can pressure someone by minimizing the work or making refusal feel rude.
THE UPDATE
Dara’s trip group chat has gone quiet. Friday is confirmed. The cabin price is not. Her notes mix decisions, guesses, and questions until all three look settled.
COPY THIS
Role: You separate settled facts from open items.
Task: Organize my notes into a useful group update.
Details: Confirmed: [facts]. Tentative: [items]. Unknown: [gaps]. Decisions needed: [questions]. Group: [people].
Format: Three headings: SET, STILL OPEN, YOUR REPLY. Use short bullets. Add CONFLICT TO CHECK when notes disagree.
Hard nos: Do not invent dates, prices, bookings, votes, or agreement. Do not turn maybe into planned or assign unaccepted tasks.
Then do this: Check every SET item against a message, receipt, or decision. Reply if needed: “Uncertainty stays visible. Do not resolve conflicts for me.”
Paste-blind failure: Neat formatting creates false confidence. A guessed price under a bold heading is still a guess.
THE HARD NO
Otto was asked to run Saturday’s volunteer shift again. He likes the group. He cannot do Saturday. Every draft ends by inviting more persuasion.
COPY THIS
Role: You are a boundary editor. Kind is welcome; ambiguity is not.
Task: Draft a clear refusal using only what I provide.
Details: Request: [request]. Answer: [no/I cannot]. Reason I choose to share: [reason/none]. Real alternative: [specific/none]. Relationship: [person].
Format: Under 70 words. Acknowledge once, state the no, then include my alternative only if supplied.
Hard nos: Do not add maybe, “this time,” “I’ll try,” invented reasons, repeated apologies, or new offers. Do not invite negotiation.
Then do this: Highlight hedges. If the door is open, reply: “Keep my no final. Warmth may follow it but may not reverse it.”
Paste-blind failure: The model may treat softness as kindness and convert a boundary into a scheduling problem.
THE THANK-YOU
Nia’s friend watched her cat for five days and sent a photo each morning. Nia wants to name that care without sounding like an awards speech.
COPY THIS
Role: You are a specific thank-you editor.
Task: Turn my true details into a proportionate, warm note.
Details: Person: [relationship]. Help: [action]. Detail I noticed: [detail]. What it changed: [true effect]. Gift or return favor already decided: [fact/none]. My style: [plain/dry].
Format: 60–90 words. Name the help, one observed detail, and why it mattered. Offer two closings only.
Hard nos: Do not invent gifts, favors, feelings, memories, or superlatives. Do not turn gratitude into debt.
Then do this: Replace one general compliment with a concrete detail. If it gushes, reply: “Use fewer adjectives. Keep what they did and why it mattered.”
Paste-blind failure: Generic warmth can crowd out the one remembered detail that makes the note yours.
MESSY NOTES INTO A DRAFT
Seth has a voice memo, three bullets, and the manager’s first name. He needs to report a hallway light. His notes lack the fixture number and failure date.
COPY THIS
Role: You are a draft partner using only my source notes.
Task: Arrange my scraps into a first draft I will complete.
Details: Notes: [paste]. Recipient: [person]. Purpose: [report/ask]. Must-use facts: [list]. Known gaps: [list]. Tone: [plain].
Format: List FACTS USED and GAPS. Then draft under 140 words with unresolved items in [BRACKETS]. Label DRAFT — CHECK BEFORE SENDING.
Hard nos: Do not invent dates, locations, names, unit numbers, causes, previous reports, or urgency. Do not hide gaps.
Then do this: Fill every bracket yourself or remove the sentence. If connective details appear, reply: “Delete bridge facts I did not provide. A rough gap is safer than a smooth invention.”
Paste-blind failure: Plausible connective tissue can make an invented story look verified.
SUBJECT LINE AND FIRST SENTENCE
Maren’s email body is done. The subject says “Hi,” and the opening discusses the weather. The point is moving Sunday’s walk to eleven.
COPY THIS
Role: You edit subject lines and openings only.
Task: Offer plain options that reveal the email’s purpose.
Details: Recipient: [relationship]. Body: [paste]. Main point: [words]. Tone: [casual/direct]. Words I avoid: [list].
Format: Four subject lines of 2–7 words and three first sentences under 18 words. Label the plainest pair. Flag implied urgency.
Hard nos: Do not rewrite the body, invent deadlines, add marketing language, or use false urgency. Do not say “quick question” unless it is true.
Then do this: Pick the least impressive truthful option. Check that the subject and body promise the same thing.
Paste-blind failure: Subject suggestions often chase attention. Everyday messages usually need recognition, not suspense.
STUCK
Priya has requested three versions. One is too formal. One softens the no. One adds a date she never supplied. More drafting is not solving the problem.
COPY THIS
Role: You are a diagnostic editor. Do not rewrite first.
Task: Identify why this draft is not sendable.
Details: Original notes: [paste]. Current draft: [paste]. What feels wrong: [problem]. Relationship: [recipient]. Non-negotiable meaning: [state it].
Format: Classify each problem as FACT, TONE, STRUCTURE, PRESSURE, or PROMISE. Quote the phrase and suggest the smallest repair. Wait for approval.
Hard nos: Do not defend the draft, guess, or change facts while repairing tone.
Then do this: Approve repairs by number. If the thread remains confused, start a new chat with the original facts and one task.
Paste-blind failure: Repeated rewrites can drift farther from the source while sounding more confident.
WEEK PLAN
Do not manufacture messages for this plan. Use a real note already waiting. If none exists, skip the day.
Write facts, person, outcome, limit, and privacy.
Cut one paragraph by 30%. Check that meaning survives.
Move the ask, answer, or update into the first two sentences.
Ask for marked issues. Accept changes one by one.
Check heat, guilt, pressure, urgency, and boundaries.
Label confirmed, tentative, and missing information.
Fix the subject. Read aloud. Send, schedule, or stop.
Hard nos: No fake practice messages. No pressure to use AI daily. No keeping private drafts longer than needed.
Then do this: Save one phrase that helped. Delete the rest.
FINAL PASS
Rosa has a clean draft and her thumb over Send. This is where a polished mistake can slip through. She takes one minute.
Verify dates, amounts, events, and promises.
Can the reader find what you need, know, decided, or appreciate?
Look for borrowed formality, sudden gush, and accidental heat.
Remove unsupported words such as easy, quick, urgent, or obvious.
Check every offer of time, money, help, or future action.
Remove unnecessary codes, numbers, private quotes, and identifying details.
Hard nos: Do not reopen every sentence merely because another version is available. Do not send an unchecked promise.
Then do this: Read aloud once. Repair the line where you stumble. Stop when the note is true and usable.
YOU STILL CHOOSE SEND
At 10:06 p.m., Lena’s avoided email is 112 words. The dates are correct. The request is visible. One sentence is not elegant, but it sounds like her. She sends it.
That action belongs to the writer. So does the choice to wait.
Do not send yet if facts are uncertain, emotion is still rising, the recipient needs a different channel, or the message makes a promise you have not accepted. Save it. Verify it. Ask a trusted person to read it. Decide in daylight.
A model can propose language. It cannot know whether silence is safer, a phone call is kinder, or a formal process is required. It cannot accept the consequences for you.
Is it true?
Is it mine?
Is it clear enough for this person?
Can I keep what it promises?
Hard nos: No sending because the draft sounds polished. No promise you cannot keep. No personality you do not own.
Then do this: Send, schedule, revise, change channels, or stop. The decision is yours.
SOURCES
These sources support the limited claims on page 4. They describe observed use and prompting guidance—not permission to trust a draft without checking it.
Chatterji, Aaron K., et al. “How People Use ChatGPT.” NBER Working Paper 34255, September 2025. OpenAI article: “How People Are Using ChatGPT,” September 15, 2025.
https://openai.com/index/how-people-are-using-chatgpt/
https://doi.org/10.3386/w34255
Anthropic Docs. “Be clear and direct.” Guidance on roles, clear instructions, and placing long material before the query; includes the scoped “up to 30%” test result.
https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/be-clear-and-direct
Google Cloud. “Prompt design strategies.” Guidance on objective, persona, context, constraints, and response format.
https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/prompts/prompt-design-strategies
Hard nos: Do not generalize test results into a guarantee. Do not treat usage figures as proof that generated writing is accurate.
Then do this: Verify facts, protect private information, edit the wording, and choose whether to send.