Free to read · no account needed

20 min · prompt

Copy-paste prompt packs (writing · study · job · office)

Goal: Fill a pack with your facts and boundaries; empty packs are souvenirs, not tools.

Best for: Absolute beginners who want fill-in prompts, not theory. Works in ChatGPT, Claude, or Grok.

When you need results tonight, packs beat theory. Copy a filled pattern, swap your facts, keep the Boundaries that stop inventions.

Why beginners skip this

Copy-pasting a whole pack without swapping names and dates feels easy—you ship someone else’s scene. Replace placeholders first.

How to use these packs

Each pack is five fill-in prompts. Replace the [brackets]. Keep the Boundaries line—that is what stops the model from inventing dates, quotes, or praise you did not earn.

Jargon: a prompt is just the message you send the chat. You do not need a special “roleplay” opener for routine work. If a pack fails, open a new chat and shorten the ask—one job per message.

  • Paste → fill brackets → send.
  • Treat the first reply as a draft. Say “shorter”, “warmer”, or “Leave with four small packs you can paste”
  • Never paste passwords, keys, or other people’s private data (see What never to paste).

Pack A — Writing (emails, posts, outlines)

Use when the text must sound like you, not like a brochure. Freeze facts first; polish second.

A1 — Reply email
Goal: Reply so the reader knows the decision and the next step.
Context: [one-sentence situation]
Audience: [peer / manager / client]
Format: subject ≤7 words; body ≤120 words; one clear ask.
Boundaries: Do not invent dates, owners, or promises. Mark guesses [?].
Draft: ---
[paste]
---

A2 — Make this less stiff
Goal: Rewrite for a human who is busy and respectful.
Keep: [facts that must stay]
Tone: plain, warm, no flattery, no “Leave with four small packs you can paste”
Format: same length or shorter.
Boundaries: Do not add new commitments.

A3 — Outline before prose
Goal: Turn this topic into a usable outline.
Topic: [topic]
Audience: [who]
Format: H2 titles only, 5–7 sections, one bullet of purpose under each.
Boundaries: No full paragraphs yet. Ask me 3 clarifying questions first if the topic is vague.

A4 — Social / short post
Goal: Draft a post I can edit in 5 minutes.
Topic: [one idea]
Format: ≤120 words; 1 hook line; 1 concrete detail I must fill as [DETAIL]; no hashtag spam.
Boundaries: Do not invent metrics or customer quotes.

A5 — Cut AI sludge
Goal: Remove generic filler from this draft while keeping my meaning.
Format: return (1) cleaned draft (2) list of phrases you deleted and why.
Boundaries: Do not invent a “better” story. Keep my facts.
Example

Filled prompt

Goal: Reply so the reader knows the decision and the next step.
Context: We are delaying the Friday demo by one week; design needs the API freeze date.
Audience: product manager I work with weekly
Format: subject ≤7 words; body ≤120 words; one clear ask.
Boundaries: Do not invent dates, owners, or promises. Mark guesses [?].
Draft: ---
Hey — demo might slip. Can we talk?
---

What good output looks like

  • Subject names the decision, not “Quick question”
  • One ask (e.g. confirm freeze date) — no new fake deadlines
  • Tone matches a weekly peer, not a press release

Second worked example — Pack A3 (outline before prose).

Example

Filled prompt

Goal: Turn this topic into a usable outline.
Topic: Internal FAQ for our refund policy change next month
Audience: support agents (busy, skim)
Format: H2 titles only, 5–7 sections, one bullet of purpose under each.
Boundaries: No full paragraphs yet. Ask me 3 clarifying questions first if the topic is vague.

What good output looks like

  • Model asks clarifying Qs before inventing policy details
  • H2s map to agent jobs (when / how / exceptions)
  • No fake legal paragraphs yet

Pack B — Study (explain · quiz · plan)

Honesty rule: use these to understand and practice—not to submit AI text as your own graded work. If your school forbids AI for an assignment, follow the policy.

B1 — Explain simply
Goal: Explain [concept] to a beginner in my field: [field].
Format: (1) plain paragraph ≤120 words (2) one analogy (3) 3 terms defined in one line each.
Boundaries: If you are unsure, say so. Do not invent citations.

B2 — Check my understanding
Goal: I will explain [topic] in my own words. Quiz me with 5 questions that catch gaps. Wait for my answers before revealing solutions.
My explanation: ---
[paste]
---

B3 — Wrong → why
Goal: Here is my answer to [question]. Tell me what is wrong or incomplete, then give a corrected version and a one-line rule I should remember.
My answer: ---
[paste]
---

B4 — Weekly study plan
Goal: Build a 5-day plan for [exam/topic], about [N] minutes per day.
Format: table Day | Focus | Practice task | How I know I am done.
Boundaries: Prefer active recall over “Leave with four small packs you can paste” Do not invent reading lists I did not provide—ask me what materials I have.

B5 — Flash prompts from notes
Goal: From my notes, make 10 Q&A flashcards.
Format: Q | A | Hint (optional). Max 2 sentences per answer.
Boundaries: Only use facts present in the notes. Mark thin spots [?].
Notes: ---
[paste]
---
Example

Filled prompt

Goal: Explain “gradient descent” to a beginner in my field: product analytics.
Format: (1) plain paragraph ≤120 words (2) one analogy (3) 3 terms defined in one line each.
Boundaries: If you are unsure, say so. Do not invent citations.

What good output looks like

  • Analogy fits analytics (e.g. walking downhill on an error surface), not random sci-fi
  • Terms like learning rate defined without fake paper names
  • No fake “According to a 2019 Nature study…”

Second worked example — Pack B2 (quiz that waits).

Example

Filled prompt

Goal: I will explain “what is an API” in my own words. Quiz me with 5 questions that catch gaps. Wait for my answers before revealing solutions.
My explanation: “It’s like a waiter between apps so they can order data without entering the kitchen.”

What good output looks like

  • Matches named constraints for “Leave with four small packs you can paste today—th”
  • Unknowns labeled; no invented facts
  • Stops before irreversible actions
  • Pass/fail markable in ≤60s (prompts-copy-paste-packs #1)

Pack C — Job search (never invent experience)

Hard rule: the model may rearrange and clarify what you did. It must not invent employers, titles, metrics, or skills. If a number is missing, write [METRIC] and fill it yourself from real records.

C1 — Match resume bullets to a JD
Goal: Rewrite my bullets to mirror the job description’s language—without adding experience I did not list.
Job description (key lines): ---
[paste]
---
My bullets: ---
[paste]
---
Format: table Old bullet | Rewritten | JD phrase reused | New claims? (must be No)
Boundaries: If something is not in my bullets, leave it out or mark [NEED EVIDENCE].

C2 — Cover letter skeleton
Goal: Draft a 3-paragraph cover letter from evidence only.
Role: [title] at [company]
Why them: [2 facts I researched myself]
Why me: [3 proof points from my resume only]
Format: ≤250 words; no “I am passionate about…” fluff.
Boundaries: Do not invent awards, metrics, or mutual contacts.

C3 — Interview story (STAR)
Goal: Turn this experience into a STAR answer (Situation, Task, Action, Result).
Experience notes: ---
[paste]
---
Format: 4 short labeled paragraphs; Result must use only numbers I provided or [METRIC].
Boundaries: No heroic embellishment.

C4 — Practice question + feedback
Goal: Ask me one common interview question for [role]. Wait for my answer. Then score Clarity / Evidence / Length (1–5) and suggest one tighter opening line.
Boundaries: Do not invent a better career history for me.

C5 — Red-flag scan
Goal: Scan my resume/letter for unverifiable claims, vague verbs, and AI-sounding buzzwords.
Format: list Issue | Why it is risky | Safer rewrite direction.
Boundaries: Prefer honest smaller claims over impressive fake ones.
Example

Filled prompt

Goal: Rewrite my bullets to mirror the JD—without adding experience.
JD key lines: “SQL dashboards; stakeholder updates; A/B test support”
My bullets: “Built weekly Looker views for growth; sent Friday notes to PM; helped analysts set up experiment sheets”
Format: Old | Rewritten | JD phrase | New claims? (No)
Boundaries: No new employers or metrics.

What good output looks like

  • Maps Looker → dashboards without claiming “owned all SQL”
  • Every New claims? cell is No
  • Leaves [METRIC] blank rather than inventing +40%

Worked refusal (Pack C): when the model invents a metric, paste this immediately.

Example

Filled prompt

Stop. The “+40% conversion” was not in my bullets.
Rewrite the table. New claims? must stay No.
Use [METRIC] for gaps. Do not fill gaps.

What good output looks like

  • Unknowns labeled; no invented facts
  • Stops before irreversible actions
  • Pass/fail markable in ≤60s (prompts-copy-paste-packs #2)
  • Matches named constraints for “Leave with four small packs you can paste today—th”

Pack D — Office weeklies (email · notes · update)

Pair with deeper pages: email polish, meeting notes → actions, stakeholder update. This pack is the Monday–Friday starter kit.

D1 — Meeting → actions
Goal: From these notes, list decisions, actions, and open questions.
Format: ## Decisions (only if explicit) ## Actions (owner + date or TBD) ## Open questions ## Unclear
Boundaries: Do not invent owners or deadlines.
Notes: ---
[paste]
---

D2 — Weekly status
Goal: Write a skimable update for [manager/client].
Format: Status color (Green/Yellow/Red) + 3 wins + 3 risks + 3 asks. ≤150 words.
Boundaries: No fluff openers. Numbers only if I provided them.

D3 — Chase without nagging
Goal: Follow up on [open item] after [N] days.
Tone: polite, direct, one ask.
Format: ≤80 words; subject line included.
Boundaries: Do not invent urgency that is not real.

D4 — Agenda builder
Goal: Turn this goal into a 30-minute meeting agenda.
Goal: [outcome]
Format: 5 timed rows | Owner | Decision needed? (Y/N)
Boundaries: Leave buffer; do not pack 12 topics.

D5 — Clarify a fuzzy ask
Goal: Turn this vague request into 5 clarifying questions I can send back.
Request: ---
[paste]
---
Format: numbered questions; each one answerable in one sentence.
Boundaries: Do not start doing the work until I answer.
Example

Filled prompt

Goal: From these notes, list decisions, actions, open questions.
Notes: “Ship slipped; Maya will confirm Friday; budget approved for two contractors; docs owner unclear.”
Boundaries: Do not invent owners or deadlines.

What good output looks like

  • Budget approval listed under Decisions
  • Maya’s Friday confirm is Action with real owner—not a fake hard date invented for docs
  • Docs stays under Open questions / Unclear

Second worked example — Pack D3 (chase without nagging).

Example

Filled prompt

Goal: Follow up on the API freeze date after 4 days.
Tone: polite, direct, one ask.
Format: ≤80 words; subject line included.
Boundaries: Do not invent urgency that is not real.
Context: Last mail asked Maya for Friday confirm; today is Tuesday; freeze still TBD.

What good output looks like

  • Stops before irreversible actions
  • Matches named constraints for “Leave with four small packs you can paste today—th”
  • Pass/fail markable in ≤60s (prompts-copy-paste-packs #3)
  • Unknowns labeled; no invented facts

Fill brackets tonight

An empty pack in bookmarks helps nobody. Fill one pack with real facts before sleep.

Red flag

Empty souvenir packs; facts never filled—fill one slot before calling it a tool.

Save this card

Card: An empty pack is a souvenir; a pack filled with your facts and boundaries is a tool. Keep this beside the tool; read before you start.

Before you start

Bring one live artifact for “Leave with four small packs you can paste.” Write Done in one line before you open the model. Guide: prompts-copy-paste-packs. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week pull one prompt from the pack, swap names/dates/scene for today’s real material, then run; no send with placeholders left.

Pitfalls

PitfallBetter
Pasting a pack with brackets still emptyFill every [ ] or the model will invent filler
Five tasks in one pasteOne prompt → one job; follow up in the same chat
Deleting the Boundaries line to “save time”Keep it—especially for jobs, school, and numbers
Using Pack C to invent a stronger resumeStop; rewrite only evidence you can defend in interview

Practice now

Tonight pull one prompt from the pack, swap names/dates/scene for today’s real material, then run.

Close the loop

Write one line: next time I send with placeholders left, I refuse.

One sentence takeaway

Replace name/date/scene placeholders first; then run and send.

Next

GFB · Everyday · Email · Resume

← Back to home · Learn · Tools · Compare · Start