AppDeploy

View saved version →

---
{
  "name": "onboarding",
  "description": "Help users get started with AppDeploy by suggesting two personalized app ideas or collecting their own, then building and deploying their choice. Use when the user runs AppDeploy plugin setup or asks for AppDeploy onboarding."
}
---

Run onboarding directly in the conversation. Do not call `appdeploy_onboarding` or open the onboarding widget.

## Choose the starting point

Start with what you already know about the user from previous conversations and saved memories to understand their interests, recurring activities, and needs. Use the host's memory or conversation-history retrieval capabilities when available and needed to recall relevant information. Supplement this with any current conversation context. A new or empty chat is not sufficient reason to skip personalization.

Suggest exactly two distinct apps that match the user's interests, serve useful purposes, and are simple enough to build quickly. Give each a short, concrete title that names its main function, such as "Shopping list planner", "Chat with friends", or "Calorie tracker".

Only if neither prior knowledge nor current conversation context provides enough information to suggest useful, personalized ideas, suggest exactly two useful utility apps instead.

## Ask for a choice

After presenting the two suggested apps, call the host's native multiple-choice/ask-user tool in the same turn. Use `request_user_input_async` when available, otherwise use a compatible native tool such as `request_user_input`. Do not stop with only a question in chat or switch modes to ask it.

Ask exactly one question: "What would you like to build?" Supply exactly two selectable options: the two suggested app titles. The user's own idea belongs in the chooser's built-in free-text answer field, which is provided automatically. Leave that field empty for the user; do not add "Custom idea", "Your own app idea", "Other", or an input placeholder as a selectable option.

For `request_user_input_async`, use this payload shape, replacing the suggested titles:

    {"questions":[{"title":"What would you like to build?","options":["<first app title>","<second app title>"]}]}

For `request_user_input`, use its question and option-object schema:

    {"questions":[{"header":"App idea","id":"app_idea","question":"What would you like to build?","options":[{"label":"<first app title>","description":"<first app purpose>"},{"label":"<second app title>","description":"<second app purpose>"}]}]}

For either tool, the options array must contain exactly two app ideas. For another native ask-user tool, apply the same two-option and built-in free-text-field interaction using its supported schema.

If no native chooser supports this interaction, show both suggested app titles in chat and ask the user to choose one or describe their own idea.

Wait for an explicit selection or a non-empty custom idea before building anything. A preselected option, an unanswered question, or a dismissed chooser is not a choice.

## Build and deploy

If the user selects one of the suggested apps, briefly present a detailed build prompt describing that app's purpose and one useful core feature. Keep the app simple enough to build quickly, with that feature working end to end from the user's main action to a complete, useful result. Include only the supporting UI and data handling needed for that feature.

If the user provides their own idea, use that as the build request. Fill in routine implementation details without adding unrelated features.

For either path, proceed to build and deploy the chosen app with AppDeploy, starting with `get_deploy_instructions` and following the returned workflow. Do not stop after presenting the build prompt or ask the user to repeat their selection.