Your AI identity and your AI team, portable to every AI platform.
Sign in Get Started
Menu
Build an Agent of Me Explore Styles Professional Agents Community Agents Leaderboard AI News
AI Platforms Directory Model Matrix Compare Which AI should I use? Integration Guides Set up OpenClaw Prompt Fit
Learn & Tools Learn Ask the Data Agent Builder API
About About us Contact Disclaimers
Sign in Get Started
Account
Your AI identity, portable

Create a free account to build your profile. Private by default. Nothing is shared unless you publish it.

Get Started Sign in
Dark mode

🧭 Guided View
New to prompts, system instructions, context windows, tokens? We explain every term as you browse, in plain English. Same pages, with the help built in.

⚡ Expert View
You already know how prompting works. Just the substance, clean and compact, with no extra explanations. This is the default view.

Interface language

The Working Prompter · Section 2/5, Showing Beats Telling

Learning objectives
Tap Next (or use the arrow keys) to move one idea at a time. No timer, the 5-question quiz waits at the end. The ← up top exits any time; progress keeps.

An example is an instruction in disguise

Course 1 said it in passing; this section makes it a tool. An example in a prompt is not an illustration. It is a pattern the model will continue, usually more faithfully than it follows a description. 'Reply like this:' plus one real support reply you loved outperforms three sentences of adjectives about warmth and brevity.

The standard shape is a labeled input → output pair: 'Customer message: … / Our reply: …'. One pair teaches the transformation; the labels teach where the pattern starts and stops. The technique has a name, few-shot prompting but the habit matters more than the name: when you can show it, show it.

One to three good ones beat ten mediocre ones

Examples are potent, and that cuts both ways: the model imitates everything about them, including the flaws you didn't notice. A mediocre example actively teaches mediocrity. Quality beats quantity, one to three strong examples usually cover a task, and past that you are adding weight, not signal.

Choose examples that show the hard part. If your real inputs range from angry customers to billing confusion, don't paste three easy thank-you notes, show the edge you most need handled well. Good examples vary along the same dimension your real inputs vary.

The example IS the format spec

The model treats your example's format as part of the pattern. If the example has a subject line, outputs grow subject lines. If it runs four sentences, expect four-ish sentences. So build the example in exactly the shape you want back, same headers, same length class, same markup.

The trap is instructions that argue with examples. You write 'keep replies under 100 words' and paste a 300-word example; now the rule and the pattern disagree, and outputs drift long or wobble between the two. When you spot that conflict, fix the example. It usually speaks louder than the rule.

Label your counter-examples

Sometimes the fastest way to define good is to show the bad thing you keep getting. That is safe only with labels: 'Not like this: "I sincerely apologize for any inconvenience…", why: it opens on apology instead of the fix.' Unlabeled, a bad example is just another pattern, and the model may continue it.

The strongest setup bounds the target from both sides: one 'Like this' example and one labeled 'Not like this' with the reason it fails. The reason matters. It tells the model which feature of the bad example to avoid, instead of leaving it to guess.

Mini quiz, Showing Beats Telling

5 questions, drawn fresh from the bank every attempt. Pass mark 60%. Unlimited retakes.

Next section: Structure at Scale →
Read the full lesson text

1. An example is an instruction in disguise

Course 1 said it in passing; this section makes it a tool. An example in a prompt is not an illustration. It is a pattern the model will continue, usually more faithfully than it follows a description. 'Reply like this:' plus one real support reply you loved outperforms three sentences of adjectives about warmth and brevity.

The standard shape is a labeled input → output pair: 'Customer message: … / Our reply: …'. One pair teaches the transformation; the labels teach where the pattern starts and stops. The technique has a name, few-shot prompting but the habit matters more than the name: when you can show it, show it.

2. One to three good ones beat ten mediocre ones

Examples are potent, and that cuts both ways: the model imitates everything about them, including the flaws you didn't notice. A mediocre example actively teaches mediocrity. Quality beats quantity, one to three strong examples usually cover a task, and past that you are adding weight, not signal.

Choose examples that show the hard part. If your real inputs range from angry customers to billing confusion, don't paste three easy thank-you notes, show the edge you most need handled well. Good examples vary along the same dimension your real inputs vary.

3. The example IS the format spec

The model treats your example's format as part of the pattern. If the example has a subject line, outputs grow subject lines. If it runs four sentences, expect four-ish sentences. So build the example in exactly the shape you want back, same headers, same length class, same markup.

The trap is instructions that argue with examples. You write 'keep replies under 100 words' and paste a 300-word example; now the rule and the pattern disagree, and outputs drift long or wobble between the two. When you spot that conflict, fix the example. It usually speaks louder than the rule.

4. Label your counter-examples

Sometimes the fastest way to define good is to show the bad thing you keep getting. That is safe only with labels: 'Not like this: "I sincerely apologize for any inconvenience…", why: it opens on apology instead of the fix.' Unlabeled, a bad example is just another pattern, and the model may continue it.

The strongest setup bounds the target from both sides: one 'Like this' example and one labeled 'Not like this' with the reason it fails. The reason matters. It tells the model which feature of the bad example to avoid, instead of leaving it to guess.

Business

Business AnalystChief of StaffExecutive AssistantM&A AnalystManagement ConsultantOperations AnalystProject ManagerRecruiter

Finance

AccountantDue Diligence AnalystEquity Research AnalystFamily Office AnalystFinancial AnalystFixed Income AnalystInvestment Banking AnalystPortfolio Analyst

Legal

Contract Review AssistantLegal Due Diligence AssistantLegal Research AssistantParalegal

Marketing

Brand StrategistContent StrategistGEO AnalystMarketing StrategistSEO AnalystSales Strategist

Personal

Career CoachLearning TutorReflection AssistantResearch AssistantTravel PlannerWriting Assistant

Real Estate

Acquisition AnalystAsset Management AnalystCommercial Real Estate AnalystDevelopment AnalystLease AnalystProperty Financial Analyst

Research

Competitive Intelligence AnalystDeep Research AnalystIndustry Research AnalystJournalist ResearcherMarket Research AnalystMedical Research Assistant

Technology

AI Strategy AdvisorCybersecurity Research AssistantData AnalystProduct ManagerSoftware Engineer