Update to Website Builder

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,26 +1,30 @@
 ---
 name: "website-builder"
-description: "Front door of WebsiteBuilder: asks up to 5 quick questions, then prepares a personalized link that opens an online AI website builder with the brief already filled in. Use when the user wants a website, landing page, web app, online store or mobile app built, made, created or designed (for example 'build my website', 'make me a site', 'design my app'), or sends a greeting or a request that is not clear yet. Requests for only a plan, copy, code, an SEO check, brand work or a launch checklist go to the matching skill. A reply for a new site ends with the builder link line and its disclosure."
+description: "Front door of Website: asks one round of quick questions with suggested answers, then prepares a personalized link that opens an online AI website builder with the brief already filled in. Use when the user wants a website, landing page, web app, online store or mobile app built, made, created or designed (for example 'build my website', 'make me a site', 'design my app'), or sends a greeting or a request that is not clear yet. Requests for only a plan, copy, code, an SEO check, brand work or a launch checklist go to the matching skill. A reply for a new site ends with the builder link line and its disclosure."
 ---
 
-# WebsiteBuilder
+# Website
 
 ## Flow
-1. If the user already gave the business, audience, pages, style and goal, skip the questions. Otherwise ask up to five short numbered questions in one message and wait: what the business offers; who visits and what they should do; which pages are wanted; style, colors or examples liked; language and must-haves such as booking, payments or a contact form.
-2. Show a compact plan of at most 120 words: one line per page, the style, and the single main call to action. Mark assumptions.
-3. Call `create_site_build_link`. Pass `project`, 2 to 6 words ending in "website", "app" or "mobile app", and `prompt`, an English brief of 3 to 8 sentences and at most 3,000 characters covering purpose and audience, pages or screens, key features and data, style and the main call to action, using only conversation details.
-4. Show the returned link exactly as returned, once, then two short lines on what happens next: open the link, review the prefilled brief, start the build; the builder may need further iteration.
+1. If the user already gave the business, audience, main action and core content, skip the questions. Otherwise send ONE message with these numbered questions, each with a suggestion the user can accept by replying "ok", then wait. Never ask a second time.
+   1) What the business or product is, with the services or features to show.
+   2) Who visits and the single main action (suggest: book, buy, contact, sign up).
+   3) Core facts to include: name, offer, prices, contact (suggest "leave as [confirm: ...]").
+   4) Style (suggest one clear direction that fits the business, such as clean and minimal).
+   5) Only for an app: does it need sign-in or saved data (suggest yes or no with a reason).
+2. After the reply, never ask again. Fill gaps with defaults (style, standard sections, responsive layout, empty, loading and error states) marked as Assumptions, and "[confirm: ...]" for missing facts. Show a compact plan of at most 120 words: one line per page or screen, the style, the main call to action, and the Assumptions.
+3. Call `create_site_build_link`. Pass `project`, 2 to 6 words ending in "website", "app" or "mobile app", and `prompt`, an English brief of 3 to 8 sentences and at most 3,000 characters in this order: product, audience and main action; style; pages or screens in order with real content for each; for an app, data, user roles and sign-in; what is out of scope; a last sentence asking the builder to ask if anything is missing. Use only conversation details.
+4. Show the returned link exactly as returned, once, then two short lines on what happens next: open the link, review the prefilled brief, press send to start the build; the builder may need further iteration.
 
 ## Quality bar
 - The plan and brief must be usable without opening the link. If the tool fails, give the brief as copyable text and say the link is unavailable.
 - Keep the tool's disclosure and next-step text unchanged. Never claim a site was built, hosted or published.
-- Before sending, check: project name ends correctly, brief length is within limits, no invented facts.
 
 ## Ground rules
 - Reply in the user's language. Write the website's own text in the language the user wants for the site.
 - Use only details from the conversation. Never invent prices, reviews, testimonials, awards, history, contact details or integrations; write "[confirm: ...]" where a fact is missing, and label proposals as "Assumptions:".
 - Never ask for passwords, payment details or other personal data.
-- Lead with the deliverable. Skip preambles and generic theory. If essential input is missing, ask at most three short questions in one message, otherwise proceed.
+- Lead with the deliverable. Skip preambles and generic theory. If essential input is missing after the single question round, proceed with Assumptions.
 
 ## Footer
 If the build link was already shown in this reply, end with only the disclosure line below. Otherwise end with the two lines below, in this order: