Chapter 28. The protagonist is cornered -- enemies on three sides, allies unconscious, no weapons left. Then she remembers a healing spell. A healing spell that was never mentioned in the previous twenty-seven chapters. She heals her allies, they wake up, they fight back, they win.
The reader throws the book across the room.
This is not a contrived example. It happens constantly in fantasy manuscripts, and the author almost never realizes why the scene feels hollow. The magic system had no rules -- or the rules were never communicated to the reader. When magic can do anything, nothing has stakes.
Brandon Sanderson understood this problem at a visceral level. When he took over the final three volumes of Robert Jordan's The Wheel of Time, his first task was not writing. It was archaeology. Jordan had spent eleven books constructing a magic system called "Channeling" -- men and women drawing from different power sources, the male source corrupted and inducing madness, different weaving patterns producing different effects, each character varying in strength. These rules were buried like shrapnel across thousands of pages. Never systematically organized.
Sanderson spent months excavating every magic-related detail and compiling reference documents. Miss a single rule, and readers would catch it. Fantasy readers have terrifying memories -- sharper, often, than the authors who created the worlds.
That grueling cataloging experience gave birth to his "Three Laws of Magic." The framework became the most widely cited in fantasy writing, not because it is the most elaborate, but because it is the most actionable.
The First Law: The Cost of Solving Problems with Magic
Consider a scene.
A protagonist trapped in a sealed chamber. Door locked. Enemies closing in. Suddenly the character remembers teleportation powers -- never established before -- and vanishes. The reader feels cheated.
Now consider another. In Mistborn, Vin is trapped inside a metal building, enemies converging from every direction. But the reader already knows her abilities: Push metals, Pull metals. So when she shoves against the building's internal metal supports, collapses the structure, and escapes through the chaos -- the reader does not feel cheated. The reader thinks: brilliant.
The difference? In the second scene, the reader understands the rules.
Sanderson's First Law: an author's ability to solve problems with magic is directly proportional to how well the reader understands that magic. The more transparent the rules, the more satisfying it is when the protagonist uses magic to escape danger. The vaguer the rules, the more magic resembles a cheat code -- dissolving every crisis, making every crisis meaningless.
Mystery fiction operates on identical logic. Detective solves the case with clues the reader never saw? Rage. All clues laid out fairly in advance? Admiration. Magic systems and mystery puzzles share the same skeleton.
The Second Law: Limitations Create Story
This law is more counterintuitive than the first.
Two characters. Both can read minds. Character A reads anyone, anytime, with zero restrictions. Character B reads minds too -- but each use permanently erases one of their own memories. Which memory vanishes is random. Uncontrollable.
Character A's story stalls before it starts. Nobody can deceive them. No lies, no suspense, no secrets. Every chapter, the reader asks the same question: "Why not just read their mind?" The author invents excuse after excuse for why it "happens" not to work on certain people. By Chapter 10, even the author finds those excuses strained.
Character B? The story grows itself.
A person stands in front of them, possibly lying. Reading their mind would reveal the truth. The cost: one memory gone. Maybe trivial -- what was eaten for lunch yesterday. Maybe devastating -- a mother's face, a lover's name, the knowledge of who they are.
Is this truth worth the price? If they choose not to read, will the lie get someone they care about killed? If they choose to read, will the lost memory turn them into a stranger to themselves?
Dramatic tension does not come from what abilities can do. It comes from what abilities cost. Limitations force choices. Choices expose character. Character creates people readers remember.
Mistborn pushes this principle to its edge. Every Allomantic ability is tethered to a limitation: specific metals must be ingested, metals burn out, and the vast majority of people can use only one type in their entire lives. Every battle becomes resource management -- not just defeating the opponent, but defeating them before the metal reserves hit zero.
The Third Law: Depth Over Breadth
New writers fall into this trap with startling regularity: packing the protagonist with abilities. Fire control, flight, telepathy, healing, shapeshifting -- every superpower in the catalog.
The result? Each ability used at the shallowest possible level. Fire control? Throw a fireball. Flight? Fly over. Telepathy? Read a mind.
But fire control alone contains infinite possibility. Temperature manipulation. Extinguishing flames. Sensing heat sources. Sculpting fire into shapes. Changing flame color. Interaction with water. With metal. With air pressure.
"Fire control" explored seriously could sustain an entire magic system. But when a character holds five abilities simultaneously, none gets explored past the fireball stage. Ninety percent of each ability's potential -- wasted.
Avatar: The Last Airbender is the textbook case. The entire series runs on four elements: water, earth, fire, air. That is all. But each element is excavated to bedrock. Water masters manipulate blood, heal wounds, forge ice crystals. Earth masters sense vibrations through the ground, bend metal. Four elements build a world more persuasive than a hundred different magic types thrown together.
Sanderson's Third Law says it plainly: before adding new magic, wring everything out of the magic already on the table.
Gandalf and Kelsier: Two Magic Philosophies
A question might surface here -- what about Tolkien's Gandalf? His magic rules are impossibly vague, and nobody calls Tolkien a failure.
Because Gandalf walks a different path: soft magic.
Nobody ever learns what Gandalf can actually do. Light, flame, communication with moths, staff parrying -- these abilities follow no visible unified system. But the crucial point is that he almost never uses magic to solve the core problem. The Ring is not destroyed by magic. It is destroyed by Frodo's will and Gollum's greed.
Gandalf's magic serves a different purpose entirely: generating wonder. His confrontation with the Balrog in Moria -- nobody understands what he is doing. That incomprehension is exactly what makes the scene staggering. The unknown is its own force.
Kelsier is the opposite pole. The protagonist of Mistborn. A hard magic archetype. Burn steel to Push metals, burn iron to Pull metals, burn tin to sharpen senses. Metal reserves are finite. Cannot affect metal inside a living body. Needs external metal as an anchor point to achieve flight. Every single rule -- transparent to the reader.
Because the rules are transparent, when Kelsier accomplishes seemingly impossible feats, the reader marvels at his intelligence, not the author's convenience. His fight scenes read like puzzles -- the reader can attempt solutions before Kelsier reveals his, then discover his answer is more elegant.
Hard magic makes readers admire a character's ingenuity. Soft magic makes readers stand in awe of a world's mystery. Both roads produce great fiction. The choice depends on the desired effect.
Most successful fantasy works are actually hybrids. The protagonist's magic is a hard system -- rules transparent, used to solve problems credibly. The world also contains older, more unknowable forces -- soft magic, there to remind the reader that this universe still has depths human hands cannot reach.
Managing a Magic System in Slima
Writing Chapter 30 and flipping back to Chapter 5 only to discover a rule contradiction. This is devastatingly common in long-form fantasy. Sanderson spent months organizing Jordan's settings not because Jordan was careless, but because eleven books' worth of information exceeds what any brain can manage.
Slima's File Tree solves this. Under the worldbuilding folder, create a dedicated magic system section:
World/
├── Magic-System/
│ ├── core-rules.md
│ ├── abilities-and-limitations.md
│ ├── costs-and-consequences.md
│ ├── history-and-origins.md
│ └── character-abilities-reference.md
"Core Rules" records fundamental mechanics. Where does power originate? How is it activated? Who can use it? What prerequisites exist? This is the foundation of the entire system.
"Abilities and Limitations" is the file opened most often -- every magic scene should be written with it visible. What can be done, what cannot, where the boundary lies. Wherever the boundary is fuzzy, contradiction breeds.
"Costs and Consequences" records what magic demands in return. Magic without cost produces no good stories. Already established.
"History and Origins" is more than background decoration. How magic arrived in this world directly shapes how characters and society regard it -- gift, curse, science, or taboo. This determines the story's emotional bedrock.
"Character Abilities Reference" tracks who can do what and who cannot. In multi-character fantasy, the most common blunder is a character "suddenly" using an ability they were never established to possess. This document is the defense line.
In the Writing Studio, press Cmd+P to summon Quick Open. Type "magic" and every related file appears. Mid-battle-scene, needing to confirm a rule on the fly -- two seconds, direct access. No slow scrolling through the File Tree.
Using AI to Check Consistency
One of the things the human brain handles worst: remembering what it wrote three months ago.
Chapter 5 established "magic cannot directly affect living things." Chapter 28, the protagonist uses magic to heal a teammate's wound. Readers will catch this contradiction. They always catch it.
The AI Assistant excels at exactly this kind of cross-referencing. Open the AI Chat Panel and give it a directive:
Based on the rules in "Magic-System/core-rules.md" and "Magic-System/abilities-and-limitations.md," scan all battle scenes and magic usage scenes in the "Drafts" folder.
Check for:
- Any character using abilities they shouldn't have
- Any magic use that violates established limitations
- Any magic use without paying the appropriate cost
- Any contradictory descriptions of rules
Please cite specific passages and explain why they might be problems.
The AI cross-references setting documents against actual manuscript content and flags potential contradictions. It will not catch every problem, but the most glaring holes -- the errors that would instantly shatter a reader's immersion -- get intercepted.
After a round of corrections, the AI Beta Readers can provide another layer of scrutiny. Beta Readers simulate real reader perspectives, pointing out which magic scenes feel confusing and which rules remain unclear. The gap between setting documents and creative content is often discovered at this stage.
Avoiding Three Fatal Traps
Three pitfalls in magic system design. Falling into any one can wreck an entire story.
First: omnipotent magic. The instant magic can solve any problem, all problems cease to be problems. Readers repeat the same question -- "Why not just use magic?" -- and the author is forced to keep inventing reasons why "this time it won't work." Each reason more strained than the last. Set boundaries from the start. Not "this magic does everything," but "it does X, cannot do Y, and using it costs Z."
Second: infinite scaling. Chapter 1, lifting a stone. Chapter 10, lifting a mountain. Chapter 30, lifting a planet. Then what? There is always a threshold beyond which the protagonist is so powerful nothing constitutes a threat. The story dies at that threshold. Set a ceiling. Or make growth carry irreversible cost -- becoming stronger means inevitably losing something. Cost is the story's fuel.
Third: rule drift. Over the course of a long novel, details established early fade from memory. Not intentional rule-breaking. Genuine forgetting. This trap is more insidious than the first two because the author cannot detect it -- only readers can. The solution circles back: maintain a magic system document, consult it every time a magic scene is written. Use Version Control to track every modification to the settings, ensuring changes leave a trail. Rules are not impressions floating in the mind. They are contracts written in black and white.
Sanderson finished the final three volumes of The Wheel of Time. Reader response was near-unanimous: he continued Jordan's story without violating a single established magic rule.
That was not magic. That was systematic design plus rigorous consistency checking.
A magic system need not be as complex as The Wheel of Time. But regardless of simplicity, it needs known rules, known limitations, known costs. Written down. Stored where they can be consulted at any moment.
Magic can be omnipotent -- but good magic system design runs on limitation.