How to Build a Magic System in Sci-Fi

Start with one mechanism and one hard limit. Not a taxonomy, not five schools, one thing that works and one wall it cannot get past.

The limit is doing more work than the mechanism. Le Guin's ansible is almost embarrassingly simple, a box that sends a message anywhere instantly, and the whole point is that the message is all you get.

No ships, no cargo, no rescue. That single restriction keeps her worlds enormous instead of convenient, because help can always be told and never sent.

Dune's prescience runs the same way. Navigators can see a safe path through folded space and cannot see through other prescients, so the ceiling on the power is other people who have it.

A reader tests your limit within about two chapters. Give them one they can hold.

Now decide what your mechanism eats and where that comes from. The limit you just wrote tells you what kind of scarcity makes sense.

This is the step most drafts skip. Powers get costs assigned to them like a fee, some vague drain on the user, when the interesting version is a chain of people and places that had to cooperate to make one use possible.

Spice only comes from Arrakis. It has to be harvested off open sand, in weather, with worms in it, by crews who die doing it.

So the mechanism is prescience but the actual story is a supply line, and everyone from the Emperor down is standing on one planet's worth of it.

When you know the input, you know the chokepoint. When you know the chokepoint, you know who really holds power in your setting, and it usually is not the person with the ability.

Scarcity plus a chokepoint produces a class structure. That happens whether you design it or not, so you may as well design it.

Gibson understood this better than almost anyone. In his work the mechanism is network access and the limit is ICE, defensive software that will hurt you, and what falls out of that is a world where the people with legitimate access sit inside corporations and everyone else is a specialist criminal renting time on gear they cannot afford to own.

Access is the class system. The skill is almost secondary.

Niven pushed the same logic the other direction. Make teleportation cheap and universal and you do not get utopia, you get flash crowds, thousands of people converging on a disaster in minutes because they can.

Decide who is locked out and what they do about it. That group is where your story usually lives.

Last decision, and it is the one that pays off all three before it. What breaks, and who is standing there.

A mechanism with no failure mode is a tool. A mechanism that can fail is a threat that hangs over everyone who depends on it, and dependence is exactly what you built in the previous three steps.

Cut the spice supply and it is not one ship that stops, it is every ship, every empire, every prescient who now goes blind. Frank Herbert only gets to say "the spice must flow" as a threat because he did the supply chain work first.

Failure also sorts your cast honestly. The people with reserves ride it out and the people locked out do not.

The worst version of this is a system that fails dramatically and costs nobody anything. Make the outage land on someone the reader already knows.

Run the chain once more before you write. Mechanism, limit, input, chokepoint, who is locked out, what breaks.

If any link does not follow from the one before it, that is where the system will feel arbitrary to a reader, even if they cannot say why. Usually the culprit is a capability you added because a scene needed it. Cut it or pay for it properly.

Don't get me wrong, some real science underneath helps. Grounding a mechanism in thermodynamics or genetics or computation buys you credibility cheaply.

But the physics is not the thing readers believe. Cost is.

Get the chain right and you can explain almost nothing about how the thing works. Readers will fill it in themselves, because they can see who pays.