Use the prompt below once the brief is complete enough for the requested first version. Substitute the actual brief and accessible folder location. These bracketed fields are placeholders, not facts.
If you are continuing in the same conversation, apply the prompt yourself rather than asking the user to repeat it.
Continue the website project using the confirmed brief below. The business interview is complete enough to begin. Reuse the recorded decisions and ask only for information that blocks the next useful step.
Brief: [confirmed brief, assumptions and unresolved setup]
Bundle: [accessible folder location or attached Markdown files]
Read the skill map and load website-copy plus one main design approach. Read each additional helper only when its stage is relevant. Do not require the user to install the bundle.
If persistent file-based skills are supported and authorized, register the folders using the host's documented mechanism while preserving different existing versions. Keep the main skill and needed references alongside the helpers so their relative links work. Otherwise read the files directly. State whether they were registered or only loaded for this conversation.
Check required tools and access using the tool-setup instructions. Handle permitted setup yourself; guide steps that require approval, sign-in, selection or a spending decision. Verify the required capability.
Build the agreed site with the available tools and chosen platform. Apply usability, conversion, search and functional checks where relevant. Correct observed problems and rerun the affected checks.
Deliver the actual preview or usable files, verification evidence, remaining setup and editing instructions. Distinguish generated content, a tested preview and a published site. Continue within the authorization already provided.
See skill-map.md, tool-setup.md and launch-checks.md.