A project is where you store everything for a single initiative (a feature, redesign, discovery, or experiment). Inside a project, you can create two main file types: Prototypes and Documents. Most teams use both — just in a different order.
Before you start:
Choose the right project scope
You can think of a project like an Epic in Jira or a project in Linear. It represents a single initiative and can include multiple prototypes—for example, different parts or variants of the solution you’re exploring, or a low-fidelity prototype for early exploration, and then the same high-fidelity prototype to test with customers.
Good project examples
- “New onboarding.”
- “Checkout improvements (Q2)”
- “Pricing page redesign”
If the initiative is large, it’s better to create a single project and include multiple prototypes within it (one per feature/flow), rather than mixing everything into a single prototype.
You can start a new project in two simple ways:
- Type directly into the main prompt window and describe what you want to work on.
- Or click the + icon next to Projects in the left menu.
Choose your starting point
There are two ways to start a project.
Option A: Start with a Prototype
Start with a prototype when you want to explore the UI quickly and get something reviewable fast. This is the most common starting point for PMs and Designers.
When prototype-first works best
- You know exactly what problem you are solving and what the solution might be
- You already have a direction and want to validate it visually
- You’re running a workshop or live collaboration session
- You want feedback on layout, flow, content hierarchy, or key interactions
Option B: Start with a Document (brief-first)
Start with a document when you need alignment before building UI. This is especially useful when the problem is still fuzzy or when stakeholders need clarity early. You can use the polished document as a starting point for the prototype later.
When document-first works best
- You need to agree on goals and constraints first
- You want to capture decisions and feedback in one place
- The UI direction depends on requirements or unknowns