How Modus works
The hub model, the seven chapters, and how they unlock.
Projects are born in Chats: you talk an idea through, hit Create project, and the conversation's brief becomes the seed of the build.
From that point on, everything runs from a single hub: the project's home screen and the spine of the build. It holds seven chapters plus a Deploy action that take you from a written spec to a live, token-backed dApp, each building on the last. Learn this model and you know how all of Modus works.
The hub
Open a project and you land in the hub. It has three tabs:
- Overview: a featured Up next card marking the chapter to work in, above the chapter rows.
- Activity: everything that's happened on the project, grouped by chapter.
- Library: the project's uploaded files and assets.
Each chapter card shows that chapter's live state, whether a PRD excerpt, screen thumbnails, a code preview, or deploy status, so the hub reads like a dashboard, not a menu.
The seven chapters
| # | Chapter | What it does |
|---|---|---|
| 01 | PRD | The spec. Problem, users, scope, architecture, pages, journeys: AI drafts it, you edit it. |
| 02 | Design | Generates every screen from the spec. Pick a design system or build from scratch. |
| 03 | Code | A browser IDE. Production front + back end in your stack, built by chatting with Modus. |
| 04 | Docs | README, architecture, API, runbooks, generated from your code and kept in sync. |
| 05 | Deck | A pitch deck built from your PRD and design. Edit any slide; export to PDF or PowerPoint. |
| 06 | Token Launcher | Launch the project token: name, supply, chain, taxes, launch style, then deploy. |
| 07 | CMS | A content backend for anything structured: blogs, pages, changelogs. Rolling out soon. |
Deploy isn't a chapter card: it's the ship action in the hub's top bar (and in the Code chat), always available; it pushes your frontend to Vercel or Netlify.
How chapters unlock
Most chapters are open from the start; a couple wait for the work they depend on.
PRD, Design, and Code are open from project creation: the approved spec is Design's and Code's recommended input, not a gate. Approving the PRD opens the Token Launcher; your first build turn in Code opens Docs and Deck. CMS is rolling out: when it ships, it activates with a Better i18n connection.
Until a chapter unlocks, its card sits locked and says what to finish first; once open, it moves through ready → in progress → approved, styled the same on every card so the hub stays scannable. The exact rules live in Chapters & unlocks.
Build it → run it
The chapters are the build half. Once your company is live, the run half lets you hire AI employees to operate it across community, treasury, marketing, and ops. That half is rolling out; see Hiring your crew.