A magic system rule is a promise you make to the reader about what magic can and cannot do. Once you make it, you have to keep it, or the reader stops believing anything else in the book.
That is the whole job. Everything else is detail.
Most advice about magic rules starts with the source, the elements, the cool powers. That is backwards. The source is fun to invent and it does almost nothing for the story. The rules are what the reader actually feels, because rules are the only part of a magic system that ever tells a character "no."
A rule is a constraint, not a feature
The most common mistake is writing rules that describe what magic can do. Those are not rules. Those are abilities.
A real rule is a limit. It says what magic costs, what it cannot reach, when it fails. Brandon Sanderson built most of his reputation on this idea, and his Second Law says it plainly: limitations are more interesting than powers. A character who can do anything is boring. A character who can do one specific thing and pays for it is a story.
Allomancy in Mistborn is the standard example for a reason. Burning metals gives you power, but you only have so much metal, and burning it is visible, and everyone in the room knows exactly what you just did. The cool part is not that Vin can push on metal. The cool part is that she runs out.
Compare that to the version of magic where the wizard is tired and then, in the moment it matters most, is somehow not tired anymore. The reader clocks that instantly. You spent your credibility to win one scene.
The rules a reader can predict are the ones worth writing
There is a split worth naming early, because it decides how strict your rules need to be.
On one end you have codified, mechanical systems where the reader can more or less do the math. On the other you have systems built for wonder, where magic stays strange and unexplained. This is the hard magic system versus soft magic distinction, and most stories land somewhere in the middle.
The rule that matters is Sanderson's First Law: your ability to solve problems with magic is directly proportional to how well the reader understands that magic. If the reader knows the rules, a clever use of magic to escape a trap feels earned. If the reader does not know the rules, the same escape feels like cheating.
So the question is not "how magical should this feel." The question is "am I going to solve problems with this magic, or just create atmosphere with it." If you solve problems, the reader needs the rules up front. If you only ever create dread and wonder, you can keep the rules hidden and it works fine. Gandalf never explains himself and Tolkien is not worse for it.
Here is how the two ends actually differ in practice.
| Codified rules (hard) | Withheld rules (soft) | |
|---|---|---|
| Reader knows the limits | Yes, up front | No, kept vague |
| Magic used to solve plot problems | Yes, and it feels earned | Rarely, or it feels like cheating |
| Main job of the magic | Constraint and tension | Wonder and dread |
| Example | Allomancy, Avatar bending | Gandalf, most Earthsea threats |
| Risk if done badly | Feels like a rulebook | Feels like a cheat code |
Neither column is better. They are answers to different questions. What breaks a book is sitting in the left column while writing right-column rules, or the reverse.
How many rules you actually need
Fewer than you think. A magic system does not need to be complete. It needs to be consistent in the parts the reader sees.
Three or four load-bearing rules will carry an entire novel if they interact. Avatar: The Last Airbender runs almost entirely on a handful: you bend the element you are born to, you learn from a master, the Avatar bends all four, and the Fire Nation's whole war is built on breaking that balance. That is not a thick rulebook. It is a few rules that touch everything.
The trap is inventing forty rules nobody will ever use. That is worldbuilding as procrastination. It feels like progress because you are writing, but the reader only ever meets the rules that show up in a scene. If a rule never constrains a character, it does not exist as far as the story is concerned.
Write the rules that will be tested. Leave the rest as fog. You can always sharpen the fog later, and you cannot un-write a rule the reader has already watched you break.
Limits are where the tension lives
Consequences are where the rules earn their keep in the plot.
A rule the reader never sees enforced is a rule the reader does not believe. Someone has to break the taboo, pay the cost, and have the rest of the world notice. In Ursula K. Le Guin's Earthsea, magic runs on true names, and the cost is the Equilibrium: change one thing and something else shifts to answer it. Ged does not just cast a spell and win. He casts a spell and the world sends him a bill.
That bill is the story. The reader does not lean forward because a character can do magic. They lean forward because doing it might cost something they cannot afford.
This is why limits generate more plot than powers ever do. A power is a solved problem. A limit is an open question the reader carries into the next chapter.
Rules and mechanics are not the same thing
Worth separating two words people use interchangeably.
The mechanics are how the magic physically works: what you touch, what you say, what happens. The rules are the boundaries around those mechanics: what it costs, what it cannot do, who is allowed. If you want to go deep on the machinery itself, magic system mechanics covers the moving parts. The rules sit one level up, governing all of it.
You need both, but they answer different reader questions. Mechanics answer "what did I just watch happen." Rules answer "should I have believed it." A system with great mechanics and no rules feels like a special-effects reel. A system with clear rules and thin mechanics still holds together, because the reader trusts the boundaries even when the details stay vague.
A rule everyone in the world has to obey
The strongest test of a rule is whether it applies to the villain too.
If magic costs the hero something but the antagonist seems to pay nothing, the reader feels the seams. The most convincing systems are the ones where the rule is a fact of the world, not a difficulty setting for the protagonist. Everyone drinks from the same river. The villain is just better at it, or crueler about who pays.
In The Thirteenth House, one of my own worlds, the rule is that power runs on your own lifespan. Small uses are cheap. Cinematic uses burn permanent years off your life. That single rule does the villain test for me, because the antagonist is not exempt from it. He is just willing to spend more of himself, and that willingness is the scariest thing about him. The rule is the character.
This is also where magic rules start to look like real systems of power. A rule that says who can access magic, who trains, who gets locked out, is not really a rule about magic. It is a rule about class, and readers recognize it instantly because they have lived inside systems that hand out just enough while quietly taking more. The rules of your magic are the physics of your world, and physics does not make exceptions for the people in charge.
If you are building the whole thing from nothing, magic system creation walks through the earlier decisions, and magic system elements covers the components the rules end up governing. But the rules are the part that makes any of it feel true.
FAQ
What makes a good magic system rule? A good rule is a limit, not a power. It states what magic costs, what it cannot do, or when it fails, and it holds consistently every time it appears. The rule the reader can predict and watch get enforced is the one that builds trust in the whole story.
How many rules should a magic system have? Fewer than most writers assume. Three or four rules that interact with each other will carry a full novel, as long as they actually constrain characters in scenes. A rule that never says "no" to anyone does not count. Extra rules nobody uses are worldbuilding for its own sake, not story.
How strict should magic system rules be? As strict as the job you are asking the magic to do. If you use magic to solve plot problems, the reader needs to understand the rules clearly and up front, or the solution feels like cheating. If the magic exists mainly for atmosphere and wonder, you can keep the rules vague and it still works.
Do the rules apply to villains too? Yes, and that is often what separates a believable system from a convenient one. If the rules bind the hero but the antagonist ignores them, readers feel it. The strongest systems treat the rules as a fact of the world that everyone pays into, hero and villain alike.
What is the difference between hard and soft magic rules? Hard magic has codified, knowable rules the reader can reason with, which lets magic solve problems without feeling like a cheat. Soft magic keeps its rules hidden to preserve mystery, so it works best for creating dread and wonder rather than resolving conflicts. Most stories mix the two.
Should I write all my magic rules before I start the story? No. Write the rules that will actually be tested in scenes and leave the rest vague. You can always sharpen an undefined area later, but you cannot take back a rule the reader has already watched you break.
