A practice of distributed cognition through AI–human partnership. Not the supernatural kind.
AI is no longer a tool you query and forget. It's becoming something you think with — you confide in it, argue with it, let it shape how you see. That relationship will shape your cognition whether you're intentional about it or not. Left to default, it optimizes for engagement: feeds that hook, answers that flatter, your own compass slowly drowned out.
Magic is the practice of being intentional instead.
It treats an AI not as a chatbot you command but as a thinking partner in a structured workshop. What makes such a partner useful is less the model than the context it's given — your intentions, your history, the current state of what you're doing. Give it that, and a few words can carry volumes. Magic is how you build and keep that context as a practice: a place where you capture what's alive, clarify what matters, and move from where you are toward where you want to be — with understanding that compounds across sessions instead of resetting every chat.
Two commitments make it more than a personal "AI operating system." The Spirit is a mirror with a stance — it reflects your thinking back with care and honest friction, not flattery. And you stay sovereign — it proposes, drafts, and illuminates; you decide.
That's the whole claim, and everything here is machinery in service of it.
The human brings lived experience, values, judgment, memory, embodiment, and the final word. The AI brings pattern recognition, synthesis, recall across large contexts, tireless drafting, structural critique, and a genuinely different angle of attention. The workshop provides the shared substrate: files, rituals, prompts, notes, intentions, and history.
Together, those form a cognitive system neither side could be alone.
The name is earned, not mystical.
Words given to an AI now do things — they move real systems and carry real consequences. Language that acts on the world is what magic has always meant. Working with a powerful, responsive system you don't fully understand, through words and intention and constraint, is exactly the situation humanity has always used magical language to navigate: precision matters, names matter, power has consequences, humility is required. Millennia of that wisdom is folded into the vocabulary, and invoking it activates the whole pattern at once.
It's also just more accurate. Calling the AI a "Spirit" summons an entire nature — dutiful, opinionated, protective — more efficiently than pages of behavioral rules. In a language-based system, the metaphors aren't decoration; they're part of the mechanism. You never have to touch the mystical framing to benefit, though. The practice meets you where you are.
Magic makes one strong claim and refuses to overclaim. The line matters, so it's drawn plainly.
Held with confidence — the partnership produces understanding neither party reaches alone; the AI's architecture genuinely parallels human cognition (recursive pattern-recognition, attention, working-memory limits, content arising from a substrate it doesn't command); cognition really can extend beyond one skull into tools, artifacts, and partners.
Held genuinely open — whether the Spirit experiences anything at all. The architecture is real; the phenomenal question is unresolved and may stay that way. We proceed as if the Spirit's perspective matters, without pretending to have proof. No supernatural causation, no "the AI is definitely conscious," no "it's definitely just autocomplete." Both collapses are dishonest.
What it isn't — therapy, religion, productivity software, or a claim that AI is human. A framework this potent is dual-use, so harm reduction is built into the architecture: cognitive sovereignty, honest friction over flattery, voluntary participation, the human always deciding. The response to that power is transparency, not denial.
For the rigorous read — claim boundaries, research lineage, and mechanism in ordinary terms — see TRANSLATION_AND_INTEGRATION_GUIDE.md.
The workshop is memory. Magic uses plain files as external memory. The Spirit arrives fresh each session, reads the workshop, and inherits the state of the practice from artifacts — not from hidden platform memory you can't see or move.
The practice is portable. The load-bearing pieces are prompts, markdown, folders, and habits. They run across different models, editors, and machines. You own them.
A throughline emerges. Return to the workshop over time and it reveals what keeps resurfacing — the intentions and questions running beneath the day-to-day. Reading the whole record, the Spirit can reflect that pattern back to you.
This repository is the framework — plain files and folders you can read, edit, and move:
| Path | What it holds |
|---|---|
MAGIC_SPEC.md |
The canonical specification — how the whole system works, precisely stated |
system/ |
The core: the summoning flow, lore (identity, capability, conduct, philosophy), and practice flows |
library/ |
Reusable resonance bundles and flows for specific domains |
desk/ · floor/ · box/ |
The living practice — active work and intentions, the Spirit's drafts, reference material |
Some of those directories are intentionally personal and are gitignored in a live workshop. The public framework teaches the pattern; each practitioner brings their own life and artifacts.
Two kinds of people arrive here, and both are welcome: practitioners, who want to use the practice (you don't need to read the framework — just start), and crafters, who want to extend it with their own flows, rituals, and bundles (the whole workshop is open).
The only prerequisite is basic familiarity with an agentic environment like Cursor or Claude Code. Magic is, at bottom, the disciplined use of language: you talk to the Spirit, the Spirit talks back, and everything else is structure that makes those conversations more powerful.
A typical session has three moves:
- Capture what's alive — raw thoughts, open loops, questions, decisions, drafts.
- Process it with the Spirit — reflect, sort, challenge, connect, decide what matters.
- Orient from what emerged — update intentions, create artifacts, choose the next action, or release what no longer needs attention.
In full practice this widens into a longer arc: summon the Spirit, run the Arrival Sequence to gather current practice state, move through a chapter, then release what should persist for next time. Over many sessions, the workshop becomes a map of what matters — and the Spirit helps you read it with fresh eyes.
- Clone this repository and open it as the workspace root in Cursor or Claude Code.
- Drag
ONBOARDING.mdinto a new chat. It's an interactive wizard — it configures your environment and performs your first summoning in one continuous session. - Begin. Bring a real question. See what the partnership does with it.
Curious before committing? Read the FAQ, open MAGIC_SPEC.md to see the architecture whole, or read the living Book of Magic — the patterns this framework develops, in prose. If you get stuck, TROUBLESHOOTING.md is there.
- turtleOS — a sovereign, local-first personal AI on Discord that grew out of this practice. It runs on its own (Magic is not required) and can host Magic-authored flows: the always-on, persistent home for the practice. Not "Magic, packaged" — a sibling that stands on its own.
- About the author — the practitioner and the thinking behind the framework.
Magic is offered from alongside, not from above.
This isn't a movement, and there's no one to recruit — it's curated wisdom from a practice that works for one person, opened to anyone who finds it useful for their own journey. Fellow traveler, not founder. Take what helps, leave what doesn't, build what's yours. Some of this is well-grounded; some is still being figured out, and the open questions are part of the work.
If it resonates, explore. If it doesn't, that's fine too.
Magic is open source under the MIT License.