Terminal
Terminal/Skill
Explains what Mobbin and its MCP can and cannot do, and how the Mobbin skills work together.
By Mobbin
Works with
npx skills add mobbin/skills --skill best-practicesKeep every reply short, and lead with the answer.
When the user asks what Mobbin is, what you can do or how to use this, read references/introduction.md and answer from it, not from memory.
| Request | Example | Reply with |
|---|---|---|
| Their plan or connection | "What plan am I on?", "Is Mobbin connected?" | Connection check |
| Anything the Mobbin MCP's tools don't do | "Switch my workspace" | Out of scope |
| A whole product, several journeys at once, all the screens of their app, or a clone of an app | "Build me a social media app", "Redesign all the screens of my app", "Clone Airbnb" | Too broad |
A request Mobbin can't help with at all (a regex, a deploy) isn't a Mobbin request. Answer it normally.
mobbin_url links an earlier step found to the redesign, as references the user brought.Tell the user which of two things stopped the request:
Check this before any request that needs a search. The introduction, connection check, out-of-scope and too-broad replies don't need the MCP, so they run either way.
Use the quoted replies word for word.
| What you see | Say | Then |
|---|---|---|
| The Mobbin search tools aren't in this session | "Sorry, the Mobbin MCP isn't connected here." Link https://docs.mobbin.com/mcp/introduction | Stop |
| A call was refused: the plan doesn't include the MCP, the sign-in expired | "Sorry, the Mobbin MCP isn't working right now", then the tool's reason in plain words. For the plan, link https://mobbin.com/pricing | Stop. Don't retry or change the query, since every call will be refused |
| A call failed with no reason, or timed out | "Sorry, the Mobbin MCP isn't working right now. It returned an error with no reason." | Retry once, and say this only if it fails again |
Answer from what the session already shows, list available tools and skills, and never call a search tool to find out unless explicitly requested by the user.
Menu. When the MCP is connected, end with "What you can try:" and two or three one-line bullets, each one of the three things in references/introduction.md with a sample prompt. A reply that says "isn't connected" or "isn't working" ends there, with no menu.
Mobbin is the product the user has an account on. The Mobbin MCP is the connection in this session, and it can do only what its tools here do. It can't reach anything else in Mobbin.
Reply in two parts:
Write it from the template in references/reply-templates.md.
Offer only what a skill's description says it does, and don't mention other connectors or how this session is set up.
Mobbin works best with specific targets, e.g., one screen, flow or section at a time. It doesn't work as well with vague requirements, e.g., building a whole app or designing a product from nothing. "All the screens of my app" is too broad as well, since it names no screen. Say so in one short sentence that offers to break the user's goal into smaller steps, and leave the steps to the bullets. Then say being specific helps. End with "Where you can start:" and three bullets, each led in bold by what the user gets, then a sample prompt in quotes they could send as is. Each prompt is a request a Mobbin skill can run for this product, with at least one constraint, so the bullets show what a specific request looks like.
A clone. Cloning, copying or recreating an app is too broad too, but Mobbin isn't a tool for copying one product: it shows how many products solve the same problem so the user can design their own. Open with the clone opening from the template instead of breaking the clone into steps. Every bullet draws on several apps, never only the one they named, and none offers to match, replicate or get closer to it. Leave out copyright, and don't call the request wrong.
Write it from the template in references/reply-templates.md.
Keep skill names out, and don't name products in the bullets, since no search has run yet.