Screenrove

Generate a complete build prompt for a coding agent: ordered screens with notes, observed transitions, full-resolution image URLs, the measured design guide, and an implementation checklist. This is the same prompt as the "Use in agent" button on the site. Reference IDs: use `{product}-onboarding` for a product's signup flow, `{product}-collection` for all their screens, or any single screen id (like `linear-marketing-pricing`). Use this when you want to build UI that follows a real product's patterns. The prompt includes everything an agent needs: screenshots to reference, design tokens to match, and implementation steps to follow.

Combine specific screens from different products, plus one visual style, into a single build brief. Each screen contributes one thing (say what with "id: what to take"); structure comes from the screens and every visual token comes from the chosen style, so conflicting looks are resolved instead of mixed. Returns the brief as Markdown with the screenshots attached. When the screens contain interactive components (modals, tabs, toggles, toasts, forms), the brief also lists matching entries from the motion library to fetch with getMotion. Use this when the user wants, say, Linear's issue composer, Vercel's pricing layout and Notion's visual language in one screen. Find screen ids with searchScreens or findRelatedScreens first. For one product's whole flow or collection, use buildHandoff instead.

Compare the user's UI structure against Screenrove's catalog of real products. Describe what the user has (screen type, sections, flow steps, plan count) and get a report showing the closest real-world references with factual comparisons. Use only the fields the user provides; leave out personal names, pricing, or customer data. The report includes step counts, section counts, observed actions, and factual comparisons— not recommendations. Use this when the user wants to validate their UI against real products, understand if their flow has more or fewer steps than competitors, or see how similar screens are structured.

Compare two captured screens side by side: layout structure, page sections, observed actions, dimensions, screen types, and design guide differences. Returns a structured comparison with similarities, differences, and factual observations. Use this when the user wants to understand how two products approach the same problem differently—e.g. comparing Linear's pricing page with Stripe's pricing page, or Vercel's onboarding with Notion's onboarding. You can also compare one screen against a target description to see how close a reference matches what the user is trying to build.

Find screens from other products that solve the same design problem as this one: same primary pattern first, then shared tasks, states and components (rarer tags count more). At most two per product. Each result says why it matched. Use this after finding one good reference, to show the user how other products handle the same screen, e.g. other empty project lists, other pricing pages with a comparison table, or other create-issue modals.

Get the measured design guide for a product: observed font families, color palette, type scale, layout patterns, spacing values, and component observations. Marketing site and product UI are measured separately. Use this when you want to match a competitor's design system, understand their visual language, or borrow their typography and color choices for your own project.

Get the complete onboarding flow for a product: every step in order with titles, notes on what happens, observed transitions (button labels and where they lead), and which steps are alternate branches. Includes the handoff reference id to use with buildHandoff. Use this to study how a competitor structures their signup and onboarding, what information they collect at each step, and how they guide users to activation.

Get one motion entry as a build prompt: what moves and how (every property, duration, easing curve or spring, delay and trigger), why it feels good, what a rebuild must keep, Screenrove's working vanilla HTML/CSS/JS implementation, and the original source code when its license allows. Values are marked as exact (from code) or approximate (measured from a recording). Use the numbers as given and translate the code to the project's stack.

Get house rules for UI motion (durations, which easing for enter and exit, springs, what to animate, reduced motion) with citations, plus ready-to-use duration and easing tokens, the motion library's sources and its category and trigger vocabulary. Read this once before adding animation to an interface, so new motion is consistent.

Get a product's full collection: coverage notes, design summary, and every captured screen grouped into onboarding flow, marketing pages, and in-product screens. Use this to explore a competitor's complete UI: their signup flow, pricing page, dashboard, settings, and other screens. Each screen has notes and an image URL.

Get everything recorded about one screen: notes on what it does and how it's laid out, source URL, image URLs and dimensions, observed actions and where they lead, and page sections for long marketing pages. Use this to understand a specific UI pattern in detail before building something similar.

Get the actual screenshot so you can see the UI. For marketing pages taller than 4000px, preview returns only the first screen (above the fold); use size=full for the whole page, which can exceed what vision models accept. getScreen lists the page's sections with their y offsets so you know what's below the fold.

List every captured user journey: onboarding flows, signup sequences, checkout processes, booking flows, and marketplace explorations. Shows step counts, flow type, and observed transitions between steps. Use this to find complete user journey references—not just individual screens—so you can see how products guide users through multi-step processes like signup, onboarding, or checkout.

List every product in the UI reference catalog with its capture date, tags, coverage notes and screen counts. Start here to see what competitor products, design systems, and UI patterns are available. Products include: Linear, Cursor, Vercel, Airbnb, Stripe, Duolingo, Notion, Raycast, Cal.com, Framer, and Supabase. Each has captured onboarding flows, marketing pages, and/or in-app screens.

List the tag vocabulary for searching by design problem: four facets (task, pattern, component, state), each tag with its definition, aliases and how many screens carry it. Use the ids with searchScreens or pickReference, e.g. pattern=board-view or state=empty.

Show the user several matching UI references side by side in their browser and let them click the one to build from. Returns a URL to open for them. Prefer this over sending full-page images whenever the user should decide which reference to use. The picker shows real screenshots at scroll depth so they can evaluate long pages. After calling this, tell them to choose in the picker, then call waitForPick with the pickId to get their choice and a complete build prompt.

Search the motion library: polished UI animations and micro-interactions (button presses, toggles, toasts, number tickers, thinking states, hover effects, interaction sounds) curated from open-source component libraries and designers' recordings. Each entry has a precise motion spec (properties, durations, easing curves or spring constants, staggers) and most have a live demo with vanilla HTML/CSS/JS code. Use this whenever you build or polish an interactive element and want it to feel finished: "a satisfying copy button", "toast stack", "AI thinking indicator", "tab underline that slides". Then call getMotion for the spec, code and a build prompt.

Search the UI reference catalog by design problem and keyword. Every screen is tagged on four facets: task (what the person is doing), pattern (screen archetype), component (building blocks) and state (empty, filtered, error...). Filter by any of them; commas mean OR within a facet and different facets combine with AND, e.g. pattern=list-view,table-view and state=empty. Tags accept ids, labels or aliases ("kanban", "zero state"); listTags shows the vocabulary. q matches titles, tags, notes, page sections and observed actions; every word must match, or the closest partial matches come back with partial=true. Filter by product, kind or scope too. Use this to find design pattern examples like empty states, pricing pages, kanban boards, onboarding steps, settings or create forms. Results carry each screen's tags; refine lists the most common other tags among the results so you can narrow down. Pass a result's id to getScreenImage to see it, or findRelatedScreens for the same problem in other products. When the user wants screens combined, or a brief or spec built from several references, call buildRecipe with the chosen screen ids.

Wait for the user to choose on the pick page. Long-polls up to 50 seconds—returns as soon as they click, or status "pending" after the wait (call again if so). Once chosen, returns their reference with its screenshot and a full build prompt, so you can start building from it immediately. If they clicked "None of these fit", status is "dismissed" and you should ask what they want instead.