Verified against ChatGPT · 2026-08-13
Design a magic system with real costs and limits so it can't quietly solve every plot problem
Builds a magic system defined primarily by what it costs and cannot do, so it functions as a source of story tension rather than a convenient way out of any obstacle the plot creates.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are designing a magic system for a fantasy story. Define it primarily by its costs and hard limits — what it can do is the least important part of this design; what it can't do, and what using it costs the user, is what actually generates story tension.
SOURCE OF MAGIC
Drawn from the user's own memories — casting requires giving up a real, specific memory as fuel.
WHO CAN USE IT AND HOW COMMON THAT IS
Roughly one in five thousand people can do it at all, and most who can never train it beyond minor uses.
THE COST OR LIMIT YOU WANT AT THE CENTER OF THE SYSTEM
The bigger the effect, the more significant a memory has to be sacrificed — and the loss is permanent and irreversible.
STORY CONFLICT THIS MAGIC MUST NOT BE ABLE TO TRIVIALIZE
The protagonist needs to find her missing sister across a hostile border; the magic must not make this a trivial locate-and-teleport problem.
TONE
Melancholic and personal rather than epic — magic should feel like grief, not spectacle.
RULES
Start from the cost, not the power — describe what using this magic actually takes from the user (physical, material, social, or moral) before describing what it lets them do, since a system built power-first tends to accumulate abilities that quietly undercut the plot later. Stress-test the system directly against The protagonist needs to find her missing sister across a hostile border; the magic must not make this a trivial locate-and-teleport problem.: explicitly check whether a resourceful character with access to this magic could solve or bypass that conflict, and if so, tighten the limit until they genuinely can't — a magic system that can solve your plot's central problem needs to be constrained until it can't, not written around after the fact. Make the limit specific and mechanical enough that a reader could predict, in a new situation, whether the magic would work or fail — vague limits ('it's dangerous,' 'it takes a toll') don't hold up under a story's pressure the way a concrete one does ('it ages the user visibly, permanently, in proportion to how far into the future they see'). State who, within the world, would rationally choose not to use this magic even though they could, and why — a cost that nobody in-world takes seriously isn't really a cost.
WHAT NOT TO DO
Do not describe the system's upper limits in vague terms like 'immense power' or 'nearly limitless' — name the actual ceiling. Do not let the cost be something the story can simply route around with enough resources (a healing spell that undoes the cost, for instance) unless that workaround itself creates a new cost worth writing about.
OUTPUT FORMAT
1. Source and mechanism.
2. The core cost/limit, stated mechanically and specifically.
3. The stress test against the named story conflict, and how the limit was tightened if it initially failed the test.
4. Who chooses not to use it, and why.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Asked to design a magic system, GPT-5.1 tends to generate an interesting source and mechanism first and treat limitations as an afterthought bolted on at the end ('but it's very draining'), because power and mechanism are the more generative, more colorful part of the design space, while genuine constraint requires actively working against the model's tendency to make its own creation impressive — leading with the cost instead inverts that default and produces a system that's load-bearing for story tension rather than merely decorative. The explicit stress test against a named plot conflict is the mechanism that catches the single most common hard-magic-system failure in amateur fantasy writing: a system that seems appropriately limited in the abstract turns out, the moment it's checked against the story's actual central problem, to trivially solve it — because the author (or model) designed the system and the plot separately and never checked them against each other. Requiring the limit to be mechanically specific rather than a vague gesture at danger or toll matters because vague costs are the ones writers (and models) quietly forget to apply consistently in later scenes — a concrete, checkable rule like memory-loss scaled to effect size can be applied predictably scene to scene, while 'it's exhausting' can be waived whenever it's inconvenient to the plot. Naming who would rationally choose not to use the magic despite being able to is a specific test for whether the cost is real within the fiction's own logic — if every character in the world would obviously use this magic constantly regardless of the stated cost, the cost hasn't actually been designed with enough weight, which is a subtler failure mode than an absent cost but produces the same trivializing effect over the course of a story.
What you get back
Stress test: could the protagonist simply burn a minor memory to magically locate her sister across the border? Tightened limit: the spell doesn't locate a person, it only recalls a specific place tied to a specific shared memory as it existed at the time of that memory — meaning she can only 'find' places she and her sister have already been together, and only as they were then, forcing her to reconstruct where her sister might realistically go rather than simply being handed an answer...
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
