This week, your root system learns who you are. Your values, your work, your voice. Then it builds something real.
After this module: Your root file is written, your root system knows your life and your work, and you have built your first page.
Available April 7, 2026Video walkthrough coming with sprint launch.
Your Root System Scan
Before your system can help you, it needs to know who you are. Not your business plan. Not your target audience. You. What you believe, how you work, who you serve, what you already have.
The Root System Scan is a guided conversation that takes about 15 minutes. It walks you through all four languages and produces two things:
📄 Your root file draft
The first version of your CLAUDE.md. Who you are, who you serve, how you work, what you have, and the rules your system should follow. Written as instructions, not descriptions.
📝 Your about page draft
The foundation for your public-facing story. What you believe, what you do, who you work with, how you got here. In your voice, using your words.
💡
Why this matters
Your root file becomes the first thing your AI system reads every single session. When Claude writes your content, builds your pages, or helps you make decisions, it starts here. The deeper you go in this scan, the better everything after it works.
How it works
The scan is a conversation. It asks you about what's not working, then walks through each language (mind, heart, body, soul), surfaces your pattern, and assembles the raw material into your root file and about page. You can type or use voice.
At the end, you download your root file as a markdown file. You will use this in the next lesson when you set up your system.
If you already have Claude Code set up, you can run the same scan as a conversation in your terminal. Open Claude Code in your project folder, paste the prompt from the Root System Scan README, and work through it there. Same questions, same output, different interface.
You already have your root file draft from the scan. Now we go deeper.
The scan gave you the shape of who you are across all four languages. The onboarding conversation takes that shape and fills it in with real detail: your actual methodology, your specific offerings, your brand colors, your work rhythms, the tools you use, who you want to reach, and what you are building toward. This is where your root system goes from "knows who you are" to "knows how to work for you."
How it works
Open your terminal, navigate to your project folder (cd ~/sarah-coaching or whatever you named yours), and type claude to start Claude Code. Once you are in, type /onboarding and press enter.
If /onboarding does not work
Some setups do not support slash commands. If that happens, just type: "Run the onboarding skill from .claude/commands/onboarding.md" and Claude will find it and walk you through the same conversation.
If you completed the Root System Scan, paste your downloaded root file when prompted. Claude will use it as a starting point so you do not repeat yourself. If you skipped the scan, that is fine too. Claude will ask everything from scratch.
The onboarding walks through five sections. Each one goes deeper than the scan did:
Soul
Your values, purpose, reflective practice, what your ideal day actually looks like
Mind
Your methodology, specific offerings, ideal client in detail, 12-month vision
Heart
Your voice, how you actually talk, where your people find you, how you build trust
Body
Your work rhythms, tech stack, brand elements (colors, fonts), what you want tracked
Plus: The Big Picture
At the end, Claude asks why you are here and what would make this sprint worth it. This becomes the filter for everything your system suggests and builds.
This is not a form. It is a real conversation, 30 to 45 minutes depending on how deep you go. Claude asks, listens, mirrors back what it heard, and then writes your system files in real time. The deeper you go, the better everything works from here.
What it creates
As you answer each section, Claude writes files into your project. By the end, you will see a receipt showing everything it created:
CLAUDE.md ✓ Your root file (final version)
context/memory/fact/identity.yaml ✓ Values, purpose, philosophy
context/memory/fact/business.yaml ✓ Methodology, offerings, ideal client
context/memory/fact/preferences.yaml ✓ Voice, communication style
context/memory/fact/brand.yaml ✓ Colors, fonts, visual identity
context/memory/fact/goals.yaml ✓ 12-month vision, sprint goal
context/memory/fact/current-state.yaml ✓ Rhythms, tracking, accountability
context/memory/fact/tech-stack.yaml ✓ Tools and platforms
mind/content/voice-guide.md ✓ How you sound in writing
heart/crm/seed-contacts.md ✓ Your existing network
The scan gave you one file (your root file draft). The onboarding creates ten. Together, they mean your root system knows your values, your methodology, your voice, your rhythms, your tools, your goals, and who matters to you. That is the foundation everything else builds on.
What happens after onboarding
Once your onboarding is complete, your root system gets better every day. Here is what that looks like:
💡
Daily check-ins
Every time you open Claude Code and say good morning, your root system checks in with you. How are you feeling? What are you working on? What is your energy like? These check-ins get logged. Over time, they reveal your patterns.
💡
Reflective practice
If you have a reflective practice (journaling, meditation, pulling a card, prayer, nature time), your root system can support it. Tell it what you do. It will prompt you, log your reflections, and track consistency. This is private. It stays in your root system.
💡
Voice refinement
The more you interact with your root system, the more it sounds like you. When it writes something that feels off, tell it. "Too formal." "I would never say that." "More like how I would text a friend." It learns. In Module 2, you will understand exactly how.
Your root system knows you now. Time to see what it can do with that knowledge.
The scan gave you an about page draft. The onboarding deepened everything. Now you turn all of that into a real page you can actually publish.
How it works
In Claude Code, type /about-page-builder and press enter (or say "Run the about page builder skill from .claude/commands/about-page-builder.md" if slash commands do not work). Claude reads everything it knows about you (your root file, your identity, your business, your voice, your brand) and builds a complete web page. No templates. No fill-in-the-blanks. A real page written in your voice, using your colors and your words.
Before it builds, it will show you what it knows and ask for anything missing: your photo, your logo, specific colors or fonts you want, any design inspiration you have in mind. Then it builds.
What you get
A single HTML file, ready to open in your browser. It includes:
1A hero section with your name, what you do, and your philosophy
2Your story written in your voice, from what you shared in the scan and onboarding
3Your methodology broken into clear steps or pillars
4Who you work with and the transformation you deliver
5Your values and what you believe
6A way to connect with your contact details and social links
The page uses your brand colors, your font choices, and responsive design that works on any device. It is a complete, production-ready page you can deploy or iterate on.
Why this matters
Most people agonize over their about page for weeks. They stare at a blank page, write something generic, hate it, start over. You already did the hard part. You figured out who you are in the scan and the onboarding. This step just makes it visible to the world.
The page lives at mind/website/about/index.html in your project. Open it in your browser. Read it. If something feels off, tell Claude. "This part does not sound like me." "Make the story shorter." "I hate this section." It will rewrite it. This is your page. It should feel like you.
💡
The real test
Share it with someone you trust. Not for feedback on the design. For their reaction. "Does this sound like me?" That reaction is the proof that your root system works.
💡
Deploy when ready
This page is yours. You can put it on your existing website, host it on its own domain, or just keep it as a working draft. There is no pressure to publish it right now. It will be here when you are ready.