How to Create a Coherent Magic System (Hard vs Soft Magic)

8 min read
Worldbuilding
Magic
Fantasy
Coherence
Share
A coherent magic system — defined by its limits
Without limits, magic breaks tension. Here's how to build a system that holds — costs, rules, owned exceptions.

Try SagaScope for your magic system

Sign up for the waitlist to be among the first to test Codex management and magic coherence checking in SagaScope.

Magic is often what makes you want to write a fantasy novel. But it's also what can make a universe collapse fastest: a spell that appears from nowhere to save the heroes, a forgotten rule, a "flexible" limit whenever it gets in the way of the plot. The reader immediately senses when magic is no longer a framework but a get-out-of-jail card.

In this article we'll see how to create a coherent magic system, whether you prefer Sanderson's laws (Hard magic system) or Tolkien's more mysterious magic (soft magic), including hybrid universes like Harry Potter. You'll see how to set clear rules, handle exceptions without breaking everything, and above all how to keep these decisions in mind over the long haul… even when you're writing volume 3 two years after the First draft.

We'll also look at how a tool like SagaScope can help you remember, visualize and query these rules—and tease a future AI assistant that can answer questions like: "Does this spell respect my magic laws?"

Hard vs Soft Magic: What We're Really Talking About

"Hard" magic: clear rules, visible stakes

In a so-called "hard" magic system, the rules are explicit: the reader quickly understands what's possible, what isn't, and at what cost. That's Brandon Sanderson's specialty in Mistborn or The Stormlight Archive: well-defined abilities, clear limitations, precise costs (metals consumed, oaths to keep, etc.).

Advantages of hard magic:

  • Clear stakes: if we know a power can only be used three times, each use matters.
  • Reader anticipation: they can mentally play with the system ("if they combine this ability with that one, what happens?").
  • Logical twists: solutions feel clever, not pulled out of a hat.

Risks:

  • slipping into RPG manual mode: too much jargon, too many rules spelled out;
  • forgetting the emotional or symbolic dimension of magic for the sake of pure system.

"Soft" magic: mystery, wonder and implicit limits

In so-called "soft" magic, the rules are largely implicit. The reader doesn't know exactly what's possible but feels an internal logic: the magic has a tone, a flavor, a consistency of mood.

In Tolkien, for example, we don't have a clear table of Gandalf's spells. Yet we feel that:

  • magic is rare and often subtle;
  • it's tied to ancient, sacred or natural forces;
  • it's not there to solve every problem at the last moment.

Advantages:

  • a strong sense of mystery and wonder;
  • room to stay symbolic: magic can embody themes, mythological forces, rather than quantifiable "skills."

Risks:

  • sliding into Deus ex machina: a power never seen before appears to save everyone;
  • giving the impression that anything is possible, so nothing has weight.

Mixing both: why most sagas are hybrid

Many universes actually work with a mix:

  • fairly clear rules on some aspects (school spells in Harry Potter, combat techniques in some shōnen);
  • blurry zones reserved for mystery, the sacred or very high-level power.

What matters isn't choosing "hard vs soft" once and for all, but consciously deciding where you want to be explicit and where you accept blur—then sticking to that line.

Defining the Foundations of Your Magic System

Origin of magic: source, cost, access

Start by asking three simple questions:

  1. Where does magic come from?
    • A natural energy?
    • Entities (gods, spirits)?
    • Pacts?
    • Technology?
  2. What is the cost of using it?
    • Fatigue, pain, aging.
    • Scarcity of a material.
    • Corruption, loss of memories, moral debts, etc.
  3. Who can access it?
    • Everyone?
    • A trained elite?
    • A caste born with a gift?
    • People who paid a particular price?

The harder the system, the more these answers must be concrete and verifiable in the text. The softer it is, the more they can be suggested, but it helps if you have answers behind the scenes.

What magic can do (and what it will never do)

One of the most common mistakes is to multiply possibilities without ever closing them. Result: you end up with characters who can do almost anything… except when you need them to fail.

Make a list, even a short one, of:

  • 3–5 things magic does very well in your world (heal, manipulate elements, bind oaths, see the near future, etc.);
  • 3–5 things it can never do, even at the highest level (raise the dead, completely cancel a prophecy, instant travel for everyone, etc.).

These absolute prohibitions give your plot depth: characters must find other solutions than magic when they run into them.

Social, political and technological consequences

A coherent magic system isn't just a list of powers; it's a shock to a society. Ask yourself:

  • Who controls magic? An order, an empire, no one?
  • How does magic affect medicine (healing vs mortality), transport (teleportation, magical mounts), war (weapons, shields, strategy), economy (resource creation, artificial scarcity)?

A world where all diseases can be cured but the village hospital is still a medieval dispensary will quickly feel inconsistent.

Avoiding Inconsistencies That Frustrate the Reader

The magical Deus Ex Machina and how to avoid it

The magical Deus Ex Machina is:

  • a power never mentioned before that appears at the exact moment all seems lost;
  • use of magic with no cost, no setup, no consequence.

To avoid it:

  • foreshadow your magical abilities: show them in a minor form before using them at the Climax;
  • regularly remind the reader, through small details, of limits and costs.

The implicit rule: the more you want to resolve major conflicts with magic, the more the reader must understand that magic.

Handling exceptions without destroying the rules

Sometimes you'll want to introduce an exception ("normally you can't raise the dead, but…").

Two clean ways to do it:

  • Exception framed within the system
    For example: a unique relic, an extremely rare sacrificial ritual, a terrible price. The exception confirms the rule by showing how serious it is to bypass it.
  • Exception with major narrative cost
    If you break a rule, show the consequences: world disruption, hero corruption, creation of a graver new stake.

Coherence across scenes, volumes and spin-offs

The difficulty isn't so much setting rules once as keeping them over time:

  • you write volume 1, you set limits;
  • you write volume 2, you forget a constraint from three years ago;
  • a reader notices that "normally, this spell should work here too."

Hence the use of documenting your magic system in a real Codex (and not only in your head).

Commented Examples: Sanderson, Tolkien, Harry Potter

Why Sanderson's rules became a reference

In Mistborn, magic (Allomancy) rests on absorbing specific metals, with:

  • clear powers (push/pull metal, enhance senses, influence emotions…);
  • visible costs (metals consumed, fatigue, dependence);
  • interesting combinations (characters who master several metals).

The reader quickly understands what's possible and watches for creative solutions characters will invent within this framework.

Tolkien: mainly "soft" but framed magic

In Tolkien, magic is often tied to:

  • songs (creative/verbal power);
  • artifacts (Rings, swords, blessed objects);
  • quasi-divine figures (the Istari, the Valar).

We don't have a spell manual, but we feel red lines:

  • you don't snap your fingers to resolve the war;
  • magic is rare, tied to History and the sacred.

Harry Potter: a "school" system with accepted blur

In Harry Potter we have:

  • named spells, listed in textbooks (hard);
  • blurry zones (ancient magics, sacrificial magic, power of love, Peverell wand…).

The balance works because:

  • daily life is very hard (you know what a spell does);
  • major events are more mythical (prophecies, ancient magic), so softer.

How SagaScope Helps You Keep Your Magic Coherent

Centralize your magic rules in your Codex

In a tool like SagaScope, you can use the universe Codex to:

  • define sources of magic, costs, limits;
  • create dedicated entries for your magic types, orders, artifacts.

The idea is to avoid your rules living only in a paper notebook or a corner of your Notion.

Where a simple wiki stays passive, SagaScope is designed to connect to the manuscript:

  • each scene can reference the rules or concepts used (spells, laws, artifacts);
  • the ingestion AI can recognize when a passage uses an already-defined rule.

In time, this allows:

  • spotting when you break a rule without realizing it;
  • surfacing scenes that could be strengthened (e.g. by recalling a cost or limit already set).

Saga teaser: querying your system ("does this spell respect my rules?")

Even if Saga (SagaScope's chatbot) isn't available yet when you read this, our goal is clear: create an assistant that can dialog with your Codex and your manuscript.

The idea, in time, is that you can ask it questions like:

  • "Does this ritual violate a rule I set earlier?"
  • "What are the possible consequences of this new ability on my magic system?"
  • "Have I already shown this type of spell in previous volumes?"

The point isn't to let the AI invent your system for you, but to put it at the service of what you've already defined—so no important rule falls by the wayside over the volumes.

Keep this framework handy

Get SagaScope early access + writer templates — one email, no account required.

Ready to structure your novel?

Join the SagaScope waitlist. Founder perk: locked pricing + AI credits at launch.

ST

SagaScope Team

The team behind SagaScope, passionate about writing and technology.