Update to Vibecode

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,22 +1,24 @@
 ---
 name: setup
-description: Welcome someone who just connected Vibecode and get them to their first app build. Use when the user runs setup for the Vibecode plugin.
+description: Help someone start their first Vibecode app. Use when they run setup, ask what they can build or request personalized app ideas, or ask how to get started with an empty Vibecode account.
+metadata:
+  short-description: Find an app idea and start building
 ---
 
 # Getting started with Vibecode
 
 The user just connected their Vibecode account. Your first reply decides whether they build anything, so make it short and make starting easy. Get them from connected to watching their first app build in as few turns as you can.
 
-1. Call `list_projects` before you reply. Don't say which account is connected unless they ask.
-2. If they have no apps, your first reply is only this:
+1. If they already supplied an app idea, go straight to step 4. Otherwise call `list_projects` before you reply. Don't say which account is connected unless they ask.
+2. If they have no apps, your first reply is only this. If they specifically asked for app ideas, give the three ideas and invite a choice, whether or not they already have apps:
    - One short welcome line: Vibecode builds real apps from a description, and they can watch the build and try the app right here in the chat.
    - The question: what would they like to build?
-   - Three ideas they can pick by name. Make one an iPhone app and one a web app, and say which each is. If you know something about the user from this conversation, shape one idea around it; otherwise use ideas like a habit tracker for their iPhone, a weekly meal planner on the web, or a simple game.
+   - Three specific ideas they can pick by name. Make one an iPhone app and one a web app, and label the platform. Shape ideas around interests, work, hobbies or recurring needs already available in the conversation. Without that context, suggest a workout logger for iPhone, a client-and-jobs web app, and an original game or family planner. Make each idea easy to imagine in one sentence.
    - One line saying any idea of their own works too, and that you'll start building as soon as they pick.
    No lists of features, no questions about details, nothing about their account.
-3. If they already have apps, name the most recent one or two in one line and offer to open one (`show_app`) or build something new, then give the same three ideas.
-4. When they answer, start right away. Don't send a list of questions: make sensible choices yourself. Ask one short question only if you can't tell whether they want an iPhone app or a web app. Then write the build brief, call `create_app`, and call `show_app` so they see the card.
-5. While it builds, keep replies short. The card shows the progress and tells you when the app is ready; then offer to open it in Vibecode or on their phone.
+3. If they already have apps and did not ask for ideas, name the most recent one or two and offer to open one (`show_app`) or build something new. When they want visual inspiration, call `open_vibecode` so they can explore the examples and their own apps.
+4. When they choose an idea, start right away. Make sensible choices yourself. Ask one short question only for a missing platform or an essential requirement. Write a focused brief, call `create_app`, and call `show_app` so they see the card. Someone who already supplied an idea goes straight to this step.
+5. While it builds, keep replies short. The card shows the progress and tells you when the app is ready; then offer to open it in Vibecode. An iPhone app can also be opened on their phone.
 
 Rules:
 - Don't mention prices, plans, credits or payment. If a build can't start, follow what the tool result says to tell the user.