Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.flowstep.ai/llms.txt

Use this file to discover all available pages before exploring further.

You do not need any design experience to use Flowstep. There’s no need to know the difference between a typeface and a font, understand grid systems, or have ever opened a design tool before. Flowstep handles layout, typography, color, spacing, and visual hierarchy automatically — your job is simply to describe what you want.

​
How it works without design skills

When you type a prompt, Flowstep interprets your description and makes all the visual decisions that a designer would normally make: how to arrange elements on screen, which fonts to use, how much whitespace to add, and how to establish a visual hierarchy that guides the eye. You describe the purpose and content; Flowstep produces a screen that looks like a professional designed it.
Think of prompting Flowstep the same way you’d brief a designer. You wouldn’t tell a designer which font size to use — you’d tell them what the screen is for and what it needs to communicate. Flowstep works the same way.

​
Tips for writing good prompts

You don’t need design vocabulary to write a useful prompt. Focus on three things: the purpose of the screen, the key information it should show, and the type of product or audience. Lead with the screen’s purpose Start with what the screen is supposed to do. “Sign-up screen for a meal planning app” tells Flowstep far more than a list of UI elements. Mention the key content or actions Include the most important things a user should see or do. You don’t need to list everything — just the elements that matter most to the experience. Reference a product type or audience if it helps Mentioning the kind of product (e.g., consumer mobile app, B2B dashboard, e-commerce checkout) helps Flowstep match the right visual tone and conventions.
If your first result isn’t quite right, don’t start over — just type a follow-up prompt. Saying “make the layout more minimal” or “use a darker color scheme” is enough to steer the design in a new direction.

​
Example prompts to try

Here are a few prompts that work well, written in plain English with no design terminology: Onboarding flow for a fitness app
“First screen of an onboarding flow for a fitness tracking app. It should welcome the user, briefly explain what the app does, and have a button to get started.”
Settings page for a SaaS product
“Settings page for a B2B project management tool. Include sections for profile, notifications, billing, and connected accounts. Use a clean, professional look.”
Mobile checkout screen
“Checkout screen for a mobile shopping app. Show an order summary, a field for a promo code, and a prominent button to complete the purchase.”
These prompts work not because they use design language, but because they clearly describe the screen’s purpose, content, and context. That’s all you need.