The root system is a folder of files on your computer. Grok opens that folder the same way Claude Code does. Claude Code stays what the course teaches. Grok adds pictures, short video, and live X in the same sitting.
A root system is files: the root file, the rules, the skills, the memory, the pages. Any tool that can open a folder and follow English instructions can work in it.
DIY ships with Claude Code, and the course walks that path end to end. Grok is how you see that the files themselves are yours. The home for this family of pages is Claude Code, chat, and Projects.
These are the things that are true in the same conversation that is already inside your folder. Each one is from Grok's own docs, or from this page being written here.
The folder
Grok Build reads the root file, the rules, the skills, and the pages. You open the folder. The system is already there.
Pictures
Ask for a picture and it lands as a file you can open. This page's image test ran in the same session that wrote the HTML.
Moving pictures
Grok can make a short clip, typically up to 15 seconds. Real, documented, and not a film studio. Useful for a still that needs to move.
The live world
Grok searches the web and X in the same product. Claude Code can browse. First-party X search is the part Grok carries on its own.
Yes. You point Grok at your system folder, the way you would point Claude Code at it. It reads the root file first, then the rules and the skills, then it can write, edit, and run the same work.
This page is that happening. It was written in Grok, inside the live system folder, using the website design skill that already lived there.
The tool is the conversation. The system is the files. 🧠
The root file, the rules, the skills, the memory, the daily logs, the pages on the site, the CRM rows. Those are files and accounts in your name.
Grok already knows how to read a CLAUDE.md and the skill files next to it. You open the folder. The system is already there.
What you save in one session is sitting there for the next one, whichever tool opens it. ❤️
The start command. You open the folder, then start Grok there.
cd ~/your-system-foldergrok
A few things in the system still assume Claude Code. Some install guides say "open Claude". Some automatic checks were wired to Claude's hook system. The course videos walk the Claude path.
Writing a page, logging a contact, changing a price, making a picture: that conversation is the same sitting.
Yes. Ask for a picture in the same conversation that is already reading your files. The file lands locally, next to the rest of your system.
Brand pages and YouTube thumbnails with exact Karla type still get built as HTML, because the letters have to be the real letters. The picture tool is for photographs, plates, and edits of a real photo you already have.
Short video is the same family: seconds, not a filmed session. 🎥
No. Claude Code is the default setup, the one DIY ships with, and the one the course walks end to end. Built For You starts on that same path, and it can be built on any model if we agree.
Grok is bonus proof that the files travel. The course stays one path: Claude Code in week one.
The line the install already uses: this is what the course teaches; any capable AI coding tool works too.
Because that is the tool this system was built in, every day, for seven months. The skills, the guides, the corrections after things broke in front of real people: they were written in that conversation.
The architecture was files on purpose, so the tool can change. Claude Code is today's default. The folder is what you keep if the default moves. ✨
They load. Grok reads the root file, the rules, and the skill files. Say "good morning" and it still knows to follow the morning protocol. Ask it to build a page and it still has to read the design system first.
Some automatic gates were written for Claude Code's hook system: the voice check after an edit, the join-link check before a deploy. In Grok those files are still there. A few of them wait to be asked, rather than running themselves after every save.
If a check matters for a ship, ask for it. The skill is in the folder.
No. The files sit on your machine. Open them in Claude Code on Monday and Grok on Tuesday. What you write in one is sitting there for the other.
Your site, your database, and the emails that go out live on accounts in your name. They keep serving whether anyone has a chat window open. 💪
If you already have the Repo(sitory) on your computer, open that folder and start Grok there. Start it in the system folder, so it loads the root file and the skills.
cd ~/your-system-foldergrok
If you do not have the files yet, start with the free Service Map. The course still teaches the Claude Code install first. Any capable AI coding tool works too.
The home for these pages is Claude Code, chat, and Projects. This one is the Grok sibling.
Grok is bonus proof that the files travel. The course stays one path: Claude Code in week one.
The course
DIY ships with Claude Code. The videos walk that path. Built For You starts there too, and it can be built on any model if we agree.
The gates
Voice checks and join-link checks were wired to Claude Code. In Grok those files are still there. A few of them wait to be asked, rather than running after every save.
Memory
Claude Code keeps memory on as a habit of this system. Grok's extra memory layer is off until you turn it on. The memory files in your folder still load either way.
When you close the laptop
Grok Build can loop a prompt while a session is open. Laptop-off routines and Cowork-shaped handoff live in Claude's stack. Your site and CRM keep running on your own accounts either way.
The Service Map costs nothing and the builds hold nothing back. When you want the Repo(sitory) and the teaching in order, that's DIY at €550. When you want it standing up and running in your business, that's Built For You.