Your first 30 minutes

Starter Project and Onboarding Behavior

First-Run Flow

KazaKit’s onboarding is designed to create a real workspace rather than a generic demo.

The guided flow includes:

1. Welcome
2. Creator type
3. Project name
4. Workspace preview
5. Theme
6. Creation/loading

The quick flow omits the detailed workspace preview.

What a Starter Project Can Include

Depending on project type, the starter workspace may create:

• a project identity;
• a creator-aware checklist;
• initial Library documents;
• a scratchpad Quick Note;
• a real milestone in Chronicle/Calendar;
• due dates on selected starter tasks;
• a recurring task where it makes sense;
• an output-aware goal for writing-heavy projects.

Example: Game Starter

A Game starter can include work such as:

• Define your core loop
• Sketch the first playable moment
• List your top three mechanics
• Set your first playtest milestone

It can also create Library foundations such as:

• Game Design Doc
• Lore & Story
• Mechanics
• Technical Docs
• Marketing
• Creative Direction

Onboarding Principle

Starter content is scaffolding, not sample content the user must preserve. The user should replace it with the real structure of the project.

Suggested “First 30 Minutes” Guide

1. Choose your language.
2. Select the closest project type.
3. Name the real project you want to work on.
4. Review the starter workspace preview.
5. Choose a theme.
6. Open Project Overview.
7. Replace one starter Library page with real project information.
8. Capture one unfinished thought in Quick Notes.
9. Create or choose a Moodboard and send the note into it.
10. Promote one clear next action into Workshop.
11. Add a due date or milestone.
12. Start a 15- or 25-minute focus session attached to that work.
13. Return to Today to see how the project now has structure.

This guide demonstrates the product’s connected loop more effectively than a tour of every button.