Phase 3 — Create project

There are three entry points to project creation:

Dashboard → ”+ New project” quick action → /projects/new (blank).
Project list → ”+ New project” button → /projects/new (blank).
Sample gallery → click a sample → /projects/new?sample=<id> (prefilled name + description + useAiScaffold checked).

All three land on the same wizard.

The 3-step wizard

graph LR
  classDef step fill:#eef0ff,stroke:#4f46e5,color:#0a0a0a;
  S1[Step 1<br/>Name + description]:::step --> S2[Step 2<br/>Profile picker]:::step --> S3[Step 3<br/>Tree mode + AI scaffold]:::step --> Done[Project created<br/>→ workspace or hub]

Step 1 — Name + description

Two inputs:

Project name — required. Free text.
Short description — optional. Multi-line. Becomes the idea text for the AI Decompose Wizard if you opt into AI scaffold in Step 3.

If you arrived via ?sample=<id>, both are prefilled from SAMPLE_PRDS[id] and useAiScaffold is auto-set true.

Next is disabled until name is non-empty.

Step 2 — Pick profiles

A profile narrows AtomPRD’s 26 atom kinds to a methodology-specific subset. Profiles list is loaded from GET /profiles (system + org-cloned).

The default system profile is atomprd-v1 — full 26 kinds. You can pick multiple profiles; the project will accept atoms valid in any selected profile.

Each profile card shows:

Name + system badge (read-only system profile) or no badge (org clone, deletable).
Description.
Atom-kind count.

Common picks:

atomprd-v1 — full 26 kinds. Good default.
Custom clone — see Profile management below.

Next is disabled until ≥ 1 profile selected.

Step 3 — Tree mode + AI scaffold

Three layout modes for the project’s decomposition trees:

Mode	Effect
One tree (unified)	All profiles share one tree. Filter by profile inside. Best for solo + small teams.
Tách cây theo profile	One independent tree per profile. Cross-tree relations link them. Best for large teams with separate PM / DevOps decomposition.
Custom (advanced)	Create trees manually after project creation. Full control.

Plus a single checkbox:

✨ Use AI to scaffold modules & features — After creation, the Decompose Wizard opens with your description pre-filled — pick an archetype and generate 5-7 modules in ~90 seconds.

Default checked when arriving via a sample, otherwise checked. Uncheck for a fully manual project.

Create project → API POST /projects then POST /projects/:id/trees/seed (split because tree seeding is in a separate module). On success:

If useAiScaffold → navigate to /projects/:id/workspace?wizard=1 (Decompose Wizard auto-opens).
Otherwise → navigate to /projects/:id (project hub).

Project hub — `/projects/:id`

After creation (or whenever you navigate to a project), you land at the project hub:

┌────────────────────────────────────────────────────────────┐
│ 🟦 Habito  · draft · 1 profile · tree mode: unified         │
│                                                              │
│ Mobile habit tracker with streaks, social challenges, and …│
│                                                              │
│   [ History ]   [ Open workspace → ]   [ ? ]                │
└────────────────────────────────────────────────────────────┘

┌── PageGuide ─────────────────────────────────────────────┐
│ ✨ Project hub                                            │
│ This is your project's command center. From here you …  │
│  ① Open Workspace  ② Take a snapshot  ③ Connect AI agent │
│  ④ Export bundle                                         │
└──────────────────────────────────────────────────────────┘

┌── 4 destination cards ─────────────────────────────────┐
│  ▣ Workspace (PRIMARY)        ▣ Tree (legacy)          │
│  ▣ Documents (W10 — soon)     ▣ Settings (soon)        │
└────────────────────────────────────────────────────────┘

The hub centralizes per-project actions:

Avatar — click to upload / crop a per-project image. Falls back to a hue derived from project ID.
Status / profile / tree mode — read-only summary line.
History → /projects/:id/history (Phase 5).
Open workspace (primary CTA) → /projects/:id/workspace (Phase 4).
Workspace destination card is the highlighted entry; “Tree (legacy)” exists for backward compatibility but is deprecated.

The hub PageGuide enumerates the four key project actions: open workspace, snapshot, connect MCP agent, export. Dismissible per-(user, project) via localStorage:atomprd:page-guide-dismissed:project-detail.

Profile management — `/profiles`

Separate page accessible from the top nav. Lists all profiles visible to the current org:

System profiles — read-only. system badge. Cannot delete.
Org clones — created from system profiles via the 📋 copy button. Editable + deletable.

Clone flow: pick a system profile → click 📋 → API POST /profiles/clone with auto-named <source>-<timestamp>. The clone shows up immediately. Edit it later (UI for atom-kind editing is wired into the clone’s detail page — outside the scope of this user flow).

Why clone? When your org needs custom decomposition rules (e.g. add a compliance atom kind for fintech, or remove host_domain for mobile-only projects). System profiles never change beneath you; clones are stable per-org.

The /profiles page itself shows a PageGuide describing the methodology-preset model. See RFC-005 — Profile system for the underlying spec.

What just happened (server side)

Step	API	Side-effect
Step 1-2-3 input	(no API yet)	Local state.
Click Create	`POST /projects`	Project row + status `draft`.
(chained)	`POST /projects/:id/trees/seed`	One or more tree rows depending on `treeMode`.
Navigate	(client)	`/projects/:id/workspace?wizard=1` or `/projects/:id`.

If useAiScaffold was checked, the workspace renders with wizard=1 and the Decompose Wizard auto-opens — that’s where Phase 5 begins.