Mobbin UI references

Mobbin UI references helps search a library of real screens, user flows, and website sections from shipped products, then cite the references behind a design decision. It uses the official Mobbin MCP server rather than relying on remembered app designs. The workflow focuses on one screen, flow, or section at a time and supports UI design or implementation grounded in real examples.

Tool choice follows the target. Screen and component requests use screen search with a platform. Marketing-site hero, pricing, or footer requests use section search without a platform. Journeys, and screens whose position within a journey matters, use flow search with a platform.

Queries start with the target type and stay in plain phrases. Each contains at most three constraints, such as a state, step, visible part, or visual trait, all taken from the user's request. Domain and app name do not count toward that constraint limit. Remove the user's own brand and copy, along with filler such as asking for the best examples. Screen search uses standard mode without constraints and deep mode for one to three constraints.

Use the skill when a user wants examples of paywalls, onboarding, components, journeys, or website sections, or needs design choices supported by actual products. Scope the search to a single target. It is not a workflow for building an entire product, cloning an application in one pass, generating images, or editing design files.

Although the library covers iOS, Android, and web products, the search platform filter supports only iOS and web. An Android request uses iOS references, which must be identified as iOS when cited. A small or empty result set means few close matches for that query, not proof that the library contains no relevant material.

Inputs include the requested screen or journey, platform, user-supplied constraints, and an authenticated Mobbin connection. The output is a set of visually checked references, each with its actual app or site name, Mobbin URL, and the design decision it illustrates. Open every image before citing it and verify the returned name even if the query specified a particular app. Results are references, not code or editable design files; adaptation to the user's design system remains necessary.

For additional screen results, repeat the successful query while excluding all previously seen screen IDs. Section and flow results use the next page while another page exists. Weak matches call for changing or dropping a constraint instead of simply raising the limit. If a named app is missing, retry its exact spelling and then the other platform without filling gaps from memory. If images fail to open, request JPEG format. A refused call requires stopping and reporting the connection or plan issue rather than retrying.

The skill requires the remote Mobbin MCP server, network access, and a Pro, Team, or Enterprise account. Browser OAuth handles sign-in; tokens do not belong in prompts or files. A supported client setup command is:

claude mcp add --transport http mobbin https://api.mobbin.com/mcp

Search is read-only and sends queries to Mobbin under the user's account. The same server also exposes account-writing collection tools, which require an explicit request such as saving screens. The upstream skills are MIT licensed.