Lesson 18 of 32 · Part One, the principles
The Principle of Controlled Imagination
Creative work needs two things at once. The spark is the invitation to invent - write a story, design a poster, build a role-play. The fence is everything you settle in advance: who the character is, where it happens, how long it runs, what tone it keeps, what must be true at the end. Without the fence the machine wanders off somewhere irrelevant; without the spark it merely rearranges what you already told it. Give it both and you get something you did not expect, in the shape you actually needed.
How to use The Principle of Controlled Imagination in Claude
Separate the two halves in the prompt itself: a tag for the fence, holding everything that is settled, and a tag for the spark, holding the one thing you are inviting it to invent. It keeps a fence unusually well, which is the point of doing it this way - and it will tell you when two of your rules fight each other, if you ask it to. The story itself goes in an Artifact so you refine the same text instead of accumulating drafts. On pictures, be clear about the limit: it does not make images, but it writes a precise image brief - composition, light, colours, the space left for text - that you paste into a tool that does, and it is good at checking that brief against your fence. A fence you use nightly belongs in a Project's instructions.
- One tag for the fence, one for the spark - keep them apart.
- Ask it where two of your rules contradict each other.
- Ask what it rejected as too strange; that is often the good one.
From GenAI for Everyone: Prompt Engineering Handbook, First Edition 2025, by Raja Rajeshwari Seshadri and Shreeram Iyer.
Separate the two halves in the prompt itself: a tag for the fence, holding everything that is settled, and a tag for the spark, holding the one thing you are inviting it to invent. It keeps a fence unusually well, which is the point of doing it this way - and it will tell you when two of your rules fight each other, if you ask it to. The story itself goes in an Artifact so you refine the same text instead of accumulating drafts. On pictures, be clear about the limit: it does not make images, but it writes a precise image brief - composition, light, colours, the space left for text - that you paste into a tool that does, and it is good at checking that brief against your fence. A fence you use nightly belongs in a Project's instructions.
From the book Write your creative fence once in a Project's instructions - characters, tone and length - and every new story in that Project will follow it. Claude can also write a detailed image description for you to use in an image tool.
- One tag for the fence, one for the spark - keep them apart.
- Ask it where two of your rules contradict each other.
- Ask what it rejected as too strange; that is often the good one.
- Forbid the closing moral by name - it adds one otherwise.
- No images: have it write the brief, paste that into an image tool.
Instead of
Write a bedtime story for a 6-year-old.
Claude version
<fence> Listener: my granddaughter, six years old, at bedtime. Character: Gowri, a small elephant calf who is afraid of the dark. Place: a forest beside the Kaveri, during Dasara. What she learns: that the night has lights of its own - fireflies, stars, the festival lamps. Voice: a grandmother telling it aloud. Short sentences. Unhurried. Forbidden: villains, anyone getting lost, anything frightening, and any moral at the end. No sentence that explains what the story was about. Length: about 400 words. Ending: Gowri falls asleep. </fence> <spark> One funny moment in the middle that I have not asked for and would not have thought of. Invent it freely. Do not explain it, do not signpost it. </spark> <task> First, in two lines: does anything in my fence pull against anything else - the length against the festival, the gentleness against the fear of the dark? Say so now rather than quietly solving it. Then write the story as an Artifact. Then, outside the Artifact: the word count, and the funnier version of the funny moment that you decided was too strange to use. I would like to see what you protected me from. </task>
Then loop it
- Your discarded version was better. Put it in - the monkey and the stolen laddoo - and edit the Artifact rather than writing a new one. It is also 300 words over; cut from the opening and leave the ending alone.
- Now a second Artifact with the Kannada version, and below it a plain English read-back, so I can check the funny moment survived the translation.
- Rewrite my prompt with the fence intact and the character, place and festival left blank, so I can save it in a Project called "Bedtime stories". Then suggest three more adventures for Gowri.
Why it worksThe spark - "surprise me with one funny moment" - sits inside a firm fence of character, setting, goal, length and tone.
Instead of
Make a cool poster for my folk music show.
Claude version
<the_limit> You cannot make images. I know. So write me the brief, precisely enough that I can paste it into an image tool and get what we agreed, and then check the brief against my fence yourself. </the_limit> <fence> Purpose: a concert poster for a Rajasthani folk music group from Barmer. Scene: four musicians seated on a sand dune at sunset, playing kamaicha, dholak, khartal and morchang. Accuracy: each instrument must be described well enough that an image tool renders it recognisably - how it is held, its size against the body, what it is made of. Describe them as a player would, not as a catalogue would. Style: a warm painted quality taken from Rajasthani miniature painting, but modern and clean. Not a pastiche of a miniature. Not a photograph. Palette: saffron, deep red, indigo sky. Shape: vertical, for a phone screen. Text: none in the image. The top third stays empty and I will set the concert details there myself. </fence> <spark> One detail of the scene is yours to invent - something true to Barmer at sunset that I have not specified. Say which detail you added. </spark> <task> Write the image brief as an Artifact, in a single paragraph an image tool will accept, followed by a short list of what must not appear. Then, below it: the four instruments with the phrase you used to describe each, so I can correct you if a hold or a size is wrong. I play with these musicians; I will know. Then one line naming the weakest part of the brief - the thing an image tool is most likely to get wrong. </task>
Then loop it
- The morchang description is wrong - it is small, held at the mouth in one hand, not resting in the lap. Correct that line in the Artifact and leave the other three alone.
- Now add to the brief that each musician must be a different age with a different turban colour, and that the top third stays clear. Keep every other sentence identical, so the only change in the picture is the one I asked for.
- Write a second brief for a wide banner version - same style, same palette, same instruments - with the clear space on the left third instead of the top.
Why it worksThe fence of instruments, style, colours and empty space lets the AI invent the scene freely while still giving Bhanwar a poster he can use.
Instead of
Make a fun activity on water pollution.
Claude version
<fence> Class: Class 8 science. Topic: water pollution and purification. Setting: an imaginary village on the bank of the Mahanadi, a few days after a flood. Roles: six - a farmer, a health worker, a factory manager, three students of the village school. Goal: the class must agree on one plan to make the village's drinking water safe. Time: thirty minutes, including the arguing. Science: correct, and pitched at Class 8. Nothing that needs equipment a village would not have. No magic filter. Cards: three or four lines each, in the second person, so a thirteen-year-old reads it and becomes that person. Forbidden: a villain. The factory manager must have a case worth hearing. </fence> <spark> A twist to spring halfway through - something a flood would plausibly do to a village's water supply, which I have not thought of. It goes in a separate section marked for the teacher, not on any student card. </spark> <task> Build the role-play as an Artifact: the six cards, then the teacher's twist, then a thirty-minute timing plan. Before that, in two lines: where does my fence make your job harder than it should be - thirty minutes against six roles, correct science against a thirteen-year-old's vocabulary? Tell me which rule I should loosen. After the Artifact: the two or three scientific points that must survive the discussion even if the class goes off course, and one line on the mistake a Class 8 group is most likely to make about water purification. </task>
Then loop it
- The twist is good. Add two questions to the end of each card - one on the science, one on what that person gave up in the agreement - and edit the Artifact in place.
- The factory manager is still the obvious villain. Give him an argument a thoughtful student would struggle to answer, without making him right.
- Now the six cards in Odia as a second Artifact, second-person wording kept, teacher's twist left in English.
Why it worksFreedom in the characters and twist, fenced by a real topic, a time limit and correct science, gives a lesson that is lively but on target.
Questions
What is The Principle of Controlled Imagination in prompt engineering?
Creative work needs two things at once. The spark is the invitation to invent - write a story, design a poster, build a role-play. The fence is everything you settle in advance: who the character is, where it happens, how long it runs, what tone it keeps, what must be true at the end. Without the fence the machine wanders off somewhere irrelevant; without the spark it merely rearranges what you already told it. Give it both and you get something you did not expect, in the shape you actually needed.
When should I use this technique?
When you want it to invent something - a bedtime story, a concert poster, a classroom activity - but the result has to be usable: the right length, the right language, nothing frightening, nothing off the topic.
How do I apply it in Claude?
Separate the two halves in the prompt itself: a tag for the fence, holding everything that is settled, and a tag for the spark, holding the one thing you are inviting it to invent. It keeps a fence unusually well, which is the point of doing it this way - and it will tell you when two of your rules fight each other, if you ask it to. The story itself goes in an Artifact so you refine the same text instead of accumulating drafts. On pictures, be clear about the limit: it does not make images, but it writes a precise image brief - composition, light, colours, the space left for text - that you paste into a tool that does, and it is good at checking that brief against your fence. A fence you use nightly belongs in a Project's instructions.
What are the limits of this technique in Claude?
It does not generate images. That is the honest answer for the poster, and the workaround - have it write the brief, then take the brief elsewhere - is a real workaround rather than a consolation. On words, its instinct is tasteful, and tasteful is the enemy of a surprise: asked for a funny moment it writes something charming and mild, and asked for a twist it writes something sensible. Make the strange thing a requirement and ask what it rejected as too odd; the discarded version is often the one you wanted. It also writes long and lyrical - word limits are approximate at best, so count the draft - and it is fond of a closing moral, which you should forbid by name.
How do I improve the answer after the first try?
Read the first draft and ask two questions: did it stay inside my fence, and did it surprise me? If it wandered - wrong length, wrong tone, a scary villain - tighten one rule: "Keep it under 300 words, with no villains." If it feels flat and safe, loosen one: "Be more playful in the middle." Change one rule at a time so you can see what each change does. When you find the right mix, save the prompt as a template and change only the character or setting next time.
Loop it
Read the first draft and ask two questions: did it stay inside my fence, and did it surprise me? If it wandered - wrong length, wrong tone, a scary villain - tighten one rule: "Keep it under 300 words, with no villains." If it feels flat and safe, loosen one: "Be more playful in the middle." Change one rule at a time so you can see what each change does. When you find the right mix, save the prompt as a template and change only the character or setting next time.
This lesson on the other tools
The technique is the same; the way you write it is not. ChatGPT, Gemini.Perplexity.