← Back to Dictionary

Stone

Podcast 1 · Introduction

Stone /stəʊn/ · noun / verb / adjective

A short documentary narration — meaning, origin, and how the word is used.

In this course, stone means small piece of rock, or the hard material. The introduction ties that sense to pebble. See the Cambridge English entry and the Merriam-Webster entry. Encyclopedic background is in Stone.

Ready
Podcast 2 · Daily Use

In Conversation

Two British speakers using "stone" naturally in everyday talk.

Ready
Podcast 3 · Prompt Engineering

Prompting with "stone"

An instructor and developer explore real, copy-ready AI prompts built around the word.

Ready
1 / 3

Transcript: “Stone” vocabulary micro-course

Read along with the three podcasts, or open the full dictionary entry for Stone for the definition, Arabic meaning, synonyms and example sentences.

Podcast 1 — Introduction & meaning

Narrator: Today's word is "stone" — a noun, verb, and adjective, pronounced /stəʊn/, rhyming with "bone".

Narrator: A stone is a small piece of rock, or the hard material rock itself, used for building and countless other things.

Narrator: In plain English, a stone is a bit of rock — from a tiny pebble to the great blocks of a castle wall.

Narrator: It has many senses: a gem, the hard seed in a fruit, a British unit of weight, and a verb meaning to throw stones.

Narrator: The word comes from the Old English "stān", one of the oldest and most basic words in the language.

Narrator: From that ancient root it spread into building, jewellery, medicine, weight, and a wealth of vivid idioms.

Narrator: Think of "a heart of stone", "set in stone", or "leave no stone unturned" — the word is everywhere.

Narrator: In tone it is plain, solid, and ancient — concrete and dependable, like the material itself.

Narrator: So remember: a stone is a piece of rock — solid, lasting, and woven deep into our oldest expressions.

Read podcasts 2 and 3

Podcast 2 — In conversation

Speaker A: I skimmed a flat stone across the lake — it bounced four times!

Speaker B: Nice! "Stone" is such a versatile word. A pebble, a gem, even a weight.

Speaker A: Exactly. I've lost half a stone since I started running, actually.

Speaker B: Ah, the British weight sense — fourteen pounds to a stone.

Speaker A: Right. And watch out for the stone in a peach — nearly chipped a tooth.

Speaker B: Ha, the fruit sense. Americans would say "pit" there, wouldn't they?

Speaker A: They would. People sometimes confuse "stone" and "rock" — but a stone is smaller, a piece you can hold.

Speaker B: Good distinction. A rock is bigger, often part of the landscape.

Speaker A: And the idioms — "set in stone" means fixed and final.

Speaker B: Lovely. Close synonyms? "Pebble", "rock", and "gem" depending on the sense.

Speaker A: So nothing's set in stone yet — we can still change the plan.

Speaker B: Good, because I've a better idea entirely.

Podcast 3 — Prompt engineering

Speaker B: Let's use "stone" in AI prompts to mean solid, permanent, unchangeable things — fixed rules and stable foundations.

Speaker A: So "set in stone" tells the AI something must not change?

Speaker B: Exactly. For locking rules, you'd write:

Prompt: These business rules are set in stone: a refund is only allowed within thirty days. Build the checkout so this rule can never be bypassed, no matter which path the user takes.

Speaker B: The phrase "set in stone" makes the model treat the rule as fixed and final.

Speaker A: Memorable. What about a stable design system?

Speaker B: Try this:

Prompt: Make my colour palette a stone foundation: three core colours that never change across the whole app. Build every component on top of these, so the brand stays rock-solid and consistent.

Speaker A: So it's an unshakeable base. What about a database?

Speaker B: Here you go:

Prompt: Set my primary keys in stone: once an ID is assigned to a record, it must never change. Design the schema so IDs are permanent and every relation depends safely on them.

Speaker A: Solid. What about a thorough search?

Speaker B: Try this one:

Prompt: Leave no stone unturned when finding why my app crashes on startup: check the config, the imports, the database connection, and the logs, and report every possible cause you find.

Speaker A: Could it freeze an API contract too?

Speaker B: Yes:

Prompt: Treat my public API as set in stone: never rename or remove existing fields. Only add new optional ones, so older apps that depend on it keep working without a single break.

Speaker A: So "stone" means solid, permanent, unchangeable.

Speaker B: Exactly — a rock-solid word for fixed rules and stable foundations.