Onboarding

First-launch and new-project flows designed to get you from "just installed" to "editing real cases" quickly.

#Welcome screen

Three entry points:

1. Create a new project - name it, pick a starting field schema, and Kensa scaffolds the folder (.tms/, suites/, CLAUDE.md, README.md), optionally running git init.
2. Open an existing project - point at any folder with a .tms/ directory.
3. Import from another TMS - launches the import wizard.

A recent projects list offers quick-open and "Clear all".

#New-project wizard

Choose a project name and a starting schema. The structure designer is available right here, so you can shape your case fields before you start filling in cases.

#Demo seed

An Open Demo Project button loads an in-memory sample project with example cases and a live suite tree, so you can explore every part of the UI without committing a folder to disk first.

#Soft onboarding for AI plugins

Right after you create an on-disk project, Kensa gently surfaces the AI-plugin setup dialog so your agent can be wired up from the start. In-memory/demo projects skip this (there's nothing to write).

#Tutorial overlay

On the first project load, a non-blocking tutorial overlay floats callouts pointing at the key UI regions - suites, the editor, the terminal (and $TMS_CASE), and settings. It:

• doesn't block interaction (you can click around underneath it),
• hides callouts whose panel is collapsed,
• is dismissible via × or Esc, and
• never reopens once dismissed.

#Polished cold start

The app window starts hidden with a themed background and shows a static splash (logo + spinner) while state rehydrates - so light/dark matches from the first painted frame with no white flash.