Create from a prompt
Describe the interface, its content, and what it should do.
Give the request a job
Explain who will use the interface and what they need to accomplish. Specific content and behavior are more useful than a list of style adjectives.
Start with a component, a page section, or a larger interface. Keep the request bounded enough that you can inspect what it creates.
Include what matters
- Content: realistic labels, examples, values, and the primary action.
- Behavior: what happens when someone clicks, types, selects, or submits.
- States: the empty, loading, error, and success states you need.
- Constraints: intended width, responsive behavior, visual direction, and any required library.
Start with Tenor Auto
Tenor Auto chooses a model for your request. Use the model picker to choose an available alternative.
New text-only UI interfaces use the bundled shadcn foundation by default. Name another library when it is a requirement; follow-up edits preserve the component’s existing foundation.
Build an appointment card for a dental clinic. Show the date, time, clinician, and location, with Reschedule as the primary action. Include a compact mobile layout and a confirmation state.
Refine the first pass
Test the result before expanding it. Check the information and behavior, then refine hierarchy, spacing, and visual tone.
If the direction is wrong, describe the largest mismatch. A focused correction is easier to judge than another broad redesign.