How to build a magic system

A person can bring rain to a field, but only by taking it from somewhere else. Before you have named the spell, you already have a dispute, a profession, and a reason for a village to fear its neighbors.

That is a useful starting point for a magic system: a possibility with consequences. You do not need a catalog of powers before you write. You need to understand what your magic asks of the people who use it.

Start with the story’s central pressure#

Ask what problem magic should complicate. A story about inheritance might give magic to anyone willing to surrender a memory. A story about scarcity might make healing consume a resource that cannot be replaced. The connection need not be a metaphor announced on the page. It is a way to make the world and the character pull on the same rope.

Write a one-sentence premise: Someone can do X, provided Y, but doing so causes Z. Treat it as a working hypothesis, not a law you can never revise.

For our rain-makers: a trained listener can move a storm, provided they can hear its thunder, but the valley it leaves behind receives no rain. This tells us the power’s reach, an access condition, and an external cost.

Separate limits, costs, and risks#

These three ideas do different jobs. Mixing them together can make a power feel conveniently weak whenever the plot needs trouble.

A reliable cost changes decisions even when everything goes well. A risk creates uncertainty. A limit keeps some problems outside magic’s reach. Choose at least one of each and test whether your characters could circumvent them with ordinary cooperation.

Decide who can use it#

Access creates politics. If magic is inherited, families may guard marriages. If it is learned, teachers control a bottleneck. If anyone can use it with the right instrument, workshops and supply chains matter as much as individual talent.

Avoid stopping at “only a gifted few.” Ask how a gift is recognized, who can afford the test, and what happens to someone whose ability appears late. A supposedly neutral examination can still exclude people who cannot travel to the capital.

In the rain-maker world, hearing is not enough: a listener must learn the differences between storm patterns. Apprenticeships are long because mistakes hurt people far away. Now the setting has a reason for training, certification, and unauthorized practice.

Follow the consequences into daily life#

A power becomes part of a world when people plan around it. Work outward from one ordinary household rather than immediately designing an empire.

1. Work: What task becomes easier, and which profession loses its livelihood?
2. Home: What precaution does a family take without thinking about it?
3. Law: Who pays when magic harms someone outside the agreement?
4. Belief: What do people believe about the power that practitioners cannot prove?
5. Inequality: Who receives the benefit, and who absorbs the cost?

Rain contracts might require witnesses from both valleys. Wealthy estates could purchase storms during droughts. A farmer might hang bells outdoors to recognize an approaching listener’s storm. These details arise from the same premise, so they feel connected rather than ornamental.

Work one request through the system#

Before you draft a full scene, take one request and run it through every decision you have made so far, without adding anything new.

In the third dry month, the lower valley’s grain council asks for rain. The only storm within hearing is building over the upper valley’s hills, and the listener who hears it is Maren, an apprentice in her final year.

1. Premise: Maren can move the storm, because she can hear its thunder.
2. Access: She is not yet certified, and her teacher is too ill to travel. Acting alone would be unauthorized practice.
3. Limit: She cannot make more rain, so the real question is whose rain the lower valley receives.
4. Cost: The upper valley loses water it was counting on. The contract needs witnesses from both valleys, and the upper valley refuses to send one.
5. Risk: The storm has been building for days. A short move is safe but does not reach the lower fields. A long move reaches them and could arrive as hail on the crop it was meant to save.

None of this required a new rule, yet Maren now has a real choice. She can refuse. She can move the storm halfway, where it fills the shared reservoir but waters no one’s grain. Or she can carry it the whole distance without a contract. Each option costs something, and each tells the reader who she is.

The walk-through also exposes gaps. Perhaps you just decided that older storms are harder to steer, or that a contract missing a witness is void. Record those as new facts and check them against earlier scenes. If you invent a rule only so the scene can end well, treat it as a warning sign.

Choose how much the reader understands#

The author’s notes and the reader’s knowledge do not have to match. You may know a precise mechanism while a character understands it through ritual. You may also leave the mechanism unresolved and establish only what people have observed.

If magic will solve a major conflict, give the reader enough prior evidence to recognize the solution as possible. If magic’s role is to inspire dread or wonder, unanswered questions may serve the story. In either case, avoid introducing a new ability at the exact moment it erases the hardest decision.

Keep uncertainty specific#

“We do not know whether storms remember their original valley” is a productive mystery. “Magic can do anything” gives you less to work with. The first invites disagreement, experiment, and folklore; the second can dissolve the stakes.

Match the system to the story’s length#

A short story and a long series need different amounts of system. Decide only what the length can carry.

A rain-maker short story could be the refusal scene and little else. A novel needs the apprenticeships and contracts, because its characters will live inside them for hundreds of pages.

For a series, decide early what is allowed to grow. Skill, knowledge, and institutions can expand from book to book; the core limit should hold. If a later book finds a way around the cost, make the discovery expensive too. Learning to split a storm lets one listener water two valleys, and gives twice as many valleys a grievance.

Common mistakes and how to fix them#

Each of these makes magic feel convenient rather than consequential, and each can be fixed in revision.

The cost disappears when the plot gets busy#

Early chapters show every price, and by the final battle spells are free. For each scene that uses magic, note who paid and whether anyone on the page knows. If Maren moves a storm in the last act, some valley went dry. Let someone mention it later, even in a single line.

The world ignores what magic makes easy#

If storms can be moved, why does any valley still starve in a drought? List the three uses an ordinary person would think of first, then decide whether each is common, regulated, or impossible. Every answer gives you an institution or a limit.

A limit appears only when the plot needs it#

A restriction revealed at the climax feels like a cheat, even if it sat in your notes from the start. Show the rule earlier, in a scene where it causes trouble instead of resolving it. If hail will matter in the final storm, let an earlier move go wrong on a smaller scale.

Test the system in a small scene#

Write a scene in which a practitioner must refuse a reasonable request. A village asks for rain, but moving the nearest storm would destroy a neighboring harvest. Let the refusal produce an argument between people who both have good reasons.

Then write a second version from the person who bears the cost. If that perspective changes how the power feels, your magic has begun to do more than decorate the setting.

When both versions exist, read them against a few questions:

• Did magic make the decision harder, or did it only make the problem go away?
• Who paid, and does anyone in the scene know it?
• Did a character do something a rule should have prevented? If so, change the scene or the rule, and note which.

Keep a compact reference with the premise, constraints, access rules, and unresolved questions. Expand it only when a scene needs an answer. For the institutions that grow around magic, continue with creating a fictional culture.

Keep the rules in Yazar.io#

Yazar.io suits this stage well, because its sections already match the parts of a magic system: Spells for individual workings, Lore for the rules beneath them, and Characters for the people who can use them. Set up the spell template once with fields for limit, cost and risk, so every new spell asks the same three questions (field templates).

When you type Maren’s name in a spell’s entry, Yazar.io links the two automatically, and the backlink panel on her page lists every entry that mentions her (features). When a scene changes a cost, that panel shows which characters, and therefore which scenes, to reread. Your manuscript stays in Word or Google Docs; Yazar.io keeps the reference beside it.

Update, 10 October 2026: Added a worked example, guidance on scale, common mistakes, and questions for testing a scene, and expanded the Yazar.io section with specific features from Yazar.io’s public pages. On 8 October 2026, a topic-specific Yazar.io suggestion had been added.