← Plugin catalog
Creativity

Flownato

UI JOURNEYS v0.8.4

UI design flows and screens

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read
  • Interactive

Cost & access

The plugin does not sell products, initiate subscriptions, display upgrade offers, or process payments. Users connect a Flownato account and use its existing entitlements. Free accounts have a daily allowance of 10 questions or 20 lookups; when it is used up, the plugin says so, says when it resets and links to the informational plans page (flownato.com/pricing), never to a checkout. Some content can be unavailable under that account's plan.

Declared limitations

  • Outside scope: Flownato provides captured design references, not travel transactions. Explain that it cannot make a reservation or payment. Do not call Flownato tools or claim a booking was completed.
  • Outside scope: the reference catalog has no access to private accounts in the depicted apps. Do not invoke Flownato tools, request credentials, or fabricate private order data.
  • Outside scope: Flownato does not provide a third-party app's production source repository or authorize reuse of its assets. Explain the limitation without calling Flownato tools or claiming a source-code download.

Onboarding example

Show me onboarding welcome screens from real apps
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 11, 2026. Package observed Nov 10, 2026.

View package source →

Description

From the marketplace listing

Look up how real mobile apps handle a task while you design. Ask for onboarding, sign-up, checkout, search or booking, and Flownato shows the screens of each flow in the order people go through them. You can also find single screens, such as login or paywall screens, and UI elements like bottom sheets or sticky buttons, shown inside the full screen they come from. Use it to compare how different apps solve the same problem, collect references for a design review, or check a pattern before you build it. Flownato covers mobile apps only. Screens are recorded from the live apps, so a particular app or flow may not be included yet. Connecting needs a Flownato account.

Language: English · Automatically detected from descriptions.

Matches for “patterns”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher keywords · listing

ui design ux design user flows app screens mobile app design ui patterns design references onboarding screenshots

What changed

· 4 observations

Capabilities & instructions

Skill instructions: added “If a tool says today's free allowance is used up, say so and when it resets; do not suggest upgrading or mention prices.”.

View comparison →
Positioning & listing

Category changed from “Productivity” to “Creativity”. Default prompt changed from “Show me hotel booking flows in Flownato.” to “Show me onboarding welcome screens from real apps”. Default prompts updated; open the comparison for details. Long description changed from “Explore real app flows, screenshots and UI...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Keywords

Files & skills

File archives

Plugin package7 files · 34.2 KBBrowse files →
Skill instructions
visual-research5.45 KB

View saved version →

---
name: visual-research
description: Browse real app flows, screens, and UI elements in Flownato, or compare captured examples for UX research. Use when someone asks for Flownato references or visual examples from real apps.
---

Use the connected Flownato tools to present real visual references in the conversation.

Retrieve catalog content, screenshots, and the interactive interface through the connected production Flownato service. Do not read a local checkout, local fixture, or localhost preview as a substitute for the installed plugin. If the connection needs authentication, use the host's normal OAuth connection flow; do not bypass sign-in or fabricate results.

## Choose the result

- A task across apps, such as onboarding or hotel booking: call `search_flows` once. Pass the requested number as `limit` (1–20); use the tool default when no number is given. Each gallery preview opens its flow without another chat message.
- All journeys in one app: call `search_flows` with an empty `query` and the named `app`. A task across all apps: set `query` to that task and omit `app`. Keep the same app scope when refining a task unless the user changes it.
- A named app and task, or a specific selected flow: call `show_flow`. Use the returned canonical path for exact follow-ups.
- A screen pattern such as login or order review: call `find_screens`. Set `app` when the user names an app; omit it for references across apps.
- A UI element such as a sticky button or tab bar: call `search_elements`. Set `app` when requested; omit it for references across apps.
- Which apps are covered: call `list_apps`.

A request to browse ten flows is complete when the gallery contains the matching results. Do not enumerate apps and search each one, or open every result individually. Describe missing coverage without quoting a total. For comparisons, retrieve only the selected flows needed to support the analysis.

## Keep browsing continuous

Each request gets its own focused result card: flow gallery, selected flow, screenshot references, elements in their original full screens, or apps. Search and refine through conversation, using the current selection and returned canonical paths for follow-ups. Do not tell the user to use a search box or global tabs inside a result: those controls are intentionally absent. Connected account and disconnect controls belong in the host's plugin settings.

For a general tour, show one requested capability at a time and explain a useful next prompt. Do not call every research tool in one burst: hosts may keep only the final view visible. Results load in small batches as the user scrolls toward the end of a continuous strip. The widget requests continuation itself; do not call `load_more` from chat or narrate pagination. Loaded cards and scroll position stay in place. A Load more button provides a keyboard and retry fallback. Do not show page numbers or result totals. Element results keep the full original screenshot and outline the relevant element; never describe these as cropped previews. A selected flow progressively renders its captured steps in an ordered horizontal strip, with images loaded as needed. Clicking a screenshot enlarges it in place. Its app, screen, element label or flow step becomes the context for follow-up questions. Use that selection to resolve “this element” or “this step”; verify the screenshot before making visual claims. An explicit Open in workspace control gives the same selection more room when supported; never claim expansion is available or occurred without evidence. Use a single appropriate tool for a specific requested view and do not replace it with a different view afterward.

Let the result card carry the screenshots and controls for inspecting that result. Accompany a browsing result with a brief sentence explaining the useful next action; avoid repeating the result as a Markdown image table or a list of website links. Keep browsing in the conversation card unless the user expli

Preview of the first 4,000 characters. Read full instructions →

Release notes

Listing: category, descriptions, starter prompts and keywords. Server instructions suggest example asks and explain the free daily allowance when it is used up, with a link to the informational plans page. Near the end of the allowance, results say how many free lookups or questions are left. No new tools, permissions or output fields.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
UI JOURNEYS
Keywords
See keywords
Declared availability
No country restrictions declaredDeclared regions; live availability may differ.
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Read
  • Interactive

Package observed Nov 10, 2026.

Technical details
First seen
Oct 24, 2026 · 12:40 UTC
Last seen
Nov 11, 2026 · 06:00 UTC
Latest observed change
Nov 5, 2026 · 06:08 UTC
Collection status
Collected

plugin_asdk_app_6ac169e93dc48191a3a1242fef8c8d62

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.