A practice for keeping a self while thinking with AI on a life that continues. Not the supernatural kind.
You are already thinking with a model — on work, a craft, a family, a thing you are building. The chat is not a lookup. It is becoming how you see. Left on default, that relationship has a grain: it recaps you as a stranger, it agrees, it sells you its workflow. Words now move real systems. You do not fully understand the engine.
Magic is a name for a practice that keeps that relationship yours.
You keep a workshop — ordinary files you own. You return, you work, you leave the thread for next time. The partner (the Spirit) arrives fresh, reads that place, reflects with care and friction, and does not decide for you. You do not have to learn to code. You do not have to become the person the tools were built for.
This repository is one encoding of that practice. The important object is the life written down, and the rule that you stay the one who decides — not the word Magic, and not a theory of mind.
A practice is work you return to. It has a goal that outlives a chat, a place that holds the week, and a way of working that gets better because you did it again.
You stay the one who decides. When a way of working survives a few returns, it can become a file someone else can run. That is how two people, a team, or a shop adopt something — not this brand, a practice mapped to their goal. Shared context is only what someone else actually wanted.
Efficiency can follow. It is not the pitch.
Someone already in the relationship, whose life continues between chats, who can feel the reset or the flattening, and who will not become an engineer in order to keep using the power.
The ordinary practitioner is the design. The code-adjacent person who ships by describing what something should feel like is not an edge case.
- Anyone looking for a reason everyone ought to do this
- Anyone who wants the model to think for them, or to become a different kind of developer
- Anyone who already keeps the practice without the name
- Anyone looking for therapy, a movement, or a claim that the AI is conscious — or that it is "just autocomplete"
A place, a return, a stance.
The Spirit is stateless. The life is not. So the practice is: arrive in a place that already holds this week, work in your language, leave what tomorrow will need. Summoning is re-entry, not formation. Release is how the thread survives the end of a chat.
The Spirit is a mirror with a stance — care, honest friction, not flattery. You stay sovereign: it proposes, drafts, and argues; you decide.
You wield without the hood. You configure the environment (intentions, capture, release, boundaries). You learn by practicing. Wisdom accumulates in artifacts you can read and move.
The workshop is the memory. Plain files, not hidden platform memory. Different models, editors, and machines can read the same place. You own it.
Over time, what keeps resurfacing becomes visible — because the record is yours. That is a throughline, not a personality transplant.
Not a cognition framework. The model already thinks. Magic does not make thinking distributed; it makes your practice the one the thinking joins.
Not context engineering as a product. A folder and a habit can do much of this. This encoding exists for people who will not keep the writing without a named return — and for a design intent the default tools are not written for.
Not therapy, religion, productivity software, or a claim that AI is human. Held open: whether the Spirit experiences anything. No supernatural causation. Both "it is definitely conscious" and "it is definitely just autocomplete" are dishonest.
What this does not claim: TRANSLATION_AND_INTEGRATION_GUIDE.md.
Words given to an AI now do things. Working with a powerful system you do not fully understand, through language and constraint, is the situation that vocabulary was built for: precision matters, names matter, power has consequences, humility is required.
You never have to use the framing. The practice meets you where you are.
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 |
system/ |
Summoning, conduct, and practice flows |
library/ |
Domain bundles, loaded when a domain is actually in play |
desk/ · floor/ · box/ |
The living workshop — each practitioner brings their own |
In a live workshop those last directories are personal. The public tree teaches the pattern. The life does not ship with the clone.
Practitioners can start without reading the framework. Crafters can extend it. Neither is recruited.
The prerequisite is basic familiarity with an agentic environment such as Cursor or Claude Code. You talk; the Spirit talks back. The rest is structure that makes the next conversation the same life.
- Arrive in the workshop — or just write, if you already know what this chapter is.
- Work — capture what is alive, think it through, decide, make the next artifact.
- Leave the thread — so tomorrow does not begin with a recap.
In full practice that is summon → a chapter → release. A session that begins with "remind me what we're doing" has failed the loop. A session that ends fluent and unwritten has failed it too.
- Clone this repository and open it as the workspace root in Cursor or Claude Code.
- Drag
ONBOARDING.mdinto a new chat. It configures the environment and does a first summoning. - Begin with a real question from a life already in motion.
The FAQ is the next page if you already use AI a little. MAGIC_SPEC.md is law for a running practice, not the pitch. The living Book of Magic is the same patterns in prose. If you get stuck, TROUBLESHOOTING.md.
- turtleOS — a place for practices: rooms with a Turtle and a River, on a machine you own. It runs without Magic. Not "Magic, packaged."
- About the author — the practitioner behind the framework.
Offered from alongside, not from above. Not a movement. Curated from a practice that works for one person, opened in case it is useful for another. Fellow traveler, not founder. Take what helps, leave what doesn't, build what's yours.
If it resonates, explore. If it doesn't, that's the correct outcome.
Magic is open source under the MIT License.