When to use Taste Mode
Use Taste Mode when you want to create a new product UI from a text brief, such as:- a full-stack app
- a web frontend or landing page
- a mobile app
- a multi-screen game or interactive experience
- a 0-to-1 product idea where the visual direction is not decided yet
When to skip it
Skip Taste Mode when:- the project is a trivial single-screen utility, such as a basic form or very small toy app
- you already have a complete design brief with a concrete style direction, palette, type system, and page or screen list
- you already have design files, mockups, screenshots, or a style guide that should be followed directly
- you explicitly want to skip design and go straight to code
If your brief is already specific enough, Verdent Cloud can use it as the chosen direction and move directly toward page planning and build work.
How Taste Mode works
Describe the product
Start with a plain-language brief: what you want to build, who it is for, what it should do, and any mood or style references you already have.
Choose a visual direction
Verdent Cloud explores distinct design directions so you can pick the look and feel before code is written.
Plan the pages or screens
For multi-page, full-stack, or more complex products, Verdent Cloud turns the chosen direction into a page or screen plan and a plain-language product spec.
Build from the approved direction
After the direction is clear, Verdent Cloud restores the design into a working app and keeps later decisions tied to the approved design and spec.
How to use Taste Mode in Verdent Cloud
From the Cloud creation flow, describe the app you want to build instead of choosing a template. If you do not already have a concrete design direction, Verdent Cloud can use Taste Mode to help you pick one before it builds. You can keep the brief simple, but make it specific enough to guide taste decisions:- what the product is
- who will use it
- the main job it should help them do
- the pages, screens, or states you already know you need
- any tone or style references, such as editorial, playful, functional, premium, minimalist, or bold
- anything you do not want, such as generic gradients, stock-looking imagery, or a certain visual style
Example briefs
Landing page
Build a landing page for a personal finance app for freelancers. It should feel calm, trustworthy, and editorial, with a hero, feature sections, pricing, and FAQ.
Multi-screen app
Create a mobile-first habit tracker for people recovering from burnout. It should feel gentle and tactile, with onboarding, daily check-in, progress view, and settings.
Tips for better results
- Say who the product is for.
- Describe the feeling you want, not just the feature list.
- Mention known pages or screens if you have them.
- Share references or constraints early if they matter.
- Say what to avoid if you already know what would feel wrong.
- For complex products, expect to confirm the page list and product spec before the full build continues.