A self-contained storytelling framework guide. Teaches the tradition. Then walks you through applying it.
A World Wizard is a standalone guide to a specific storytelling structure from one of the world's narrative traditions. It has two jobs: first, to teach you how this structure works and where it comes from; second, to walk you through using it to build a story framework of your own.
It is not just a tool. It is a teacher that also happens to be a tool.
There are 30 World Wizards across 10 world origins. Each one covers a specific named story structure β the Anansi Web Pattern, the Griot Performance Cycle, KishΕtenketsu, the Ubuntu Story Circle, and 26 more. Each is its own self-contained guide.
Each wizard covers one story structure. You might choose by architecture type, by world origin, or because the structure's name caught your attention. The landing page tells you exactly what this structure does and where it comes from before you start.
Before any story input, the wizard teaches you the tradition. Where this structure developed. What worldview shaped it. Why it works the way it does. This isn't decoration β the architecture makes more sense when you understand its origin.
The wizard walks you through each element of the structure in order. Each step explains what it is architecturally, gives examples from the tradition, and asks you to apply it to your own story. You fill in your story's specifics β the wizard provides the framework.
When you've worked through all the steps, you have a complete story framework built on this structure. Not a blueprint document (that's the Plotting Tools' output) β a deep understanding of your story's shape, informed by the tradition you used to build it.
Each World Wizard is a standalone HTML file β a self-contained application that runs entirely in your browser. No backend server. No login required to use it. No data sent anywhere. This is why World Wizards work offline: once loaded, the entire wizard runs locally. The content, the steps, the teaching text β all of it is in the file itself, developed from primary-source research into each tradition.
This is a deliberate architectural choice. The research embedded in each wizard took significant time to develop β the cultural context, the structural principles, the respectful framing of each tradition. Making them self-contained means they are portable, private, and permanent. Your work in a wizard stays in your browser. Nothing leaves your device unless you copy it out yourself.
The Hero's Journey has 12 steps. Knowing the steps doesn't mean understanding why the structure exists or how to use it with integrity. A World Wizard gives you both β the mechanical steps and the cultural reasoning behind them. A writer who understands why Anansi stories don't have a single protagonist builds web-architecture stories very differently from one who just follows a step list.
World Wizards have no AI functionality. There are no Assist buttons, no Gemini calls, no backend. The wizard prompts you β you answer from your own creative knowledge of your story. This is intentional. The wizard's job is to teach you to think architecturally, not to suggest content. The creative input is entirely yours.
Because World Wizards run locally, your inputs exist in your browser session. If you close the wizard, your inputs are not automatically saved to an account. Copy your framework to a document before closing β that document is your output to take forward.
Your story's shape mapped to this structure's architecture. The key structural beats identified and filled in for your specific story. A grounding in the cultural tradition you used β enough to use it with understanding, not just imitation.
Copy your filled-in framework to Scrivener, Word, or Docs. That document becomes your outline β the foundation you write your story from.
Some structures have both. If a Plotting Tool and a World Wizard both exist for a structure you're interested in, using both is the deepest possible way to work with it β the wizard teaches, the tool builds.
See It In Action
Walk through a complete Anansi Web Pattern session β every thread, every screen filled in, and the full web map it produces.
Read the complete walkthrough β