← Library05 Templates

template · product · ui-ux · web · vercel

Web Product Discovery

05 Templates/Web Product Discovery.md

Web Product Discovery

Use this before building or redesigning any website or web application. The AI assistant must ask the owner these questions before deciding navigation, visual language, product identity, or deployment naming.

Required owner questions

1. Product identity

  • What is the product name?
  • What one-sentence promise should appear on the home screen?
  • Should an abbreviation or symbol appear in the logo?
  • What tone should the product use: professional, playful, editorial, technical, calm, or another direction?

2. Audience and privacy

  • Who will use it: only the owner, invited users, customers, or the public?
  • Which content is public, private, or shared?
  • Is sign-in required?
  • Which actions require confirmation or elevated permission?

3. UI/UX direction

  • Which saved design mode in design should lead the product?
  • Which reference screens or products should influence it?
  • Light, dark, or both?
  • Mobile-first, desktop-first, or equal priority?
  • English, Myanmar, or bilingual?
  • Which accessibility or device constraints are especially important?

4. Navigation and menu functions

Ask the owner to select and order the actual menu destinations. Do not invent the menu from generic conventions.

Possible destinations:

  • Home
  • Search
  • Library
  • Graph
  • Projects
  • Learning
  • Prompts
  • AI Chat / Ask
  • Quick Capture
  • Bookmarks
  • Recent
  • Profile
  • Settings

For every selected destination ask:

  • What user job happens here?
  • What is the primary action?
  • What should be visible before opening it?
  • Is it a top-level menu item, secondary page, or contextual action?
  • Should it appear on phone bottom navigation, desktop sidebar, or both?

5. Features and data

  • Is the product read-only, capture-only, or fully editable?
  • What is the source of truth?
  • How should data synchronize?
  • Is offline use required?
  • Are AI chat, semantic search, notifications, analytics, sharing, or export required now or later?

6. Vercel and domain naming

  • What should the Vercel project be named?
  • What preferred .vercel.app alias should be requested?
  • Is there an existing custom domain?
  • Is this a preview or production release?
  • Which Vercel account/team should own it?

Never accept a generic accidental name such as public, app, or a generated color-number alias as the final product URL without asking the owner.

Selection flow

flowchart TD A[Product idea] --> B[Choose name and promise] B --> C[Choose audience and privacy] C --> D[Choose UI and UX direction] D --> E[Select menu destinations] E --> F[Define function of each destination] F --> G[Choose data, editing, AI, and offline features] G --> H[Choose Vercel project and link name] H --> I[Create flowchart and screen map] I --> J[Owner approves] J --> K[Build one vertical slice] K --> L[Test mobile, desktop, and accessibility] L --> M[Deploy preview] M --> N[Owner approves production]

Decision record

product_name:
product_promise:
audience:
privacy:
ui_direction:
theme:
language:
mobile_priority:
menu:
  - name:
    user_job:
    primary_action:
    placement:
features_now:
features_later:
source_of_truth:
sync:
offline:
vercel_team:
vercel_project_name:
preferred_vercel_alias:
custom_domain:
release_target: preview

Rule for AI coding assistants

Before creating or changing a website, ask the owner to choose the product name, UI/UX direction, menu destinations, function of every destination, privacy boundary, and Vercel project/link name. Show the approved navigation and primary user journey as a flowchart before implementation. Do not deploy production until the owner approves the flow and preview.

Related

Knowledge connections