Format Library — Copy-Paste by Task

Slogan: "Don't write prompts from scratch. Steal from your future self."

📧 Cold email

ROLE: You are a senior B2B copywriter.
CONTEXT: I run [NAX, a web agency in KL]. I'm reaching out to [CFO of a 50-person SaaS].
GOAL: Book a 15-min call to discuss [reducing their AWS bill via a code audit].
RULES:
- Under 90 words.
- No "hope this finds you well."
- One specific reason I'm reaching out to *them*.
- End with a single yes/no question.
INPUT: [paste their LinkedIn bio or website here]

🐦 Social post (LinkedIn / X)

ROLE: You are a Twitter writer in the style of [@naval / @paulg / @shaan_puri].
TASK: Write 3 versions of a post about [topic].
RULES:
- Hook in first line (curiosity, contrarian, story).
- Max 280 chars for X / 220 words for LinkedIn.
- No hashtags, no emojis unless I say so.
- End with a line that earns a reply.

📄 Summarize a document

ROLE: You are a research analyst.
INPUT: [paste document or attach file]
OUTPUT:
1. One-sentence TL;DR.
2. 5 key takeaways as bullets.
3. 3 surprising or counter-intuitive points.
4. 2 questions this doc *doesn't* answer.

🧱 Write code

ROLE: You are a senior TypeScript engineer.
CONTEXT: [Stack: React + TanStack Router + Tailwind. Project conventions: …]
TASK: [Build a component that does X.]
CONSTRAINTS:
- Strictly typed (no any).
- Accessible (keyboard + screen reader).
- Match the design tokens in styles.css.
- Include a usage example.
OUTPUT: Full file ready to paste.

🐞 Debug code

ROLE: You are a senior debugger.
SYMPTOM: [What's happening.]
EXPECTED: [What should happen.]
CODE: [paste relevant file(s)]
ERROR: [paste exact error]
TASK:
1. Most likely root cause.
2. 2-3 alternate causes.
3. The minimal patch to fix it.

🔎 Research brief

ROLE: You are a McKinsey associate.
TOPIC: [the topic]
AUDIENCE: [my CEO / my own learning / a client]
OUTPUT:
- Executive summary (3 sentences).
- Market size + growth rate (with sources).
- 3 incumbents + 3 challengers.
- 2 risks, 2 opportunities.
- "What to do this quarter" — 3 bullets.

🎙 Interview question generator

ROLE: You are a hiring manager at a top startup.
INPUT: [paste JD]
TASK: Generate 8 interview questions:
- 2 behavioral (STAR method).
- 3 role-specific technical.
- 2 culture/values.
- 1 trick question that reveals seniority.
For each: include a 1-line "what a great answer sounds like."

🧠 Decision framework

ROLE: You are my thinking partner.
DECISION: [the decision I'm trying to make]
CONSTRAINTS: [budget, time, risk tolerance]
TASK:
1. List the 3 highest-leverage options.
2. For each: 2 pros, 2 cons, 1 reversible-vs-irreversible note.
3. Recommend one — and tell me what would change your mind.

🪛 Lovable mega-prompt

GOAL: Build [a habit tracker MVP].
USERS: [solo users who want simple streaks].
SCREENS:
- Landing: hero + 1 CTA "Try it free".
- App: list of habits, add habit, click to mark today done, show streak.
STACK: TanStack Start + Lovable Cloud.
DATA: habits (id, user_id, name, created_at). checkins (id, habit_id, date).
SECURITY: RLS — users only see their own rows.
STYLE: Calm, Notion-like, monochrome with one accent green.
DON'T: No animations, no marketing pages beyond the landing.

Pro tip: Build a folder in Notion / Apple Notes called "Prompts I'd Pay For." Add one a week. In a year you'll have a moat.

Learning objectives

By the end of this lesson you should be able to:

• Explain the core idea of Format Library in your own words to a non-technical friend.
• Recognise where this concept shows up in real projects and tools you already use.
• Apply at least one specific technique from this lesson to something you're building this week.

Practical exercise (10–15 min)

1. Open a new note (Notion, Apple Notes, whatever) titled "Lesson 9.3 — my notes".
2. Write 3 sentences answering: "If I had to teach this lesson to myself yesterday, what are the 3 things I'd absolutely say?"
3. Now do the smallest possible version of it — one prompt, one file, one setting change — and paste the result into your note.
4. Add one honest sentence: "Where I got stuck / what surprised me."

Ship the note to yourself. That's the loop we'll repeat every lesson.

Estimated time

• Reading: ~10 min
• Exercise: ~10–15 min
• Total: ~24 min

Remember: Reading is not learning. The exercise is where the neurons actually wire up.

Deep dive — the long version

You already have the short version above. This section is the hour-long, sit-down version — the kind of walkthrough you'd get from a mentor over coffee. Skim it the first time, then come back and read it slowly once you've done the exercise. That's where the real learning happens.

1. Why this lesson exists at all

Format Library — Copy-Paste by Task is one of those topics that seems obvious after you know it and completely opaque before. Almost every learner we've watched trip on this ends up tripping in the same 3 places:

1. They memorise the vocabulary but not the mechanics. They can say the word, but if you ask them to draw what's happening, they freeze.
2. They jump to tools too fast. They pick a framework or an AI product before they understand what problem it actually solves.
3. They confuse "reading" with "learning". Reading gives you recognition. Doing gives you recall. Only recall counts when you're building.

The point of this deep dive is to hit all three of those failure modes head-on, in slow motion, with plenty of examples.

2. A story to anchor the idea

Imagine you're teaching a curious 10-year-old about format library — copy-paste by task. They don't care about your credentials. They just want a picture in their head that makes sense. Here's the story we'd tell them:

A long time ago, before phones and Wi-Fi, if you wanted to know something you had to walk to the library and ask a librarian. The librarian would find a card in a little wooden drawer, walk to a shelf, pull down a book, and hand it to you. You'd sit at a desk and read it.

>

Everything in this lesson is that same story — just with the librarian replaced by a computer, the shelf replaced by a hard drive, and the walk replaced by the internet.

That story is the mental scaffold. Every technical detail you'll learn from here onwards hangs off it.

3. The mechanics, one step at a time

Let's slow the whole thing down. Pretend we're watching a replay in slow motion.

Step 1 — The request. Something (a person, a script, another computer) says "I would like this thing." In a browser, that's typing a URL. In an AI app, that's typing a prompt. In a bank app, that's tapping a button.

Step 2 — The middleman. A layer of software takes the request, tidies it up, and forwards it. In a browser this is called the network stack. In an AI app it's an API client. You almost never see this middleman, but it's always there.

Step 3 — The doer. A computer far away receives the request, does some work (looks something up, generates something, calculates something), and produces a result.

Step 4 — The reply. The result travels back the same way it came. Middleman receives it, tidies it, hands it to whoever asked.

Step 5 — The rendering. Whatever asked for it now shows the result on a screen, plays a sound, or takes an action.

That five-step loop is literally every interaction on every website, every app, every AI tool. Once you can spot the five steps, nothing in tech is truly mysterious again — it's just variations on the loop.

4. Three worked examples (from easy to less easy)

Example A — Reading a news article. Steps: click a link (request) → your browser asks a server (middleman) → the server sends back HTML (doer + reply) → the browser paints text on your screen (rendering).

Example B — Asking ChatGPT for a limerick. Steps: type the prompt (request) → the ChatGPT client bundles it with your session token (middleman) → OpenAI's servers run the model (doer) → text tokens stream back (reply) → the client paints them one word at a time (rendering).

Example C — Ordering food on an app. Steps: tap "order" (request) → the app opens an authenticated connection (middleman) → the restaurant's system receives the order and prints a ticket (doer) → a confirmation comes back (reply) → the app shows "Order placed" and starts a progress bar (rendering).

Different domains, exact same loop. This is why one skill (understanding requests and responses) transfers everywhere.

5. Common mistakes and how to avoid them

• Mistake 1: Skipping the exercise. Reading feels productive but the neurons only wire up when you produce something. Do the exercise. It's 10 minutes.
• Mistake 2: Learning the buzzword first. "What's LLM? What's RAG? What's SSR?" You don't need those words yet. Master the 5-step loop first, then the buzzwords slot in.
• Mistake 3: Comparing yourself to people 2 years ahead. They started too. They also felt lost. The only useful comparison is you today vs you last week.
• Mistake 4: Watching tutorials as entertainment. Tutorials are training wheels, not the destination. If you're not typing along, you're watching TV.
• Mistake 5: Believing "AI will just do it". AI is a very fast intern with amnesia. If you can't describe what you want in plain sentences, no model on earth will get you to a good result.

6. A checklist you can actually use

Before you leave this lesson, tick these off honestly:

• [ ] I can explain format library — copy-paste by task in 3 sentences without notes.
• [ ] I can point at something in real life that uses this idea.
• [ ] I finished the practical exercise, not just read it.
• [ ] I wrote 1 question I still don't know the answer to.
• [ ] I know which lesson comes next (see the "Next up" card at the bottom of the page).

If any of those are unticked, don't move on. Loop back and close them. The learners who ship are the ones who don't skip.

7. Where this lesson connects

Every future chapter will assume you internalised this idea. Specifically:

• *When we talk about prompts*** — a prompt is a request in step 1.
• *When we talk about tools*** — a tool is a specialised doer in step 3.
• *When we talk about building your own product*** — you're going to design your own version of the loop, end to end.

That's why we made you sit through the story. Everything else in the handbook is a variation on it.

8. Bonus: three questions to journal on

If you want to really lock this in, spend 5 minutes writing (not typing — actually writing) answers to these:

1. What part of format library — copy-paste by task was I secretly avoiding thinking about?
2. If I had to teach this to my past self one year ago, what would I say first?
3. What is the smallest possible project I could build this week that uses this idea?

Those three prompts, repeated across every lesson in the handbook, are the single highest-leverage habit we've seen in learners who go from zero to shipping in under 6 months.

Next up

If this lesson clicked, keep the momentum going — hit the Next → card at the bottom of this page. If you struggled, do this instead:

1. Re-read sections 3 and 5 slowly.
2. Redo the practical exercise from scratch.
3. Re-read your notes again in 24 hours. Sleep genuinely helps memory consolidate — it's not folk wisdom, it's biology.

Progress is not a straight line. Circling back is how mastery is built.