Summary  
This chapter explains how to structure prompts using four key parts—Role, Context, Task, and Format—to target a user’s specific knowledge gap and get more useful, concise responses.

General domain of usage  
Prompt engineering for large language models

## Why your prompts underperform

Compare two prompts about the same thing.

**Weak:**

```text
Explain closures in JavaScript.
```

You get a competent, generic, textbook answer. It's aimed at nobody. You'll read it,
nod, and forget it.

**Strong:**

```text
Role: Act as a patient JS mentor reviewing with a junior dev.
Context: I've written functions and callbacks for 3 months. I understand scope
and hoisting. I do NOT understand why a closure "remembers" a variable after the
outer function has returned — that part feels like magic.
Task: Explain specifically the mechanism that makes the variable survive. Use one
minimal 6-line example, then show me the same code failing without the closure.
Format: Two labelled code blocks, then 3 bullets max. No intro paragraph.
```

Same topic. Completely different value. The second one attacks *your* actual gap.


**RCTF**
A four-part structure for any learning prompt: 
- **R**ole (who Claude should be);

- **C**ontext (where you are and where you're stuck); 
- **T**ask (the precise operation);

- **F**ormat (the shape of the answer). Not a rule — a checklist. Its value is that a disappointing answer can almost always be traced to one missing part.


Definition

## The four parts

### Role
Who should Claude be? This sets vocabulary, patience level and assumed shared context.

`Act as a senior data engineer` · `Act as a tutor for a complete beginner` ·
`Act as a strict code reviewer`

### Context — *this is the one you're skipping*
What do you already know, and where exactly does it stop?

Include three things:
1. Your level (`3 months of Python`, `I've never used a terminal`)
2. What you already understand (so it doesn't re-explain it)
3. **The precise point of confusion** 

the part `I don't get is why X, not how X`

Point 3 is worth more than the rest of the prompt combined.



### Task
The verb. Be specific about the operation you want.

>`Explain the mechanism`
 beats `tell me about`. 

>`Compare X and Y on 3 axes` beats
`what's the difference`.

>`Give me 5 practice problems, hardest last` beats `help me
practice`.

### Format
The shape you can actually use. Unspecified format means Claude guesses, and it
usually guesses "essay" — the least useful shape for studying.



## The 15-second version

If you're in a hurry, at minimum say:

```text
I know [X]. I'm stuck on [Y specifically]. Explain [Y] as [format].
```

That's Context + Task + Format. It takes fifteen seconds and it doubles the quality
of what comes back.

## Reusable template

```text
Role: Act as [persona].
Context: I'm at [level]. I already understand [known]. I'm stuck specifically on [gap].
Task: [precise verb + object].
Format: [shape, length, what to omit].
```

Master the skills needed to turn any lecture, PDF, or course into knowledge that
survives the week. You will build prompts that explain at your level, retrieval
loops that quiz you instead of lecturing you, flashcards that test recall, and a
verification habit that catches confident mistakes. Every technique runs on
material you already have to study, so by the end you have a weekly system
instead of a pile of chat history.

Four-part Learning Prompt

Why your prompts underperform

The four parts

Role

Context — this is the one you're skipping

Task

Format

The 15-second version

Reusable template