# Screen types

Guidance per screen type, the same as the SaaSFrame MCP's `design_guide` tool. With the MCP, call `design_guide(for: "<key>")` to also get benchmarks measured on real SaaS pages of that type (typefaces, text sizes, button height, radii, content width) and the UX patterns those screens use most.

## Landing page

Key: `landing-page` · website page · also covers: hero-section, features-page, feature, call-to-action, product-screenshot

**Goal.** Make a visitor understand what the product does and for whom within the first screen, then give them one next step.

**Decide first**
- What is the single action: start free, book a demo, join a waitlist?
- What proof exists: the product UI itself, customer logos, numbers, a quote?

**Do**
- The headline says what the product does in plain words. Keep cleverness for the subheading.
- Show the real product early: an actual screen or a focused fragment of it explains more than an abstract illustration.
- One primary call to action, repeated at the end of the page with the same label.
- Give each section one job (explain a capability, prove it, answer an objection) and drop sections with none.
- Vary the section layouts: a page made only of three-column card grids reads as a template.

**Avoid**
- A headline that would fit any SaaS
- Feature grids of icon, title and two lines with nothing shown
- Invented customer logos or metrics

**References**
- With the MCP: `search_sections(pattern: "hero-section")`, `search_screens(category: "landing-page")`, `search_sections(pattern: "feature")`
- Without: https://www.saasframe.io/md/categories/landing-page (design guide, FAQ and three examples), then open each example's page.

## Pricing page

Key: `pricing-page` · website page · also covers: pricing, plans, comparison-page

**Goal.** Let a buyer find their plan and its price in seconds, and trust what they will be charged.

**Decide first**
- How many plans, and which one should most buyers pick?
- Billing periods, per-seat or flat, free plan or trial?

**Do**
- Plans side by side with the price as the largest element of each card; state the unit (per month, per seat) next to it.
- Mark one recommended plan, by emphasis rather than by adding noise to the others.
- Each plan lists what it adds over the previous one, not the full feature list repeated.
- If there is a monthly and yearly toggle, show the saving and keep both prices easy to compare.
- Put the detailed comparison table and the billing questions below the plans, not instead of them.

**Avoid**
- Hiding the price behind "contact us" on every plan
- Feature rows that differ only in wording
- A toggle that changes prices without showing what changed

**References**
- With the MCP: `search_screens(category: "pricing-page")`, `search_sections(pattern: "pricing")`, `search_screens(query: "yearly", category: "pricing-page")`
- Without: https://www.saasframe.io/md/categories/pricing-page (design guide, FAQ and three examples), then open each example's page.

## Dashboard

Key: `dashboard` · product screen · also covers: analytics, metrics, graph

**Goal.** Answer "how are things going, and what needs me?" at a glance, then lead to the place where the user acts.

**Decide first**
- Which 3 to 5 numbers does this user check every time?
- Which items need action today?

**Do**
- Lead with the few numbers that matter, each with its comparison (previous period, target). A number alone says little.
- Put what needs action above what is merely informative.
- Choose the chart from the question: trend over time, comparison across items, share of a total. One question per chart.
- Every number and row links to its detail.
- Design the first-day state: a new account has no data, so the dashboard must guide the setup instead of showing zeros.

**Avoid**
- A row of identical metric cards followed by charts chosen for looks
- More than one accent color competing for attention
- Charts without axis labels or time range

**References**
- With the MCP: `search_screens(category: "dashboard")`, `search_screens(category: "analytics")`, `search_screens(pattern: "metrics", type: "product")`
- Without: https://www.saasframe.io/md/categories/dashboard (design guide, FAQ and three examples), then open each example's page.

## Settings

Key: `settings` · product screen · also covers: settings-preferences, integrations, upgrading, billing-subscription

**Goal.** Let the user find one setting, change it with confidence, and know that it was saved.

**Decide first**
- How are settings grouped: account, workspace, billing, integrations?
- Does a change save at once or with a save button? Keep one rule across the section.

**Do**
- Group by what the user is trying to do, with a persistent sub-navigation once there are more than a handful of groups.
- Each setting: a label in the user’s words, a one-line explanation of the effect, then the control.
- Confirm that a change was saved, where the change happened.
- Separate destructive actions (delete workspace, remove member) at the bottom, with a confirmation that names what will be lost.
- Show the current plan and its limits where they constrain a setting.

**Avoid**
- One long undivided form
- Toggles whose effect is unclear until tried
- A save button far from the fields it saves

**References**
- With the MCP: `search_screens(category: "settings")`, `search_screens(category: "integrations")`, `search_screens(pattern: "billing-subscription")`
- Without: https://www.saasframe.io/md/categories/settings (design guide, FAQ and three examples), then open each example's page.

## Onboarding

Key: `user-onboarding` · product screen · also covers: account-setup, welcome-screen, discovery-questions, product-tour, wizard, progress-indicator, invite-team-members, invite-friends

**Goal.** Take a new user to the first moment the product is useful to them, in as few steps as that needs.

**Decide first**
- What is that first useful moment for this product?
- Which questions actually change what the user sees next? Ask only those.

**Do**
- One decision per step, with the progress visible and a way back.
- Use the answers at once: the next screen should already reflect them.
- Let optional steps (invite teammates, connect a tool) be skipped, and offer them again later in context.
- Prefer doing the real task with guidance over a tour of the interface.
- End in the product with something already there (a first project, sample data), never on an empty screen.

**Avoid**
- Asking for information that is never used
- A carousel of feature slides before the user can do anything
- Blocking progress on a team invite

**References**
- With the MCP: `search_flows(query: "onboarding")`, `search_screens(category: "user-onboarding")`, `search_screens(category: "account-setup")`
- Without: https://www.saasframe.io/md/categories/user-onboarding (design guide, FAQ and three examples), then open each example's page.

## Sign up and login

Key: `sign-up-flow` · product screen · also covers: login, signup, verification, social-login

**Goal.** Get the person into the product with the least typing, and make every failure recoverable.

**Decide first**
- Which sign-in methods: email and password, magic link, Google, SSO?
- What must be asked now, and what can wait until onboarding?

**Do**
- Ask for the minimum: every extra field costs sign-ups.
- Offer the single sign-on options the audience already uses, above or beside the email form.
- Say the password rules before the user types, and validate as they go.
- Error messages name the problem and the fix, next to the field.
- On the verification step, show which address the code went to, with resend and change-address options.

**Avoid**
- A confirm-password field without a show-password option
- Generic "something went wrong" errors
- Marketing content competing with the form

**References**
- With the MCP: `search_flows(query: "sign up")`, `search_screens(category: "sign-up-flow")`, `search_screens(category: "login")`
- Without: https://www.saasframe.io/md/categories/sign-up-flow (design guide, FAQ and three examples), then open each example's page.

## Empty state

Key: `empty-state` · product screen · also covers: success, success-state, 404-page

**Goal.** Turn a screen with nothing in it into the start of the task.

**Decide first**
- Why is it empty: first use, a search with no result, everything done, an error?
- What is the one action that fills it?

**Do**
- Say what will appear here and why it is worth having, in one or two lines.
- One primary action that creates the first item; offer an import or a sample when creating is long.
- Keep the surrounding layout (navigation, headers, filters) so the user sees where content will live.
- For "no results", say what was searched and offer to clear the filters.

**Avoid**
- A large illustration with a vague sentence and no action
- The same empty state reused for first use and for no results

**References**
- With the MCP: `search_screens(category: "empty-state")`, `search_screens(pattern: "empty-state", type: "product")`
- Without: https://www.saasframe.io/md/categories/empty-state (design guide, FAQ and three examples), then open each example's page.

## Table and list

Key: `table` · product screen · also covers: comparison, filter, search, details

**Goal.** Let the user find rows, compare them, and act on one or many.

**Decide first**
- Which column identifies a row, and which columns are compared most?
- Which actions apply to one row, and which to a selection?

**Do**
- The identifying column comes first and stays visible; numbers are right-aligned in a tabular figure style.
- Search, filters and sort sit above the table and show what is currently applied.
- Row actions appear on the row; bulk actions appear once rows are selected.
- Status is shown with a label, not color alone.
- Plan for long values, many rows (pagination or virtual scroll) and the empty result.

**Avoid**
- Every column given equal width and weight
- Actions hidden behind a menu when there are only one or two
- Truncated values with no way to read them

**References**
- With the MCP: `search_screens(category: "table")`, `search_screens(pattern: "filter", type: "product")`
- Without: https://www.saasframe.io/md/categories/table (design guide, FAQ and three examples), then open each example's page.
