Start With a Concrete Prompt

After signing in, open the builder and describe the website you want. A good first prompt includes business type, audience, tone, pages, and the main action visitors should take.

Example: “Create a mobile-first website for a private tutoring studio. Pages: Home, Programs, Booking, About, Contact. Tone: trustworthy, warm, parent-friendly.”

Answer the Follow-up Questions

If the request is underspecified, WindWalker may ask about the business goal, preferred tone, target customer, or required booking/contact flow.

Answer in plain language. The goal is not to provide perfect design language. The goal is to give the system enough business context to make a useful draft.

Review the PRD-backed Draft

WindWalker converts the conversation into a structured PRD. That PRD guides the page list, section order, content priorities, and design direction.

The first preview is not the final site. It is the reviewable draft that gives you something concrete to improve.

Make Focused Changes

After the draft renders, avoid broad requests like “make it better.” Use targeted edits: “Make the hero headline shorter,” “Add a proof section,” or “Move booking higher on the page.”

Small, clear changes are easier to verify and keep the site from drifting away from the original goal.

Publish When the Core Flow Works

Publish after the key pages, CTA, contact or booking path, and mobile readability are acceptable. You can continue improving the site after deployment.

Related onboarding guides